What Is Salesforce Bulk Texting and How Does It Work?

Salesforce bulk texting is about sending one message, personalized per recipient, to a large group of Leads or Contacts at once, straight from Salesforce records. Not a batch export. Not a separate platform bolted on the side. The send happens inside the CRM itself, and every reply logs straight back to the same record it came from, no manual matching required afterward.

Salesforce itself doesn’t do this natively, and it never really has. You need an app for it, and that gap is really the whole reason this post exists. Teams that skip that step end up stuck sending one text at a time, or worse, exporting lists to some outside tool and losing the connection to their own CRM data entirely.

What is Salesforce bulk texting?

One message, many recipients, each one personalized, sent from a Salesforce List View, or Campaign, or a Report inside Salesforce.

That’s it. No batching things manually in a spreadsheet, no separate messaging tool disconnected from your CRM. The data driving the send and the record it logs back to are the same record the whole time.

How does it work inside Salesforce?

There can be three starting points with an advanced mass texting solution, and which one you pick depends on how the list already lives in your org. and the audience size you want to target.

From a Report. Build a report for whatever condition matters: contracts expiring next month, leads untouched in 14 days, whatever. Run it, select the records, send. No developer required.

From a List View. Faster for smaller, more ad hoc groups. Filter the view, select rows, fire the send. Good for a small segment of audience like “everyone who registered for Tuesday’s webinar.”

From a Campaign. Best when you’re already tracking membership over time. Add or remove people from the campaign as it evolves, and the send list updates with it, no rebuilding from scratch each time.

Under the hood, a Salesforce-native SMS app queues these sends in controlled batches rather than firing everything at once. Salesforce puts hard limits on how many actions can fire simultaneously, and blowing past them is exactly how mass sends fail silently.

Bulk texting vs group texting vs drip campaigns

These three get lumped together constantly. They’re not the same thing.

	Bulk Texting	Group Texting	Drip Campaigns
What it is	One message, many recipients, sent once	A handful of people in one thread	A pre-set sequence sent over time
Typical size	Hundreds to millions	Under 10-ish	Any size
Timing	One send	Real time	Staggered, rule-based
Best for	Announcements, alerts, reminders	Small internal or team threads	Nurture sequences, onboarding, follow-ups

 

Bulk is a single blast. A drip is a sequence with logic behind it: wait three days, check for a reply, send the next step. Group texting isn’t really a marketing tool at all; it’s closer to a shared thread. Mixing these up is how campaigns end up either annoying people or under-delivering.

What are the limits?

Here’s the part that actually matters once you’re sending at real volume.

Throughput and batching. Salesforce caps how many operations can run at once. A proper native app queues messages into batches behind the scenes so a 50,000-record send doesn’t just fail outright. Without that batching layer, you’ll hit governor limits fast.

Carrier filtering. Carriers actively filter for spam patterns, identical message bodies sent too fast, links that look sketchy, and sender behavior that looks automated. Even a technically valid send can get throttled or blocked if it trips those filters.

Number and sender-ID constraints. High-volume sending usually needs a dedicated number type built for it (think 10DLC or short code in the US), not a personal mobile number repurposed for bulk. Skip this step and delivery rates tank, sometimes without any obvious error on your end.

Plan around these three before you plan the campaign copy. Copy is easy to fix after the fact. A blocked sender ID is not.

What does bulk texting cost?

Two layers, and people usually only budget for one of them.

App cost. A license fee for whatever Salesforce texting tool you’re using to send through, priced per user or per org depending on the vendor.

Carrier cost, per segment. This is the one that surprises people. SMS is billed per 160-character segment under standard encoding, but a single emoji or curly quote can flip the whole message into Unicode encoding, which drops that limit to 70 characters. A message you thought was one segment quietly becomes three, and your bill triples for that send. 

Budget for segments, not just seats. That’s where bills go sideways.

Getting consent right before you send at scale

Bulk is where compliance mistakes get expensive fast. One bad send doesn’t touch one person; it touches thousands.

Get express written consent before marketing texts go out. Log when and how it happened. Simple enough to say, easy to skip when you’re moving fast.

Most tools stop at keyword matching for opt-outs. STOP, CANCEL, UNSUBSCRIBE, done. But people don’t always type the magic word. Someone writes “please stop texting me,” and a keyword-only system just… doesn’t catch it. 360 SMS AI compliance runs intent-based opt-out detection instead, so that the reply gets flagged even without the exact keyword match.

Consent isn’t really one setting either. A contact might want out of marketing texts but still needs appointment reminders from support. Selective opt-in and opt-out handles that by geography, language, or department, not one blanket toggle covering the whole org. And AI compliance monitoring runs quietly in the background the whole time, catching risk before it turns into a complaint instead of after.

Quiet hours matter too. Worth remembering they shift by jurisdiction. There’s no single universal window that covers everyone.

Wrapping Up:

Getting Salesforce bulk texting right in Salesforce comes down to picking the right Salesforce-native solution built for exactly this, not a bolted-on connector. Once you’ve got a native app in place, bulk and scheduled texting is a natural next step for planning sends around time zones instead of firing everything at once.

Ready to see it running against your own Salesforce data? 

Contact our experts today!