Discover why organizations that text on Salesforce trust ForceMessage to manage SMS opt-in, opt-out, age checks, and compliance—automatically across Chat UI, Bulk UI, Notifications, and the Message Inbox.
-
›
Automatic Opt-In Requests -
›
One-Word START/STOP Control -
›
Age-Aware Protection -
›
Works Across All Components
ForceMessage Makes SMS Consent Easy in Salesforce
Turn SMS Consent From a Manual Job Into an Automatic Flow
Without ForceMessage, someone has to manually track who has opted in, who has opted out, and whether you’re allowed to text them via SMS. That’s slow, error-prone, and risky.ForceMessage turns SMS consent into an automatic, rule-driven flow that runs entirely inside Salesforce—so your team can focus on conversations, not compliance.
Automatic Opt-In Requests
When a Contact is created, ForceMessage does the consent work for you.
As soon as a Salesforce user creates a Contact and fills in:
-
âś”
A valid phone number in +countrycode format (e.g., +91…) -
âś”
Consent to Contact (not empty) -
âś”
Message Channel -
âś”
Message Opt Out = true (checked for safety by default)
Simple START = Opt-In
Contacts only need one word to say “yes”: START.
-
âś”
Any case works: start, Start, START -
âś”
The moment ForceMessage sees START: -
âś”
Two-way SMS messaging is enabled -
âś”
Chat UI can send outbound SMS -
âś”
Bulk UI can include the contact in campaigns -
âś”
Notifications and Inbox start capturing their replies -
âś”
The Message Opt Out field stays available for filtering in Bulk UI
STOP = Hard Block (With Re-Opt-In)
STOP is always respected—instantly.
When a contact replies STOP:
-
âś”
All SMS sending to that contact is blocked -
âś”
Chat UI will not allow agents to send SMS -
âś”
Bulk UI automatically excludes them from every send -
âś”
The opt-out message is logged in both Chat and Inbox
If they change their mind later, they just send START again:
-
âś”
SMS is re-enabled -
âś”
Chat UI, Bulk UI, Notifications, and Inbox all resume as normal -
âś”
A new consent event is written to your audit trail
Built-In Safety for Under-18 Contacts and Compliance Teams
ForceMessage doesn’t just send messages—it helps you protect younger contacts and prove that you followed the rules. Every key SMS consent event is checked, enforced, and logged inside Salesforce for future audits..
Age-Based SMS Restrictions
ForceMessage quietly checks age before every SMS sent from Chat UI. It looks at Date of Birth and Age Consent, and shows a red Under-18 warning whenever the age is unknown, under 18, or 18+ without consent—so you don’t message minors by mistake.
Guided Acknowledgement Flow
When an age alert appears, agents follow a simple, safe flow: they acknowledge the warning, choose a reason for sending, and ForceMessage automatically logs an Age_Restriction_Consent__c audit record for compliance.
One Rule Set, All Components
You never have to worry about which part of ForceMessage is compliant—all of it is. The same consent rules power Chat UI, Bulk UI, Notifications, and Message Inbox, so START/STOP is always enforced, every send is filtered by real opt-in status, and every consent message is stored for easy review.
Compliance That’s Easy to Show
Because everything lives in Salesforce, consent is always easy to prove. START/STOP and other consent events are stored on the contact record, age restrictions are logged as audit entries, and if someone asks “Did we have permission to text this person?” you can answer in seconds.