The broadcasts list
The Broadcasts page is your dashboard for every campaign you’ve created. Each row summarizes one broadcast:
ID — the broadcast’s internal identifier.
Name — the name you chose.
Type — the channel type (SMS or WhatsApp), with the channel icon.
State — a colored badge: Draft (amber), Pending (blue), Live (green), or Failed (red).
Progress — a percentage plus a
succeeded / total sentcount. The percentage is green at 90% and above, amber at 50–89%, red below 50%.Date — when the broadcast was created.
Actions — a View button that opens the detail page.
Open the broadcast detail page
Click View on any row to open the detail page. The header shows the broadcast’s name and its current state badge. For a Pending broadcast you’ll also see the note: “Broadcast is being processed. It usually takes up to 5 minutes before setting to live.”
Below the header, a five-card grid summarizes the broadcast: Broadcast Name, Intercom Workspace, Channel, Created At, and Cost. The Cost card reads “No extra charge” for broadcasts created under the current pricing; it also notes “Broadcast messages count towards your channel’s messaging limits.”
Inspect the message and filters
Two cards below the summary show exactly what’s being sent:
Broadcast Message — the SMS text, or the rendered WhatsApp template bubble with variables, footer, and buttons.
Filters — the filter rules you built in step 1, listed as
field / operator / valuebadges with the AND/OR logic between them.
These are read-only once the broadcast has been activated.
The Analytics section
When the broadcast is in the Live state, an Analytics section appears with four cards:
Total — the total number of messages Octopods attempted to send.
Succeeded — messages that were delivered successfully.
Pending — messages still in flight or awaiting delivery confirmation.
Failed — messages that could not be delivered.
These counters update as the broadcast progresses. Refresh the page to see the latest numbers.
Review failed contacts
If the Failed count is above zero, a collapsible Failed Contacts section appears below the Analytics cards. Expand it to see up to 50 failed sends in a table with columns:
ID — the Intercom contact ID.
Name — the contact name.
Phone — the phone number Octopods tried to message.
Error — the failure code and description returned by the channel provider.
Each row includes a View link that opens the contact in Intercom.
To export every failed contact (not just the first 50), click Download as CSV at the bottom of the section. The CSV contains Id, Name, Phone, Role, and Failure Reason for every failed message.
Browse matched contacts
The Matched Contacts section below is collapsible and shows up to 150 of the contacts the broadcast targeted, with a note: “There are X users and leads matching your rules for this message. We usually only display the first 150 matches as a sample.” Each row links to the contact’s full profile in Intercom.
Understand each broadcast state
Draft. Nothing has been sent yet. The detail page offers a Delete button and (if a channel is connected) a Pay & Set Live button to activate the broadcast.
Pending. Octopods is preparing to send. No Analytics section yet. The header note reads: “Broadcast is being processed. It usually takes up to 5 minutes before setting to live.”
Live. Messages are going out. Analytics, Failed Contacts, and Matched Contacts are all visible.
Failed. The broadcast could not activate — typically because the audience exceeded the 10,000-contact limit. The header shows the red note: “Broadcast has failed due to reaching maximum contact count.” You can delete it and start again with narrower filters.
What to do if a broadcast fails
A broadcast lands in the Failed state when activation itself couldn’t complete — not when individual messages fail during send. From that state:
Open the detail page to read the failure note in the header.
If the cause is “reaching maximum contact count”, click Delete and create a new broadcast with filters that match fewer than 10,000 contacts. Adding a tag, segment, or date range is the quickest way to narrow the audience.
What to do when individual messages fail
If the broadcast itself went Live but the Failed analytics card has a non-zero count, some messages couldn’t be delivered to specific contacts (bad numbers, carrier errors, recipient blocked, and so on). To try those sends again, use the Resend Failed Messages action — see Retrying Failed Broadcasts.
What’s next
See the Channels section for channel health and delivery troubleshooting