Salesforce SMS Integration: The Complete Guide
Salesforce integrates with SMS in exactly three ways: the native Digital Engagement messaging channel, a managed AppExchange app such as WatBox, or a custom build on an SMS API like Twilio. All three let your team send and receive text messages against Salesforce records; they differ in cost, required editions, setup effort, and how much of the compliance work — sender registration, opt-outs, quiet hours — is handled for you.
This guide covers all three routes, the US carrier registration (A2P 10DLC) that gates business texting, a step-by-step setup, what each layer costs, and the compliance rules that apply no matter which path you choose.
What are the 3 ways to integrate SMS with Salesforce?
| Native Digital Engagement | AppExchange app (e.g., WatBox) | Twilio / custom API | |
|---|---|---|---|
| Best for | Service teams on qualifying Service Cloud editions | Sales + service + marketing texting with fast, no-code rollout | Unusual data models or in-house platforms with dev resources |
| Setup effort | Admin setup; requires the Digital Engagement add-on | Managed package install + number connection; typically live in under a day once the number is registered | Weeks: API wiring, webhooks, retries, compliance logic, monitoring |
| Where texts live | Salesforce messaging console with Omni-Channel routing | Directly on Leads, Contacts, Accounts, Cases, and custom objects | Wherever you build them to live |
| Salesforce requirements | Qualifying editions + Digital Engagement licenses | Works with standard editions; no add-on licenses | API access; architecture is up to you |
| Extras beyond SMS | Part of Salesforce Messaging channels | Often bundles WhatsApp, MMS, telephony/CTI, and AI in one package | Anything — you build it |
| Typical cost | Add-on licensing + carrier/number fees | Per-user subscription + carrier/number fees | Development and maintenance + per-message API fees |
A fair rule of thumb: if you only need service texting and already license Digital Engagement, evaluate native first. If you want texting across sales, service, and campaigns — with history on the record and no add-on licenses — an AppExchange app is usually the fastest path. A custom Twilio build makes sense only when your workflows genuinely don’t fit packaged tools and you can staff the ongoing engineering.
What do you need before you start?
- A number type decision. US options: a 10DLC long code (standard business texting), a toll-free number (simpler verification, good throughput), or a short code (highest volume, highest cost). Other countries use local long codes or alphanumeric sender IDs with their own rules.
- A2P 10DLC registration (US). Business texting over long codes requires registering your brand and campaign with The Campaign Registry. Unregistered traffic is filtered or blocked by US carriers. Toll-free numbers need their own verification instead.
- Salesforce admin access to install a package or enable the channel, plus a decision on which objects own conversations.
- An opt-in source. Where does consent come from — web forms, checkout, service interactions? It must be recorded on the Salesforce record before automation sends anything.
How to set up Salesforce SMS integration, step by step
- Choose your number type. 10DLC for standard US volume, toll-free for simpler setup, short code for massive scale — or local numbers/sender IDs internationally.
- Register for A2P compliance. Submit brand and campaign details for 10DLC (or toll-free verification). Start this first: it’s the pacing item, typically days to a few weeks.
- Choose the integration path. Use the comparison above — native, AppExchange app, or custom — based on clouds, licenses, timeline, and how much compliance tooling you want handled for you.
- Connect the number to Salesforce. For an AppExchange app: install the managed package and link the registered number in the app’s setup — no code. For native: enable the SMS channel in Messaging Setup and assign it to Omni-Channel.
- Configure routing and record matching. Queues or flows for service; owner assignment for sales; matching rules so inbound numbers attach to the existing Lead, Contact, or Case.
- Wire up consent, opt-out, and quiet hours. Opt-in status on the record, automatic STOP/HELP handling, and send-window rules — before launch, not after.
- Test real scenarios, then go live. Pilot one team: inbound replies, template sends, MMS, opt-outs, error states, and reporting — then roll out.
Shortcut: with a registered number in hand, WatBox’s Salesforce SMS app completes steps 4–6 through a guided, no-code setup — two-way texting, personalized bulk campaigns, MMS, automatic opt-out handling, and AI conversation summaries, all logged on the record alongside WhatsApp and calls. See the step-by-step deployment guide for screenshots of the full flow.
What does Salesforce SMS integration cost?
Three layers, whichever route you choose. First, number and registration fees: 10DLC brand/campaign registration carries small one-time and monthly fees, toll-free verification is typically free but slower, and short codes cost hundreds per month. Second, per-message carrier fees, usually a few cents per SMS segment (and more for MMS), billed by the messaging provider. Third, the integration layer: Digital Engagement add-on licensing for native, a per-user subscription for AppExchange apps (WatBox offers a 15-day free trial), or engineering time for custom builds. For most teams the integration layer dominates at low volume and carrier fees dominate at high volume.
Compliance rules that apply to every route
- Consent first. US law (TCPA) and carrier policy require opt-in before business texting; keep the proof on the Salesforce record.
- STOP means stop. Opt-out keywords must be honored automatically and immediately, across every campaign.
- Register or be filtered. Unregistered 10DLC traffic is throttled or blocked; registration isn’t optional for US long codes.
- Respect quiet hours. Several US states restrict texting windows; send-time rules belong in your automation.
- Identify yourself. Messages should name your business; misleading sender practices damage deliverability and invite complaints.
Frequently asked questions
Can Salesforce send and receive SMS?
Yes — via native Digital Engagement, AppExchange apps like WatBox, or custom SMS-API builds. All three text customers two-way and log conversations on Salesforce records.
Does Salesforce have built-in SMS?
Not in core editions — native SMS needs the Digital Engagement add-on with qualifying Service Cloud editions. AppExchange apps work with standard editions, which is why many teams start there.
What is A2P 10DLC and do I need it?
The US carrier framework for business texting over standard long codes. If you text US customers from a long code, brand and campaign registration is effectively mandatory — unregistered traffic gets filtered.
How long does it take?
Software: under a day with an AppExchange app. Compliance is the pacing item — 10DLC or toll-free verification typically takes days to a few weeks. Start registration first.
Can I send bulk SMS campaigns from Salesforce?
Yes — apps like WatBox run personalized bulk and drip campaigns from Salesforce lists, with merge fields, opt-out suppression, and delivery reporting on the record. See bulk SMS for Salesforce.
Where do SMS conversations appear in Salesforce?
Native: the Salesforce messaging console with Omni-Channel routing. WatBox and similar apps: directly on the Lead, Contact, Account, Case, or custom-object record — alongside WhatsApp and call history.
Next steps
Start your number-type and 10DLC decisions now — they gate every route. For the adjacent channel, see the Salesforce WhatsApp integration guide; texting and WhatsApp share the same consent and routing disciplines, and many teams deploy both together. And if the managed-app route fits, explore WatBox’s SMS app or start the 15-day trial — most teams send their first text from Salesforce the same week their number clears registration.