Retry a message that shows as not sent
Understand the "not sent" bubble states in the Chat tab and use Retry instead of assuming the message is lost or that it silently went through.
Why a message ever needs a retry
The engine holds exactly one send in flight at a time, and it does so at a human pace. If you (or whoever else is on this account) send a second message while the first is still going out, the second one does not queue quietly — the panel would be lying if it showed "sending…" for a message that has nowhere to wait. Instead it lands as a terminal, honest "not sent" bubble immediately, with a Retry action attached.
This is not a bug — it's the alternative to a silently lost message
Before this was built, a normal human reply cadence (two messages back to back) could make the second one vanish with no trace and no button. A visible "not sent, tap Retry" is the fix — the message was never queued, so there is nothing to wait for and nothing to lose track of.
Reading the bubble icons
| Icon | Meaning |
|---|---|
| ✓ (check) | Confirmed sent by the platform. |
| ○ (circle) | Still in flight — queued, or paused on the platform's own side. Not final yet. |
| ✕ (retry) | Not sent. A Retry action is offered. |
An unrecognized or future status intentionally renders as the circle, never the checkmark — "delivered" is the one claim the panel refuses to guess at.
Using Retry
Pressing Retry sends the same text as a brand-new send: it goes through the firewall and the engine again from scratch, because there's no delivery idempotency key on the platform side to "resume" the original attempt with. Two guardrails come with it:
- you can only retry a row that's genuinely
failed— a message still in flight can't be retried, because it might still land in the same second; - a row can only be retried once. A second press on the same bubble is refused outright, not silently turned into a second copy of the message going to the fan.
What's next
- Reply to a waiting fan — the normal send path this recovers from.
- Shadow sends and the kill switch — what it means when nothing ever reaches "sent" at all.
Get an AI-drafted reply
Generate a handful of suggested replies for the open thread and paste the one you like into the composer — the AI never sends anything itself.
Clock in/out and see your own KPIs
Start and end a worked shift from the Chatters tab, and read your own reply-time, PPV, and revenue numbers for the day.