It’s important to comply with and follow SMS rules and regulations when using SMS to communicate with your Customers in Gladly. SMS communications regulations must be followed to avoid penalties or SMS deliverability issues. These laws and regulations include, but are not limited to:
CAN-SPAM Act – Protects consumers from receiving SMSes from companies with whom they have no relationship.
California Consumer Privacy Act (CCPA) – Gives consumers information on what personal data is collected and how it’s used, the right to delete personal data and more.
Telephone Consumer Protection Act (TCPA) – Limits the use of automated tools and requires businesses to get explicit — and documented — consent before an SMS is sent. Even if your company has a relationship with the recipient, you may only SMS if there is explicit opt-in consent.
We strongly suggest you seek legal counsel to review your SMS programs and policies to ensure compliance with SMS laws, regulations, and guidelines. To help you with this, we have created general guidelines and best practices to recommend you follow when using SMS to communicate with Customers in Gladly.
Include opt-in language in your ‘Contact Us’ web page. #
Receive consent by including opt-in language in places where you advertise the phone number that Customers can text to contact you. Using Retalé (a faux company) as an example, you could add the following language to your “Contact Us” web page on your website or mobile application next to your phone number:
“By texting us, you consent to receive text messages from Retalé at the mobile number you used to text and you are opting-in to receive future messages or a phone call in the number you provided. Message & Data rates may apply. Reply STOP anytime to opt-out.”
They consent to receive a response by SMS by proactively reaching out first, but they provide consent for that exchange only and not for future communications.
If you plan on using their number to reach out through SMS proactively, you must include information on your Contact Us page on how you may use their information in future SMS communications. For example:
“Prefer to message us instead? Text us at 555-555-5555 if you need help. By texting us, you consent to receive text messages from Retalé at the mobile number you use to text and you are opting-in to receive future messages or a phone call in the number you provided. Message & Data rates may apply. View our Terms and Privacy Policy for more information”
You should also ensure that your Privacy Policy clearly states your communication practices.
An Agent can transition an email/chat/phone call to SMS or use SMS as another Channel to communicate (e.g., send a confirmation number) while using another Channel like Voice.
When Customers send an SMS to your company to ask questions or seek help, that’s considered an opt-in. They consent to receive a response by SMS by proactively reaching out first; however, the consent is for that exchange only.
Your initial reply to their SMS — whether through the auto-reply Rule or a manual Agent response — must contain your company’s name and opt-out language. For example:
Thanks for contacting Retalé. How can we assist you today? By texting us, you are opting-in to receive future messages or a phone call from Retalé at this number. Message & Data rates may apply. Reply STOP at any time to opt-out.
In Gladly, a Customer reaching out via SMS for the first time automatically makes their phone number SMSable by marking the SMS tag on their phone number. Still, it would be best if you do not initiate reaching out to the Customer via SMS unless you have explicitly provided information about opting in to receive support via SMS, which may mean receiving other kinds of communications in the future. In this case, your SMS initial reply via a Rule using a Messaging Answer should include a link to your Privacy Policy that contains information on how their phone number may be used for future communications. For example:
Hello! Thanks for contacting Retale. We’ll get back to you as soon as we can. By texting us, you consent to receive text messages from Retalé in the mobile number you used to text and you are opting-in to receive future messages or a phone call in the number you provided. Message & Data rates may apply. Reply STOP anytime to opt-out.
Always include your company name in the initial SMS reply to ensure your Customer understands that they have contacted and consented to the right company. Also, notice there is an opt-out keyword (STOP). You must always include an opt-out language in the initial reply. It’s easy for regulators to see, filter, and flag messages that do not have this type of language.
You don’t necessarily need to keep your opt-out language in subsequent SMSes. For example, after receiving the initial response, “Hello! Thanks for contacting Retalé. We’ll get back to you as soon as we can. Message & Data rates may apply. Reply STOP to opt-out,” an Agent may then reply and say:
Agent: Hello, Chip! Thanks for contacting Retalé. My name is Gerard, and I’m happy to confirm that your order is ready for pickup.
Customer: Thank you!
Agent: Chip, I can confirm that your order is ready for pick up at the Union Square location.
In the example above, the subsequent replies did not need to include the opt-out language.
Just because Customers have texted you in the past does not necessarily mean they permit you to message them later for other reasons. If you do, make sure your Customers are aware of your Privacy Policy which should contain information that you may use their information for future communications until they opt-out. Consult your legal team or seek legal assistance in defining your policy.
Customers can opt-out of future messages anytime by replying with an opt-out keyword like “STOP.” This opts them out of receiving messages from the phone number they opted out of. Customers must resubscribe to receive any SMS messages from the same phone number. Remember always to have an opt-out language in your initial text message.
Tip – Agent experience for SMS opt-outs
See Opt-Out of SMS Messages to understand what Agents see in the Customer Profile when Customers opt-out.
Automation partners respond to inbound messages in which a Customer sending an SMS provides consent to receive support by SMS. But, the initial response to the SMS must contain your company’s name and opt-out language. For example:
Hello! Thanks for contacting Retalé. How can we help you? Message & Data rates may apply. Reply STOP to opt-out.
Only proactively sends SMS to Customers who have previously consented to receive texts from your company. Customers typically give consent if they have texted you in the past and have not opted out. Still, you should only proactively SMS Customers if they consented to receive your messages.
Customers’ initial messages from automation partners or SMS API should contain your company name and an opt-out language. For example:
Thanks for joining Retalé messaging for Platinum Members! Get ready to shop till you drop with amazing deals for our Platinum Members. Message & Data rates may apply Reply STOP to opt-out.
Having your company name on the initial SMS response ensures your Customer understands that they have contacted and consented to the right company. Also, notice there is an opt-out keyword (STOP). You must always include an opt-out language in the initial reply.
The IVR to SMS option allows Customers to transition from phone support to SMS. This option is typically presented to Customers in the IVR to reach an Agent.
Customers given the option to receive support by SMS through the IVR must explicitly be given the opt-out language, which would be through a recorded message or text-to-speech in a node. For example, your IVR menu recording may say:
To receive support through SMS instead, press one. By pressing one, you agree to receive messages from us from the number you’re calling from. Note that message and data rates may apply, and you may reply with the word STOP to opt-out of SMS communications at any time.
Upon opting in to receive support via SMS, include an opt-out language in the initial SMS sent to callers confirming their request to receive support via SMS. For example, the SMS auto-reply may say:
Thanks for contacting Retalé. How can we assist you today? By texting us, you are opting-in to receive future messages or a phone call from Retalé at this number. Message & Data rates may apply. Reply STOP at any time to opt-out.
Having your company name on the initial SMS response ensures your Customer understands that they have contacted and consented to the right company. Also, notice there is an opt-out keyword (STOP). You must always include an opt-out language in the initial reply.
Proactive SMS is a tool used to communicate with Customers via SMS in bulk, allowing you to send the same message to multiple Customers at once. Because it uses SMS, it’s bound by the same rules and regulations as other SMS Channels.
Watch Out – Proactive Conversation features do not replace marketing tools
Proactive Conversation tools like Proactive Email and Proactive SMS allow you to quickly communicate pertinent information to Customers. Still, it’s not meant to replace mass, marketing-type outbound communication to Customers which is a more appropriate use case for tools like MailChimp (email) and Attentive (SMS).
You should only use Proactive SMS to communicate with Customers who have previously provided consent to receive other communications from you. Typically, consent is given if the Customer has previously reached out via SMS and has received your initial SMS response with the opt-out language and link to your Privacy Policy on how you may contact them for future communications.
Refrain from including recipients who don’t have a relationship with your company or have not provided consent.
The Messaging Answer used in each Proactive Campaign should contain an opt-out language. For example:
Your maintenance contract with Relaté is about to expire. If you’d like an extension, reply to this message so we can assist. Reply STOP to unsubscribe.
Having your company name on the message ensures your Customer understands who’s contacting them. Also, notice there is an opt-out keyword (STOP). You must always include an opt-out language in a Proactive SMS Messaging Answer. If they do opt-out, you will no longer be able to communicate through SMS until they opt-in again.
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
__cf_bm
29 minutes
This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
_wpfuuid
1 year 1 month 4 days
This cookie is used by the WPForms WordPress plugin. The cookie is used to allows the paid version of the plugin to connect entries by the same user and is used for some additional features like the Form Abandonment addon.
BIGipServer*
session
Marketo sets this cookie to collect information about the user's online activity and build a profile about their interests to provide advertisements relevant to the user.
cookielawinfo-checkbox-advertisement
1 year
Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category.
cookielawinfo-checkbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
CookieLawInfoConsent
1 year
CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie.
PHPSESSID
session
This cookie is native to PHP applications. The cookie stores and identifies a user's unique session ID to manage user sessions on the website. The cookie is a session cookie and will be deleted when all the browser windows are closed.
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Cookie
Duration
Description
li_gc
5 months 27 days
Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes.
lidc
1 day
LinkedIn sets the lidc cookie to facilitate data center selection.
UserMatchHistory
1 month
LinkedIn sets this cookie for LinkedIn Ads ID syncing.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie
Duration
Description
_ga
1 year 1 month 4 days
Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors.
_ga_*
1 year 1 month 4 days
Google Analytics sets this cookie to store and count page views.
_gd_session
4 hours
This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded.
_gd_visitor
1 year 1 month 4 days
This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads.
_sp_id.*
1 year 1 month 4 days
Snowplow sets this cookie to store user information that is created when a user first visits a site and is updated on subsequent visits.
_sp_ses.*
30 minutes
Snowplow sets this cookie to store user information that is created when a user first visits a site and is updated on subsequent visits.
AnalyticsSyncHistory
1 month
Linkedin set this cookie to store information about the time a sync took place with the lms_analytics cookie.
mf_user
3 months
Mouseflow sets this cookie to identify whether a visitor is new or returning.
vuid
1 year 1 month 4 days
Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie
Duration
Description
_mkto_trk
1 year 1 month 4 days
This cookie, provided by Marketo, has information (such as a unique user ID) that is used to track the user's site usage. The cookies set by Marketo are readable only by Marketo.
bcookie
1 year
LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs.
bscookie
1 year
LinkedIn sets this cookie to store performed actions on the website.
li_sugr
3 months
LinkedIn sets this cookie to collect user behaviour data to optimise the website and make advertisements on the website more relevant.