Tracking a bulk send
Every bulk send is stamped with the Message Batch Subject you typed when you sent it. That value lands in the Batch Id field of every message the send created — so one filter on that field pulls up the entire batch, in a list view or a report, with each message's delivery status next to it. This article shows how to find a batch, how to read it, and the one rule that can stop a send before it starts.
Finding your batch
In a list view
- From the App Launcher, open Connect Messages.
- Open the list view controls (the gear icon on the list view) and create a new list view — call it after your batch, for example
August rent reminder. - Add a filter: Batch Id equals your batch subject — exactly as you typed it during the send, e.g.
August rent reminder. - Add the columns worth watching: Status, To Number, Record Name, Channel, Error Message.
Expected result: the view lists one message per recipient of the send, each with its own status.
In a report
The same filter works in any report on Connect Messages: filter Batch Id equals your batch subject. Reports are the better tool once you want counts — group by Status and you get a one-line summary of how the batch did. REDA Connect also ships ready-made message reports — see Reports and dashboards.
Reading the statuses
Each message in the batch moves through its own delivery lifecycle. The statuses you'll see:
| Status | Meaning |
|---|---|
| Queued / Accepted / Sending | Handed to the provider, on its way (SMS mostly) |
| Sent | Left your org and was accepted by WhatsApp or Twilio |
| Delivered | Reached the recipient's phone |
| Read | Opened by the recipient (WhatsApp only) |
| Failed / Undelivered | Didn't get through — the Error Message field on the message says why |
The full story of each status is in Understanding delivery statuses. For failures, start with the message's Error Message field, then A message isn't sending.
How long a batch takes
Messages in a batch are sent one at a time, one after another — not all at once. A small batch finishes in moments; a batch of many hundreds takes correspondingly longer. This is normal: if you open your batch view and see some messages already Sent or Delivered while others show no status yet, the send is simply still working through the list. Refresh the view rather than re-sending — re-sending creates duplicates.
Recipient has opted out of receiving SMS Messages.(SMS sends)Recipient has opted out of receiving WhatsApp Messages.(WhatsApp sends)
The fix is to remove the opted-out people from the selection first: filter your Leads or Contacts list view on the opt-out field for the channel — for example Opt Out (REDA Connect - WhatsApp) equals False — so only contactable people are selected, then send again. Opt-out fields on Leads and Contacts shows the fields and the filtering technique in detail.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| The batch filter returns nothing | The Batch Id filter doesn't exactly match the subject you typed at send time | Check the exact spelling — open any one message from the send and copy the Batch Id value |
| The whole send was blocked with an opt-out error | At least one selected person has opted out of the channel (all-or-none rule above) | Filter opted-out people out of the list view and re-send |
| Batch has fewer messages than people selected | People with no phone number for the channel were skipped at send time | See Sending a bulk message from a list view, Troubleshooting |
| Some messages show Failed | Per-message problem — bad number, provider rejection, template issue | Read that message's Error Message field; then A message isn't sending |
| Statuses stuck at Sent, never Delivered | Delivery receipts aren't reaching your org | Check the webhook setup — Creating the public Site |
FAQ
You can — nothing enforces uniqueness — but then both sends show up under one filter. A date or month in the subject (Rent reminder 2026-08) keeps batches cleanly separated.
No. The confirmation at send time (This action is not reversible. Are you sure to send list messages?) is the last stop — once queued, the batch runs to completion.
No. A reply is an inbound message on the person's own record and appears in their Connect Feed; the batch filter shows only the outbound messages the send created. See Receiving and replying.
Report on Connect Messages filtered to the batch subject for the outbound side, and check each record's feed for replies. There's no single built-in "response rate per batch" metric.
Where to go next
- Opt-out fields on Leads and Contacts — filter opted-out people out of your selections before sending.
- Understanding delivery statuses — the full lifecycle of a message.
- Reports and dashboards — the packaged reporting on messaging activity.