Plan requirement
| Subscription | Any plan |
| Access | Admin |
Two rules explain everything here. Zendesk identifies the author of an email from the Reply-To header when it is present, and falls back to From only when it is not. And when those two disagree and the Reply-To address belongs to an agent, Zendesk restricts what agents can do on that ticket.
Why do replies go to the wrong address?
- A warning icon flagging the ticket, with no obvious error message.
- Agents cannot change ticket properties, manage CCs or followers, or attach files on that ticket.
- Tickets arriving with your own address as the requester.
- Replies going to a colleague rather than the customer.
Why Reply-To wins
It follows the email standard: the Reply-To field states where the author wants replies sent, so it supersedes the From field. This behaviour cannot be changed, and there is no setting for it. Where there is no Reply-To at all, From is used instead, and the body of the message plays no part either way.
That single rule accounts for most surprises in this area. A message forwarded or rewritten in transit arrives with a Reply-To that is not the customer, and Zendesk believes it, exactly as the standard says it should.
Resolution steps
1. Is the Reply-To address an agent's?
That is the specific condition. A From and Reply-To mismatch on its own is ordinary; a mismatch where Reply-To is one of your agents is what triggers the restriction. It is an anti-spoofing measure, not a fault.
2. Restore the abilities through the allowlist
An admin adds the agent's email address or domain to the allowlist in Admin Center under People > Configuration > End users. Do that only where it genuinely poses no security risk, because the restriction exists to stop somebody impersonating an agent.
3. Check the forwarding that produced it
Some mail systems rewrite the sender or the reply address when forwarding, so messages appear to come from your own domain. That is the usual origin, and the fix belongs in the forwarding configuration rather than in Zendesk.
4. Check for a group or alias in the path
Mail groups and distribution lists often rewrite addresses. Where one is used as a support address, its own settings decide what the message looks like on arrival.
5. Correct the requester on the tickets you already have
For a backlog of affected tickets, setting the requester to the real customer is the per-ticket fix. It does not prevent the next one; steps three and four do that.
Comments
0 comments
Article is closed for comments.