Routing & Automation
Part of Support routing and automation
Preventing duplicate customer replies from workflow rules
Audit default notifications and automation rules so each ticket event produces the intended customer message once.
Assign every customer-facing event an intended message. Check each rule that can send it. A default notification and a workflow rule may both email the requester when the same ticket is created or updated. Trace one affected ticket to see what actually sent each message.
Map the messages
List the events where the team intends to contact a customer: request received, agent public reply, waiting reminder and resolution, for example. For each, record the purpose, recipient and the rule or notification responsible.
| Event | Message to inspect | Possible overlap |
|---|---|---|
| New request | Acknowledgement | Default notification and creation-rule email |
| Agent public reply | Agent's answer | Update rule sending another message |
| Waiting reminder | Request for outstanding information | Time condition that remains true |
| Resolution | Outcome notice | Separate solve and close notifications |
Two messages can be appropriate when they serve distinct purposes. Compare their delivered wording and timing before calling them duplicates.
Trace one duplicate
In Zendesk, ticket Events can show email notifications and associated triggers. Zendesk says multiple triggers on one update commonly cause duplicate emails, and advises checking a default trigger's purpose before deactivating it.
Freshdesk says a creation rule that emails the requester can overlap the default new-ticket notification. The Activities view can identify the rule. One documented remedy is removing an unnecessary email action.
Freshdesk's notification guide suggests a skip action; its creation-rule guide describes that action for agent notifications. Check the effect in the configured account before using it to suppress a requester message. Turning off an account-wide notification requires reviewing other ticket routes.
If the event log does not show two outgoing actions, check whether the customer sent separate enquiries or the mail path created separate ticket records. That differs from two workflow emails on one event.
Prevent repeated sends
Tie an acknowledgement to the intended creation event. A reminder should require the relevant waiting state and stop after an answer or a recorded reminder stage. Zendesk automations need a nullifying action or once-only condition. Freshdesk warns that an open-ended hourly time condition can act again on later runs.
Review rule order and the final message set. Freshdesk creation rules can execute the first match or all matches, and Zendesk ticket-trigger actions can affect later triggers. A narrow rule alone does not prove only one customer message was sent.
For a proposed change, use safe sample tickets for each affected event. Inspect the ticket log and a test recipient's inbox for the content, sender and timing. A logged send action does not prove what arrived. Keep the event-to-message map current when a rule or default notification changes.
