We are at Dreamforce 2026, Industry Pavilion at San Francisco
January 26, 2026
To set up SMS in Salesforce Digital Engagement, you need six things in order: the Digital Engagement add-on license, A2P 10DLC brand and campaign registration if you are texting US numbers, Messaging turned on in Service Cloud, the Messaging User permission set license assigned, an SMS messaging channel linked to your provisioned number, and Omni-Channel routing so someone actually receives the texts.
Most guides skip the second item, and it is the one that delays go-live. Carrier registration for US business texting takes days to weeks and runs in parallel with your build, so start it first. Below is the full sequence, the routing and automation setup, the consent rules, and the reasons your first test message will not send.
Digital Engagement is not part of standard Service Cloud. It is a paid add-on, and messaging carries usage-based consumption on top of the per-user license.
Confirm three things before you plan a timeline.
On cost, be careful with numbers you read elsewhere. Digital Engagement is licensed per user with conversation-based consumption on top, and third-party posts quoting specific figures are often out of date or arguing for their own product. Get current pricing from Salesforce directly. For a vendor-neutral overview of what the add-on covers, Salesforce Ben has a useful explainer.
This decision affects registration time, throughput, and how customers perceive you. Decide before you provision anything.
For Service Cloud support conversations, a 10DLC long code is usually right. Salesforce publishes guidance specifically for creating long code SMS channels in the US and Canada, which tells you how standard that path is.
Start here, not last. If you are sending to US mobile numbers, carriers require A2P 10DLC registration: you register your organization as a brand, then register the campaign describing what you will send and why.
Salesforce documents this process for Digital Engagement, including requesting a brand for a 10-digit long code. Expect to supply your legal entity details, tax identifier, website, a description of your messaging use case, and sample messages.
Two practical points. Unregistered or poorly registered traffic gets filtered or blocked by carriers, so this is not paperwork you can defer. And approval timelines are outside Salesforce's control, which is why the entire industry advertises faster registration as a selling point.
The older Letter of Authorization step still exists where you are porting or hosting an existing number, but do not confuse the two. An LOA proves you control a number. 10DLC registration is what makes carriers willing to deliver your messages.
Run registration as a parallel workstream from day one. Your build can proceed while it clears.
With licensing sorted, the in-org setup is quick.
Go to Setup, open Messaging Settings, and enable Messaging. Then assign the Messaging User permission set license to your admins and agents. Skip that assignment and the Messaging tabs simply do not appear, which is the most common reason a setup looks broken on day one.
Also confirm each agent has the underlying Service Cloud user access they need. Permission layering is where these setups quietly fail, and getting it right is ordinary Salesforce administration work. Guidance from Salesforce Admins is a good reference for permission set license patterns.
Now connect the number. In Messaging Settings, create a new channel, choose SMS, and link the provisioned number.
Give the channel a name your team will recognize in routing rules later. "Support SMS US" ages better than "Channel 1" once you add a second number or a second region.
Configure the channel's business hours and its automated responses at this point. An out-of-hours auto-reply that sets a realistic expectation prevents most of the "nobody answered me" complaints that follow an SMS launch.
A connected channel does not mean anyone is answering. Omni-Channel decides who receives each conversation.
Create a queue dedicated to SMS support, then build a routing configuration that points at it. The part worth thinking about is capacity, because messaging behaves differently from voice or email.
The capacity model is the setting teams get wrong. An agent can hold one phone call, but several text conversations, because customers reply on their own schedule. Set the numbers too high and every conversation gets slow replies; too low and you queue customers who could have been served.
Manual replies handle the conversation. Flow handles the predictable parts: acknowledgements, status updates, appointment reminders, case-closed confirmations.
Which channel type you have changes how you build the automation, and this trips up admins who follow a tutorial written for the other one.
On enhanced channels, the flow has to check whether a Messaging End User record exists for that phone number, and create one if it does not. That record carries the consent status.
This is not bookkeeping. The consent status on that record is your audit trail showing you had permission to message that person, which is exactly what you will be asked to produce if a complaint arrives. Build the create-if-missing step into every outbound flow rather than assuming the record is there.
Wiring these flows into your case lifecycle is standard Service Cloud implementation work. If your team is new to record-triggered flows, the Trailhead modules on Flow are the fastest way in.
SMS lands on a lock screen between messages from someone's family. The regulatory framework reflects that.
In the US, TCPA governs consent for business texting, and the penalties are per message. Three requirements are non-negotiable: get and record consent before the first message, honor opt-out keywords immediately and permanently, and keep records that prove both.
Salesforce recognizes standard opt-out keywords and stops outbound messages to that recipient. Do not build around that behavior or try to re-engage an opted-out number through a different channel record. Test the opt-out path before launch, the same way you test the send path.
Two more practical guards. Respect quiet hours, because a 6 a.m. service notification generates complaints regardless of legality. And keep your message content clean, since carriers filter aggressive sales language and suspicious shortened links whether or not you are registered.
Almost every Digital Engagement SMS launch hits at least one of these. None are exotic.
The sandbox-to-production row deserves emphasis, because it is a genuine trap reported repeatedly by admins: a phone number that works in a sandbox without the country code can fail in production without it. Store numbers in full international format from the start and the problem never appears.
Keeping these paths healthy after launch, especially as numbers and campaigns change, is what ongoing managed services cover. Practitioner threads in the Trailblazer Community are where most of these gotchas surface first.
This choice comes up constantly, and the honest answer is that it depends on which job you are doing.
Native Digital Engagement wins for service. Conversations route through Omni-Channel, land next to case history in one console, and the whole thread is stored in Salesforce. Agents do not switch tabs, and reporting sits with your other service metrics.
Third-party apps often win for outbound volume. Marketing-style campaigns, drip sequences, and bulk sends are what those products are built for, and several are Salesforce-native packages with their own conversation objects and campaign builders.
The failure mode is buying one for the other's job: running support through a bulk-SMS tool that lives outside the agent console, or trying to run high-volume marketing sends through a service channel. If you end up with both, plan the data model deliberately so conversation history does not fragment. That planning is integration architecture work rather than an app install.
Yes. Service Cloud supports SMS through the Digital Engagement add-on, which routes conversations to agents via Omni-Channel and stores the full thread against the customer record. AppExchange apps are the alternative, and they suit outbound campaign use cases better.
Yes. Digital Engagement is a paid Service Cloud add-on, and each agent also needs the Messaging User permission set license. Messaging volume carries usage-based consumption on top of the per-user cost, so confirm current rates with Salesforce.
A2P 10DLC is carrier registration for application-to-person texting on 10-digit long codes. If you send to US mobile numbers, you register your brand and then your campaign. Without it, carriers filter or block your messages. Start registration before your build, since approval time is outside your control.
Messaging sessions are created automatically when a conversation starts on a configured channel, either because a customer texts your number or because an outbound message opens a conversation. If sessions are not appearing, check the channel configuration and your Omni-Channel routing before anything else.
The most common cause is phone number formatting. Numbers stored without the country code can behave differently between environments. Store every number in full international format, including +1 for the US, and test the outbound path in production with a real handset.
The in-org configuration, channel, routing, and a first flow is typically a few days of work for a capable admin. The schedule is usually set by 10DLC registration, which can run from several days to a few weeks. Sequence registration first and build in parallel.
The technical setup for SMS in Digital Engagement is not the hard part. Enable Messaging, assign the permission set license, create the channel, configure Omni-Channel, and build a flow or two.
What determines your launch date is carrier registration, and what determines whether the channel works is the unglamorous detail: capacity set from reality, consent recorded on Messaging End User records, opt-out paths tested as carefully as send paths, and phone numbers stored in full international format.
At Minuscule Technologies we run these launches in that order, so registration clears while the build proceeds and nobody discovers the sequencing problem in launch week. Talk to our Service Cloud team about scoping your Digital Engagement SMS rollout, including the registration track.
You've seen what's possible. Now, let's make it happen for your business. Whether you need an end-to-end Salesforce solution, a complex integration, or ongoing managed services, our team is ready to deliver.
Schedule a Free Strategic Call
