Dark mode
Email delivery & message status

Email delivery & message status

Open in ChatGPT Open in Claude

Every reply carries a delivery state, so you can tell the difference between "the customer has it" and "we think we sent it." This page explains the states you will see and what each one means for your next move.

Reading the status on a message

Each outgoing message shows a small status indicator in the thread. The indicator names the channel it went out on — chat bubble, envelope for email, Telegram icon — and shows a state. Click it to open message info for the full detail.

The states, in the order a message normally passes through them:

State

Meaning

Queued

Accepted but not yet dispatched. A message that is still cancellable sits here.

Sending

Handed to the provider, not yet acknowledged.

Sent

Accepted by the provider. Not proof the mailbox took it.

Delivered

The receiving mail server accepted it. For email this is the strongest routine signal short of an open.

Read

The customer opened it, for email.

Failed

It did not get through — a bounce, a block, or a spam complaint.

Unknown

No receipt information available.

External

The message came from outside Helpin, for example a reply the customer sent from their own mail client.

Failures tell you what to do

A failed email is not one condition. The indicator distinguishes them, and the distinction changes your next step:

  • Bounced or failed — the address did not accept the message. Check the address before resending; resending to a hard bounce will fail the same way.

  • Marked as spam — a complaint. Do not resend the same content to the same person. Change the approach, or stop.

  • Not sent (blocked) — the provider refused the send. On a messaging channel this usually means the customer blocked the bot; on email it means the send was blocked rather than bounced.

When a failure carries a description, the message info dialog shows it. Read it before you retry.

The states that lie to you

  • Sent is not delivered. Treating sent as arrived is how teams discover a week later that a customer never got the answer.

  • No status is not success. Unknown means you do not know, which is different from "fine."

  • Queued can be cancelled. If you spot a mistake in the moment, check whether the message is still queued before adding a correction reply.

Practical habits

  • Check the indicator before re-sending. A bounce and a slow queue need opposite responses.

  • Do not stack corrections on a queued message. Cancel it if you can; otherwise let it land and follow up clearly.

  • For email conversations, prefer the thread — replies keep the same thread and sender, so the customer's client groups them properly.

  • A failed reply does not resolve anything. If delivery failed, the conversation is still open regardless of what the status field says.

  • Treat spam complaints seriously. They damage deliverability for every customer on the domain, not just the one person.

Was this article helpful?