Resend a failed message
When an outbound email fails to send, you no longer need to hunt for a banner above the composer. The failed message itself carries a send again icon — click it, and Atender retries that message right where it is.
Where to find it
Open the conversation and find the failed message. Next to it you’ll see up to two icons:
- Send again — retries the message. Available to any agent with reply permission.
- See why it failed — links to Email deliverability settings, so you can check the sending domain. Visible only to agents with permission to open that settings screen (typically owners and admins).
Every agent can see that a message failed. Not every agent can see the way into the settings that explain why — that’s gated separately.
Resending
Click the send-again icon on the failed message. Atender puts the message back into the send queue and clears the failed marker while it retries.
You don’t need to worry about clicking it twice, or two agents clicking it at once. Atender only lets one retry claim a message that is still genuinely in a failed state — if the message has already moved on (for example, a delayed delivery confirmation came in and corrected it), the retry is refused rather than firing a second email. A resend also won’t duplicate an earlier resend of the same message within a short window.
If the resend also fails
The message goes back to the failed state, exactly as before. The send-again icon reappears, so you can try again once the underlying issue is resolved — no need to reopen or recreate anything.
What resend does and doesn’t do
- Email only, for now. Send again currently applies to outbound email messages. Other channels don’t show this icon.
- No change in wording or channel. The resend uses the original message content — it doesn’t let you edit the message or re-target another channel.
- Doesn’t require deliverability access. You can retry a failed send without being able to see why it failed. Those are two separate permissions.
Related
If the message keeps failing, an agent with access to See why it failed should check Email deliverability settings for the sending domain before retrying again.