In short
- Keep one Approved to SMS field on every record a rep can text from.
- Set it from consent captured on the form, with clear consent wording next to the checkbox.
- Have the Send SMS widget check the field before sending, and block the text if it is not approved.
- Turn on field history for the field, so you can see who changed it and when.
Why an SMS opt-in field in Salesforce
Reps text from Salesforce because it is fast. Speed is also the risk: a rep can text a number that did not agree to receive texts. Training helps. A check built into the tool helps more.
The Approved to SMS pattern puts consent in one field and makes the texting tool respect it. No one has to remember the rule. The widget enforces it.
1. Add the Approved to SMS field
- Add a checkbox or picklist named Approved to SMS on Lead, Contact, Account and Opportunity, wherever reps send texts.
- Map it on lead conversion, so consent follows the person from lead to contact and opportunity.
- Put it on the page layouts near the phone fields, so reps see it.
- Add a date field for when consent was given, and the source (form, call, text reply).
2. Capture SMS consent on your forms
Consent starts on the website. Add an SMS opt-in checkbox to the forms that collect phone numbers, with plain consent wording next to it. Link to your SMS terms and your privacy policy.
- Keep the checkbox separate from the submit button. Consent should be its own choice.
- Map the checkbox to the Approved to SMS field in Salesforce, and test it with a real submission.
- Update the consent wording and the privacy policy together when either one changes.
3. Enforce the opt-in in the Send SMS widget
Our Send SMS widget is a Lightning Web Component on the record page, wired to your SMS platform. Before it sends, it checks the Approved to SMS field.
Approved
The rep writes or picks a message and sends it. The text and the reply land on the record.
Not approved
The send button is blocked and the widget tells the rep why. The rep can see the history but cannot start a new text.
Opted out
When the person replies with an opt-out keyword, the field is set back to not approved, and the widget blocks further sends.
Outbound number logic sits in the same place, so each text goes out from the right number for that team or location.
Talk through your project
A free call about your integration, your CRM or whatever you are stuck on. Honest advice, even if you never hire us. No obligation.
4. Keep a history of opt-in changes
Turn on field history tracking for Approved to SMS. Salesforce then records the old value, the new value, who changed it and when. Pair it with the consent date and source fields, and you can answer the question "when did this person agree?" from the record.
5. Test the automation around the opt-in field
Flows that set or clear the opt-in field run on records that may have other rules. A validation rule on the opportunity can stop an opt-out flow from saving. Test opt-in and opt-out on leads, contacts and opportunities, and set up error emails for the flows.
Respect privacy laws and cookie consent
Tracking only holds up if it respects the people you track. Privacy laws and browser rules keep tightening, and a cookie banner that does nothing is not enough.
- Ask before you track: analytics and ad cookies wait until the visitor accepts, with an easy way to say no.
- Use Google Consent Mode, so Google tags follow the visitor’s choice.
- Honor Global Privacy Control: a browser that sends it is treated as a no.
- Let visitors change their mind later, from a cookie settings link in the footer.
- Keep your privacy policy and SMS consent wording in step with what you collect and send.
This is how we set up tracking on our own sites and for clients. It is general guidance, not legal advice: check the rules that apply to your business with your legal team.
Where to start
Start with the field and the form checkbox, then turn on the widget check. Book a free call and we will walk through your texting setup with you.
Want help with this?
Book a free call about your CRM, integrations or reporting, or map your systems first with our free tech stack diagram builder.
