REDA One Help Center
EN
Language
English EN Español ES Português PT Italiano coming soon Français FR Deutsch coming soon العربية coming soon
reda.one ↗
Home / REDA Connect / Bulk Messaging / Bulk messaging — sending one message to many people

Bulk messaging — sending one message to many people

Bulk messaging sends one templated message to many people at once, straight from a Salesforce list view. You pick the people on a Leads or Contacts list view, click one button, choose a template, and REDA Connect creates and sends an individual message to each person — each one tracked with its own delivery status, and all of them grouped under a batch name you choose so you can find them again later.

Bulk messaging is available on Leads and Contacts — both objects, as of REDA Connect 1.93. Other objects (Cases, Opportunities, custom objects and so on) don't have a list-view send; messages on those records are sent individually from the Connect Feed on the record — see Sending your first message.

What a bulk send can send

  • Template workflow. This walkthrough uses an active Connect Template. If your screen also offers free text, channel restrictions still apply. Only active templates are offered; a template that hasn't been tested and activated won't appear. See Testing and activating a template.
  • Channel rules still apply. On SMS, only Text templates can be sent. On WhatsApp, the template types your account supports are available. If you pick a channel and see No active template found for the provided messaging channel., you don't yet have an active template usable on that channel.
  • Merge fields work per person. A template with merge fields is filled in from each recipient's own record — every person gets their own personalised copy. See Merge fields in templates.

The limits, plainly

LimitWhat it means
1,000 recipients per sendRecipient lookup is limited to 1,000 records per object configuration. You may see the warning You have selected more than 1000 records. Only first 1000 records in the list are considered. — split larger audiences into multiple sends and verify the eligible count. Multiple matching configurations do not establish a global 1,000-recipient guarantee.
No phone number = skippedAnyone without a phone number in the field configured for the chosen channel is simply left out. No message record is created for them, and no error is shown per person.
Opted-out people block the whole sendIf any eligible recipient has opted out of the chosen channel, the entire send is blocked — nothing goes out to anyone until the opted-out people are removed from the selection. See Tracking a bulk send for the exact error and how to filter them out beforehand.
One at a timeMessages in a batch are sent one after another, not all at once, so a large batch takes a while to finish.

Where the messages land

Every bulk send asks you for a Message Batch Subject — a short name for the batch, like August rent reminder. Each message created by the send carries that value in its Batch Id field, so the whole batch can be pulled up later in a list view or report and its delivery statuses read at a glance. Tracking a bulk send shows how.

Each message also appears in the Connect Feed of its own Lead or Contact, exactly like a message sent individually — the recipient sees no difference, and a reply comes back into the same feed.

Before you can bulk-send, the basics must be in place: an active Connect Account for the channel, an object configuration for Leads or Contacts on that channel, an active template, and correctly formatted phone numbers on the records.

FAQ

No. Bulk messaging works from Leads and Contacts list views only. If your audience lives in a report or campaign, build a list view that matches the same filter and send from there.

No. A bulk send creates a separate, individual message per person — like BCC, not a group chat. Replies come back individually into each person's Connect Feed.

This guide uses a Connect Template that has been tested and activated. If your screen also offers free text, check the applicable channel restrictions before using it.

Not from a list view. Messaging on other objects happens per record from the Connect Feed. If the people behind those records are Contacts, consider bulk-sending from a Contacts list view instead.

Where to go next