How to recover "Received from support address" suspended tickets in Zendesk
By Jake Marsh · Updated
Zendesk can't recover "Received from support address" emails as they are, because the sender is one of your own support addresses. To recover them in bulk, install Winnowell and create a rule with the condition "cause of suspension" set to that cause and the action Recover with a requester. Winnowell takes the requester from the forwarded "From:" or "Reply-To:" line, or from a fixed address you choose, and the dry run lists the requester it found for every email.
Why these emails get suspended
Zendesk explains in What does "Received from support address" mean? that the email came from one of your support addresses and could cause a mail loop, for example when your own inbox forwards mail to Zendesk. Zendesk notes these tickets can't be recovered automatically: each must be recovered manually with the original sender set as requester. That is the step Winnowell does for you, across the queue.
Steps
- Open Winnowell from the left navigation bar and go to Rules. Or open one of these suspended emails in the queue and choose Make a rule from this.
- Add the condition. Cause of suspension is "Received from support address". Add more conditions if only some of them are real, for example sender email is your forwarding inbox.
- Choose the action Recover with a requester. Under Requester, pick how it's found:
- Sender in a forwarded "From:" line: Winnowell reads the first forwarded "From:" or "Reply-To:" line in the email, never one of your own support addresses. Add a Fallback requester (optional) for emails where none is found.
- Always this address: every match is recovered under the Requester email you enter.
- Add tags or an internal note naming the rule, if your team wants to see where the ticket came from.
- Watch the live matches. While you edit, the right side shows the emails in the queue that match.
- Run the dry run. In Suspended queue, click Run rules (dry run first). Check the requester Winnowell found for each email.
- Start. Winnowell recovers in batches of 100 and tags each recovered ticket (default
winnowell_recovered).
What the dry run tells you
| You'll see | What it means |
|---|---|
| "requester:" and an address under an email to recover | The requester that email will get |
| Rule "...": no forwarded sender found in the message and no fallback requester set. | Listed with what will be skipped: no requester could be found and the rule has no fallback |
| Matches per rule and overlaps | Which rule decided each email; the first match wins |
| Left alone | No rule matched |
Emails with no requester found stay in the queue, so nothing comes back under the wrong customer.
Recover a few by hand
For a handful, select the emails in Suspended queue, type the requester's address in the box next to the buttons, then choose Recover selected as this requester. Winnowell still writes them to a log ticket.
Fix the cause too
Recovering clears the backlog, but new forwarded mail keeps landing here until the forwarding setup changes. Zendesk's article says the from and reply-to addresses need to show the actual requester's address.
Make it automatic
Once you trust the rule, tick Run automatically on it and turn on Automatic recovery in the app settings. While at least one person with Winnowell has Zendesk open, it checks the queue every 15 minutes (or your interval) and recovers what that rule decides, logging each pass on that day's log ticket.
What it costs
Winnowell is billed monthly by Zendesk per account: Team $99 (up to 100 rules), Professional $199 (up to 250) or Enterprise $349 (up to 5,000), every feature on every plan, with a 14-day trial. The Winnowell documentation covers every condition and action.
Winnowell
Suspended ticket rules: dry run first, then bulk recover or delete, with an audit trail in Zendesk. From $99 a month per Zendesk account.
Questions
Why can't Zendesk auto recover these tickets?
The sender is one of your support addresses, so recovering as is would make your own address the requester and risk a mail loop. They need a different requester, which is what Recover with a requester sets.
Which address becomes the requester?
The address in the first forwarded "From:" or "Reply-To:" line, never one of your own support addresses, or the address you set with Always this address.
What if the forward has no From: line?
Then no requester can be found. Unless the rule has a fallback requester, the email stays in the queue and the dry run says so; recover it by hand with Recover selected as this requester.
Does the recovered ticket keep the original email?
It is recovered through Zendesk's recovery with the requester you set, and the log ticket records the sender, subject, cause, rule and new ticket number.
More Winnowell guides
- How to bulk delete suspended spam tickets in Zendesk safely
- How to recover suspended tickets automatically in Zendesk
More Zendesk guides
- How to send an Onfido verification link from a Zendesk ticket (Whowell)
- How to find your Mirakl shop API key and API host for Zendesk (Wharfwell for Mirakl marketplaces)
- How to load discount codes into Zendesk from a CSV file (Vouchwell)