What this helps you do
When a message does not reach someone, the Hub tells you why, so you know whether there is anything to fix. Most of the time there is nothing to do on your side: the person muted or disconnected in Blasts, replied STOP, or their email bounced and the Hub already moved them back to Blasts-only.
When to use it
Check this when Sent and Scheduled shows a send did not fully deliver, when the read count on something urgent is lower than you expected, or when a banner on Home says your Blasts account needs attention.
How to do it
- Open Sent and Scheduled and open the send to see delivered and read counts, and the reason any message did not deliver.
- If someone muted or disconnected in Blasts, there is nothing to fix. They can reconnect whenever they like, and someone who has moved on simply stays disconnected.
- If someone replied STOP, their person page shows it, and nothing is sent to them until they reply START.
- If a person's email bounced, the Hub switches them back to Blasts-only automatically. No action is needed.
- If your connections look out of date after an import or a busy signup period, click Sync connections.
- If a banner says your Blasts account needs attention because the session expired, tap Reconnect. This affects your organization's session only, never anyone's connection.
Example
After an urgent notice, a handful of messages show as not delivered. The screen explains that two people disconnected and one muted the sender. There is nothing to fix, and any of them can turn messages back on whenever they like. You click Sync connections so the list is current before the next send.
Good to know
- No credits are charged for failed sends.
- Delivered and read counts come from confirmed actions, not tracking pixels, so a low read count is real information.
- Neither a delivered count nor a read count is an acknowledgement. When you need people to confirm, ask for a YES or NO reply and let the Hub count the answers.