SMS
SMS delivery through enterprise carriers with Salesforce-native consent, history, and analytics.
Configuration
| Setting | Detail |
|---|---|
| Provider | Twilio, Azure Communication Services, or custom adapter |
| Sender | Long code, short code, toll-free, or alphanumeric sender ID |
| Registration | 10DLC brand and campaign registration required for US traffic |
| Consent | Explicit opt-in required before the first message |
Send from Apex
RME_Message.builder()
.channel('SMS')
.toPhone('+14155550142')
.toContact(contactId) // links history + applies consent
.body('Your appointment is confirmed for Thursday at 2:00 PM. Reply STOP to opt out.')
.send();
Send from Flow
Use Send Message (RME) with Channel = SMS and either a template or a text body. Store the returned Message Id to relate follow-up records.
Inbound and keywords
Inbound messages are written as Message__c records with Direction__c = Inbound and matched to a Contact by phone number.
| Keyword | Effect |
|---|---|
| STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT | Sets SMS consent to opted out |
| START, UNSTOP, YES | Restores SMS consent |
| HELP, INFO | Sends the configured help response |
Keyword handling is enforced by RME before any custom automation runs, so an opt-out can never be overridden by a Flow.
Character limits and segmentation
GSM-7 messages segment at 160 characters (153 per part when concatenated); any non-GSM character forces UCS-2 at 70 characters (67 concatenated). RME reports Segments__c on every message so cost reporting is accurate.
Quiet hours
Set quiet-hour windows per country on the channel policy. Messages requested inside a quiet window are scheduled for the next permitted time rather than dropped — see Message Scheduling.
Continue to RCS.
Was this helpful?
Last updated 1 month ago