LogoLogo
Get a demoLog inAcademyDevelopersMore docs
  • Bird CRM docs
    • Explore all products
    • Use cases
      • Bird for travel
        • Abandoned search recovery
        • Flight confirmation
        • Holiday search campaigns
        • Price change alerts
    • About Bird CRM
  • Inbox
    • Inbox
      • Concepts
        • Reports
      • Admin guide
        • Agents
          • Invite an agent to Inbox
          • Remove an agent from Inbox
          • FAQs
        • Tags
        • Routing
        • Teams
        • Feeds
        • Sender profiles
        • Reporting
      • Agent guide
        • 📚1. The basics
        • ⏰2. Your availability status
        • ✉️3. Send and receive messages
        • 💬4. Manage conversations
        • 👥5. View conversation participants
        • 👤6. View a contact's profile
  • Campaigns
    • Campaigns
      • Quickstarts
        • Send a campaign
      • Concepts
        • A/B tests
          • FAQs
        • Branded links
        • Calendar view
        • Campaign tags
        • Frequency limits
        • Scheduling
      • How-to
        • Schedule a campaign
        • Run an A/B test
        • Replicate a campaign
    • WhatsApp campaigns
      • How-to
        • Send a WhatsApp campaign
    • Email campaigns
      • How-to
        • Send an email campaign
    • SMS campaigns
      • Concepts
        • Best practices for MMS campaigns
      • How-to
        • Send an SMS campaign
    • Push notifications
      • How-to
        • Send a push notification campaign
  • Automation
    • Journeys
      • Quickstarts
        • Create an abandoned cart recovery journey
      • Concepts
        • Journey templates
        • Journey runs
        • Journey insights
        • Journey reports
      • How-to
        • Use a send message step in a journey
        • Use a wait step in a journey
        • Use a conditional step in a journey
        • Use an update contact step in a journey
        • Use an end journey step in a journey
    • Flows
      • Quickstarts
        • Use template flows
        • Build an inbound flow
      • Concepts
        • Capabilities and limitations
        • Triggers
          • Agent triggers
          • Connector triggers
            • HubSpot triggers
          • Contact triggers
          • Conversation triggers
          • Feed item triggers
          • Message lifecycle triggers
          • Voice triggers
          • Webhook triggers
          • HTTP endpoint trigger
          • WhatsApp flow endpoint trigger
        • Actions
          • Bird API actions
            • Bots actions | API
            • Channel actions | API
            • Collaboration actions | API
            • Conversation actions | API
            • Engagements actions | API
            • Number management actions | API
          • Core actions
            • How to set up global variables in Flows
          • Contact actions
          • Channel actions
          • Conversation actions
          • Connector actions
            • HubSpot actions
            • Open AI actions
          • Voice actions
      • How-to
        • Route conversations based on language
        • Route conversations based on sentiment
        • Set up a business hours auto-responder
        • Create a simple auto-responder
        • Set up conversational marketing
        • Create an FAQ bot
    • Approval Flow
  • Audience & Contacts
    • Sign-up forms
      • Quickstarts
        • Create a sign-up form
        • Create quizzes
      • Concepts
        • Sign-up process
        • Display
        • Colors
        • Targeting
        • Languages
        • Sign-up form analytics
    • Lists and segments
      • Quickstarts
        • Create a segment
      • Concepts
        • Segments
        • Lists
      • How-to
        • Create a segment based on contact activity
        • View contacts in a segment
        • Edit the setup of a segment
        • Delete a segment
        • Create a list
    • Contacts
      • Concepts
        • Contacts
        • Contacts directory
        • Contact profiles
        • Consent and subscriptions
          • Suppressions
          • Managing unsubscribes
          • Opt-ins, consent, and subscription statuses
            • Contacts with a 'blank' subscription status
      • How-to
        • Add contacts
        • Update the subscription status of your existing contacts
        • Send marketing campaigns to contacts with a 'blank' subscription status
        • Export contacts
  • Content
    • Email templates
      • Concepts
        • Email content, styling, and personalization
        • Email design best practices
        • Advanced Email Templating
      • How-to
        • Create an email template
        • Import a custom HTML email
        • Use a prebuilt email template
        • Create personalized abandoned cart, browse and order placed emails
    • Message templates
      • Quickstarts
        • Create a message template
      • Concepts
        • Localization
        • Versioning
        • WhatsApp message templates
          • WhatsApp approved message templates
          • Reply to open conversation message template
          • Commerce messages
        • Apple Messages for Business
        • Push notifications
      • How-to
        • Localize a message template
        • Add variables to a message template
        • Create an SMS message template
        • Apple Messages for Business
          • Use dynamic variables in Apple Messages templates
          • Create a text Apple Messages template
          • Create an image Apple Messages template
          • Create a location Apple Messages template
          • Create a file Apple Messages template
          • Create a rich link Apple Messages template
          • Create a list picker Apple Messages template
          • Create authentication Apple Messages message types
          • Create a quick reply Apple Messages template
          • Create a time picker Apple Messages template
          • Create an iMessage App message template
          • Create a payment Apple Messages template
        • WhatsApp message templates
          • Create a WhatsApp approved message template
          • Create a reply to open conversation WhatsApp message template
          • Create a single product WhatsApp message template
          • Create a catalog WhatsApp message template
          • Create a coupon WhatsApp message template
          • Create an action WhatsApp message template
          • Create a limited time offer WhatsApp message template
          • Create a carousel WhatsApp message template
          • Create Approved WhatsApp Flows Template
          • Create reply to open conversation WhatsApp Flows Template
        • Create Push Notifications message templates
    • Chat widgets
      • Concepts
        • Send and receive messages
      • How-to
        • Build and install a chat widget on a Shopify store
        • Build and install a chat widget on your website
    • Media Library
      • How to Upload Images to the Media Library
    • Translation files
      • Creating and using translation files
    • External Data Sources
    • Lookup Tables
    • Discounts
    • Lookup tables
      • Managing lookup tables
      • Using lookup tables in Flows
    • Products
      • Custom Product Catalog Source
  • Analytics
    • Analytics
      • Concepts
        • Reporting metrics
        • Understanding the Attribution Model
        • List-unsubscribe in email headers
        • Understand Open Tracking
    • Channel analytics
      • Concepts
        • Channel logs
      • How-to
        • Analyze the performance of your channels
    • Campaign reports
      • Concepts
        • WhatsApp campaign reports
        • Email campaign reports
        • SMS campaign reports
      • How-to
        • View campaign reports
        • View A/B test campaign reports
        • See an overview campaign performance
  • Channels
    • Channels
      • Concepts
        • Quiet hours
      • Quickstarts
        • Find and install a channel
        • View information about an installed channel
        • View Channel Logs
      • Supported channels
        • Apple Messages for Business
          • Quickstarts
            • Install Apple Messages for Business
            • Use Apple Messages for Business
          • Concepts
            • Typing indicators
            • User device capabilities
          • How-to
            • Complete onboarding
            • Use entry points
            • Route messages
            • Send messages
            • Use Apple Pay
        • Email
          • Install email
          • Forwarding emails from Gmail
          • IP pools
          • Configure BIMI
        • Facebook Messenger
          • Install Facebook Messenger
          • Use Facebook Messenger
          • Facebook Messenger message types
        • Instagram Messaging
          • Install Instagram Messaging
          • Use Instagram Messaging
          • FAQs and Best Practices
          • Instagram message types
        • LINE
          • Install LINE
        • LinkedIn Pages Messaging
          • Install LinkedIn Pages messaging
          • Use LinkedIn Pages Messaging
          • LinkedIn Pages Messaging Types
        • Numbers
          • Quickstarts
            • Find and buy a new number
            • Activate a number
          • Concepts
            • Number types
            • Know-Your-Customer (KYC)
            • Activation, approval, and rejection
            • Number restrictions in China
          • How-to
            • Use a number
            • Cancel a number
            • Troubleshooting
            • FAQs
        • Push notifications
        • Google RCS
          • Create a Google RCS agent and install Google RCS as a channel
          • Testing and launching your agent
          • Create a Google RCS message template
          • RCS message template types
          • Create and send a Google RCS campaign
          • Create an RCS lead nurture journey with a fallback
          • Use RCS with an AI Agent
          • Grow RCS subscribers with a sign-up form
        • SMS
          • Quickstarts
            • Install SMS
            • Toubleshoot SMS Deliveries Faliures
            • (Missing) SMS delivery status
            • Troubleshoot Channel Health
          • Concepts
            • SMS parts and message length
            • SMS message types and compliance
            • Opt-in and opt-out compliance
            • Choose the right sender : Availability and restrictions by country
              • SMS Country Information Guide: Africa (A-L)
              • SMS Country Information Guide: Africa (M-Z)
                • South Africa
                • Nigeria
              • SMS Country Information Guide: Asia (A-K)
                • Japan
                • India
                • China
              • SMS Country Information Guide: Asia (L-Z)
                • Malaysia
                • Singapore
              • SMS Country Information Guide: Caribbean
              • SMS Country Information Guide: Central America
              • SMS Country Information Guide: Europe (A-M)
              • SMS Country Information Guide: Europe (N-Z)
              • SMS Country Information Guide: Middle East
                • United Arab Emirates
              • SMS Country Information Guide: North America
                • Messaging Best Practices - NORAM SMS / MMS
                • Canada
                • United States
                • Prohibited Content - NORAM SMS / MMS
              • SMS Country Information Guide: Oceania
                • New Zealand
                • Australia
              • SMS Country Information Guide: South America
            • MMS sizes and limitations
            • Automatic sender selection
            • SMS Registration
              • Use case requirements for SMS Registration
              • Setting up a SMS consent flow
              • SMS Privacy Policies
              • SMS Toll-free number
                • TFN Verification
                • Additional Costs for using TFN
                • How-to Guides
                  • Purchase a Toll Free Number via Bird
                  • Register a US or Canadian TFN for SMS via Bird
              • SMS 10DLC
                • How-to Guides
                  • Purchase a 10DLC number via Bird
                  • Register a 10DLC brand via Bird
                  • Register a 10DLC campaign via Bird
                  • Install SMS 10DLC
                  • Delete inactive 10DLC campaigns to avoid additional charges
                • Throughput and Daily Caps
                • Brand registration
                • Campaign registration
                • Additional costs for using 10DLC
                • 10DLC FAQs
            • Page 1
        • WhatsApp
          • Quickstarts
            • Before you start
            • Install WhatsApp
          • Concepts
            • WhatsApp for Business
            • Accounts and verification levels
              • Verified Facebook Business Manager Account
              • Official WhatsApp Business Account (Green tick)
            • Use WhatsApp
            • WhatsApp message types
            • WhatsApp's Customer Care Window
            • FAQs
          • How-to
            • Verify your Facebook Business Manager Account
            • Set up commerce messaging
              • Product inquiries
              • Product orders
            • Create a WhatsApp Flow
              • Create a flow
              • Testing your flow
              • Publishing and sending your flow
              • Handling Flow submission
            • Enable conversational components
            • Become a WhatsApp Tech Provider
              • Onboard as a Tech Provider
              • Connecting to Bird as solutions provider
              • Meta Tech Partner Migration 2024
        • Telegram
          • Install Telegram
          • Bot commands setup
  • AI
    • AI
      • Quickstarts
        • Create an FAQ model
        • Build a detect intent model
      • Concepts
        • AI Assistants
          • Agent Assistant
          • Flows Assistant
          • Studio Assistant
          • FAQ Assistant
          • Audience Assistant
        • AI flow actions
        • AI integrations
        • Detect language: Supported languages
      • How-to
        • Set up and deploy automated FAQs
        • Set up and deploy detect intent models
    • AI Agents
      • Concepts
        • Knowledge bases
        • OpenAI token usage
      • How-to
        • Build a knowledge base
        • Set up an AI Agent
        • Deploy an AI Agent
  • Payments
    • Bird Pay (Beta)
      • Quick Start
        • How to get Bird Pay access?
      • Concepts
        • Onboarding
        • Payment Link
        • Wallet
          • Transfer
          • Recipient
        • Payments
          • Disputes
        • My customers
        • Payouts
        • Payment methods
        • Bird Pay Coverage
        • Strong Customer Authentication (SCA)
      • How-to
        • Create a Payment link
        • Refund a Payment
        • Manage Payout
        • Respond to a Dispute
        • How to set up MFA using the Authenticator app?
      • FAQs
        • Why was my onboarding unsuccessful?
        • How do I update my business address?
        • What are foreign currency fees on my Bird Payments?
        • How to raise an issue with Bird Pay with support?
  • Integrations
    • Integrations
      • Quickstarts
        • Find and install an integration
      • Concepts
        • Integration data sync
      • Supported integrations
        • ActiveCampaign
        • OPERA Cloud
        • Calendly
        • Easyship
        • Google Cloud Translation AI
        • HubSpot
        • Magento 1
        • Magento 2
        • Monday.com
        • Notion
        • OpenAI
        • Rebrandly
        • Salesforce
        • Shopify
        • SugarCRM
        • Zoho CRM
        • TikTok Ads
        • Typeform
        • WooCommerce
        • Zendesk Support
        • Google BigQuery
        • Snowflake
        • Amazon S3
        • Salesforce Marketing Cloud
        • Meta ads
        • Google Ads
  • Account & Billing
    • Account
      • Organization settings
        • General
        • Single-Sign On (SSO)
          • Set up Single-Sign On (SSO)
          • Enforce Single-Sign On (SSO)
          • Entra ID
          • Google Workspaces
          • Okta
        • SCIM
          • Okta setup
          • Entra ID
        • Security Settings
        • Business profile
        • Workspaces
        • Plans & Billing
        • Wallets
        • Users
        • Access policies
        • Access roles
        • Access keys
        • How to find your Organization ID
        • How to find a Workspace ID
        • How to limit a user's access to a single workspace
        • How to download usage report?
        • How to pay (settle) invoices via wallet?
  • Help & Reference
    • Bird support
      • Invite Bird support
    • Deliverability & compliance
      • Email compliance - Bulk sending
      • United States SMS/MMS compliance
        • Key US Regulations
        • General US content restrictions
        • US SMS/MMS compliance
        • US Voice compliance
        • US state-level laws and regulations
        • US compliance & best practices checklist
        • US compliance FAQs
      • Singapore SMS Compliance
    • Data protection
      • Approved subprocessors
    • Release notes
    • Glossary
Powered by GitBook
On this page
  • 1. Explicit Consent to Send SMS
  • 2. Collect SMS consent via text message
  • 3. Collect SMS consent via private forms (App, Paper or Non-public Webpage)
  • 4. Collect SMS consent on Public Webpages
  • 5. Collect SMS consent via Verbal consent
  • 6. Collect SMS consent via Implied consent
  • 7. Collect SMS consent to send OTP or 2FA codes

Was this helpful?

  1. Channels
  2. Channels
  3. Supported channels
  4. SMS
  5. Concepts
  6. SMS Registration

Setting up a SMS consent flow

Last updated 4 days ago

Was this helpful?

Before sending any SMS messages, it is crucial to obtain and track your users’ consent. This section provides a step-by-step guideline on how to properly set up a compliant SMS consent flow and how to describe your SMS consent process when registering for SMS programs. Doing so ensures compliance and reduces the risk of your application being declined by the carriers.

By following these guidelines, you’ll increase the chances that your SMS registration will be accepted, while also meeting legal requirements for user's consent.

If multiple SMS consent methods are used for the same SMS program, you must list them all.

When registering your number as the sender for SMS, carriers and regulatory agencies will carefully review the section describing your SMS consent flow. The name of this section may vary - e.g., Message Flow for 10DLC, Opt-In Flow for TFN - depending on the type of number and relevant regulations. It is essential to provide clear and complete information to reduce the risk of declines.

Tip: Always add links to your Privacy Policy and Terms of Service when describing your consent-gathering process. For examples and best practices on structuring these documents, .

Table of contents:

1. Explicit Consent to Send SMS

It is required and essential that you collect EXPLICIT SMS consent from a user BEFORE sending any SMS messages. Explicit consent means the user has been informed of the option to sign up to receive SMS and has actively agreed to receive such messages on the provided phone number.

In this section, we explain the minimum requirements to set up any Explicit SMS Consent flow. We dive into diverse consent methods in the following sections.

SMS Consent Flow - Call-to-Action (CTA) - minimum requirements:

  • SMS consent is OPTIONAL:

    • Separate SMS consent for Promotional or Transactional messages.

    • SMS consent is not mandatory or linked to any other action, such as a sale or a sign-up to a Newsletter. We suggest the use of un-checked boxes for online call-to-actions.

    • Add disclaimer that "SMS Consent is not a condition of purchase", if applicable.

  • Brand name: identify the company or brand associated with the messaging program.

  • SMS Program use case(s): clear explanation of messaging service nature, e.g.: user authentication, marketing, delivery notifications, appointment reminders, etc.

  • Opt-in instructions: how to sign up. It varies depending on the call-to-action advertising media. For example: text-to-join programs should advertise an opt-in keyword, e.g. START. Online call-to-actions may say "By checking this box, I agree to receive SMS [...]"

  • Message Frequency: CTA shows how many messages users will receive after opt-in. For example: 3 sms/month, one-time message, or “Message frequency varies”.

  • Disclaimer Additional Messaging Costs: CTA should note that “message and data rates may apply”.

  • Customer Support instructions: CTA must explain how to get customer support for service. For example: “Text HELP for support”.

  • Opt-out instructions: CTA must explain how to opt-out of the messaging service. For example: “Text STOP to cancel”.

  • Terms & Conditions: CTA includes a link to Terms and Conditions.

Example of explicit SMS consent flow to send Promotional notifications

  • Clearly indicate you will send marketing via SMS in your consent checkbox or toggle. During registration, provide matching message samples.

  • Never pre-select the toggle or checkbox.

  • Consent to receive SMS is never a condition for purchase.

Example of explicit SMS consent flow to send Transactional notifications

  • Clearly indicate what kind of transactional SMS use case you will send in your consent checkbox or toggle. E.g.: account notifications, customer care, delivery updates, appointment reminders, etc. During registration, provide matching message samples.

  • Never pre-select the toggle or checkbox.

  • Consent to receive SMS is never a condition for purchase.

Example of explicit SMS consent flow to send both Promotional and Transactional notifications

  • Clearly indicate what kind of SMS use case(s) you will send in your consent checkboxes or toggle. During registration, provide samples for all covered use cases.

  • Keep separate consent checkboxes for Promotional and Transactional SMS

  • Never pre-select the toggle or checkbox.

  • Consent to receive SMS is never a condition for purchase.

Non-compliance will result in decline of your registration request and the potential need to pay again for a new submission.

2. Collect SMS consent via text message

Text-to-join method refers to users providing SMS consent by texting a specific opt-in keyword to a specific number. It is commonly used in marketing campaigns or for service updates.

What to include in your SMS consent flow and also in registration description:

  • Description of SMS use cases you intend to send messages (e.g., marketing, service updates, customer care, etc.)

  • Keyword that the end-customer texts to opt-in (e.g., "WELCOME" for transactional, "OFFERS" for marketing). Keep different keywords for each type of message.

  • Disclosure about message frequency (e.g., "Up to 3 sms/month" or "Msg freq varies").

  • Disclosure about potential charges (e.g., "Msg & Data rates may apply")

  • Help instructions (e.g., "Text HELP for support")

  • Opt-out instructions (e.g., "Text STOP to unsubscribe")

  • Location of keyword advertisement: include website URL or Attachment with the mock up of the Keyword advertisement

Example of how to describe consent via text message when registering to send SMS:

For transactional messages only: Users will text-to-join to opt-in to order and shipping updates. The keyword is advertised in our e-commerce website [valid URL] and in flyers offered in our physical stores. It reads: "By texting UPDATES to [number], users agree to receive transactional SMS alerts from [company] including order confirmations and shipping updates. Msg & data rates may apply. Message frequency varies. Reply HELP for support. Reply STOP to unsubscribe. [Privacy Policy] [Terms]." See attachment for flyer example.

For marketing messages only: Users will text-to-join to opt-in to our SMS marketing communications. The keyword is advertised in our e-commerce website [valid URL] and in flyers offered in our physical stores. "By texting OFFERS to [number], users agree to receive promotional SMS messages from [company], including cart reminders. Msg & data rates may apply. 1 msg/order. Reply HELP for support. Reply STOP to unsubscribe. [Privacy Policy] [Terms]." See attachment for flyer example.

For collecting both types of consent: Users will text-to-join to opt-in to our order and shipping updates and our SMS marketing communications. The keyword is advertised in our e-commerce website [valid URL] and in flyers offered in our physical stores. It reads: "Text UPDATES to [number] for transactional messages (order updates, shipping notifications). Text OFFERS to receive promotional messages. Msg & data rates may apply. Message frequency varies. Reply HELP for support. Reply STOP to unsubscribe. [Privacy Policy] [Terms]." See attachment for flyer example.

Important: Ensure that your opt-in message clearly specifies the type of messages the user will receive. Do not combine transactional and promotional consent in a single opt-in flow. Each consent must be collected separately with clear disclosure of message content and purpose. Example of collecting transactional consent via text

Example of collecting promotional consent via text

3. Collect SMS consent via private forms (App, Paper or Non-public Webpage)

For non-public consent forms, such as physical paper forms or those behind login screens or within apps, you need to provide an active opt-in mechanism (e.g., a checkbox). This ensures users are informed and have option to actively agree to receive SMS messages. When the form is not publicly accessible online, you must upload a screenshot or scan of this to form as part of your SMS registrations.

What to include in your SMS consent flow and also in your registration description:

  • Explicit and Optional SMS Opt-In Mechanism: Use a checkbox or another explicit opt-in option to ensure users consent to receiving SMS messages by taking an action - e.g. checking a box, clicking a button, signing a paper form. The checkbox must not be pre-selected. SMS consent is ALWAYS optional.

  • Description of SMS use cases you intend to send messages (e.g., marketing, service updates, customer care, etc.)

  • Disclosure about message frequency (e.g., "Up to 3 sms/month" or "Msg freq varies").

  • Disclosure about potential charges (e.g., "Msg & Data rates may apply")

  • Help instructions (e.g., "Text HELP for support")

  • Opt-out instructions (e.g., "Text STOP to unsubscribe")

  • Links of your Privacy Policy and Terms of Service & other active URLs mentioned in the consent form

  • Screenshot or scanned document of your SMS consent call-to-action (consent form's required verbiage)

Example of verbiage for collecting consent via embedded or off-line forms:

By submitting this form and signing up for texts, you consent to receive marketing text messages (e.g., promos, cart reminders) from [company name] at the number provided, including messages sent by autodialer. Consent is not a condition of purchase. Msg & data rates may apply. Msg frequency varies. Send HELP for support. Unsubscribe anytime by replying STOP or clicking the unsubscribe link (where available). [Privacy Policy] & [Terms].

If the form isn’t available via URL, you must attach a screenshot or scan to ensure it can be reviewed and processed accordingly.

Example of how to describe consent via off-line / private forms when registering to send SMS:

The customer completes a form at the doctor’s office / in our app sign up process that includes opt-in language agreeing to receive text message communications. See attachment. The form includes a reference to our webpage www.ourbrandexample.com, where we provide a link to both our privacy policy (www.ourbrandexample.com/privacy) and term of services (www.ourbrandexample.com/ToS). A scanned copy / a screenshot of our app for SMS consent can be found at www.mydrive/scannedcopy_form.

Example of an in-App Consent Form

Explicit Consent for marketing (or promotional) messages

Example of a paper Consent form

Explicit Marketing Consent

4. Collect SMS consent on Public Webpages

For publicly available consent forms, such as Sign-up, Login, 'Contact Us' or promotional webpages, you need to provide an active opt-in mechanism (e.g., a checkbox). This ensures users are informed and have option to actively agree to receive SMS messages. It is essential to ensure that users actively consent to receiving SMS messages. When registering to send SMS, you must share a link to your public SMS consent form so that it can be reviewed by the relevant authorities.

What to include in your SMS consent flow and also in your registration description:

  • Explicit and Optional SMS Opt-In Mechanism: Use a checkbox or another explicit opt-in option to ensure users consent to receiving SMS messages by taking an action - e.g. checking a box, clicking a button. The checkbox must not be pre-selected. SMS consent is ALWAYS optional.

  • Description of SMS use cases you intend to send messages (e.g., marketing, service updates, customer care, etc.)

  • Disclosure about message frequency (e.g., "Up to 3 sms/month" or "Msg freq varies").

  • Disclosure about potential charges (e.g., "Msg & Data rates may apply")

  • Help instructions (e.g., "Text HELP for support")

  • Opt-out instructions (e.g., "Text STOP to unsubscribe")

  • Links of your Privacy Policy and Terms of Service & other active URLs mentioned in the consent form

  • Location of the SMS consent form: live URL of your call-to-action (showing consent form's required verbiage)

Example of how to present an opt-in message on a public web page:

“By checking this box, I agree to receive customer care, account notifications, promotions, and offers from [company] via SMS at the phone number provided. Consent is not a condition of purchase. Msg & data rates may apply. Msg frequency varies. Reply HELP for support. Reply STOP to unsubscribe. [Privacy Policy] & [Terms].”

Best practices when registering:

  • If the opt-in form is not on your homepage, specify the URL where it occurs and describe the exact location.

  • For pop-up forms, ensure the process is clearly explained, stating how customers are prompted to the pop-form for SMS consent, include URLs to the page where pop-up is located, and attach a screenshot as proof of SMS Consent Flow.

Example of how to describe consent via public webpage forms when registering to send SMS:

Users provide consent to receive SMS when they sign up to receive additional 10% in their 1st purchase. To receive additional discount, users access our company's homepage at www.ourbrandexample.com/smspopup and a pop-up form is presented, as seen on the attached screenshot. The user has the option to sign up to promotional marketing and order updates. We provide link to both our Privacy Policy [link] & our Terms of Service [link].”

Example of a web consent form

Explicit Marketing Consent

5. Collect SMS consent via Verbal consent

Verbal consent is typically gathered during in-person interactions or over the phone. This method is common for customer service interactions or in-store communications, where the customer verbally agrees to receive SMS communications and provide the contact phone number.

What to include in your SMS consent flow and also in your registration description:

  • Clear Verbal Statement (with script) including the required SMS Consent Language: The customer must be explicitly informed that they are opting into SMS communications and provided with key disclaimers required by the authorities. These are:

    • Brand name and message use case

    • Message frequency

    • "Message and data rates may apply"

    • Reply STOP to opt-out

    • Reply HELP to get support

    • Location (e.g. URL links) of Privacy Policy and Terms of Service

  • Consent Confirmation: Ensure the customer gives explicit verbal consent to receive SMS messages. This can be done by asking them to confirm their consent during the interaction.

Example of how to describe a verbal consent flow when registering for SMS:

The customer verbally opts in during a phone conversation with a customer service representative, who asks if they would like to receive text messages from our company. Our agents are instructed to follow this script: "Thank you for providing your phone number. Would you like to receive SMS notifications from [company name] about your recent order and related shipping updates? Note that message frequency varies and message and data rates may apply. You can reply with HELP for support or with STOP to opt-out at anytime. Review our privacy policy (www.ourbrandexample.com/privacy) and terms of services (www.ourbrandexample.com/ToS) for additional details".

Additional Information:

Creating a standard verbal script for your team that clearly states the key disclaimers will ensure consistency and compliance across all verbal opt-ins. If the script is included in your registration request, this will greatly increase your chances of approval!

Example of script you can use when collecting verbal consent:

“Thank you for providing your phone number. Would you like to receive SMS notifications from [company name] about your recent order and related shipping updates? Note that message frequency varies and message and data rates may apply. You can reply with HELP for support or with STOP to opt-out at anytime. Review our Privacy Policy (www.ourbrandexample.com/privacy) and Terms of Services (www.ourbrandexample.com/ToS) for additional details".

6. Collect SMS consent via Implied consent

Implied consent occurs when the user initiates the text message communication with the business, and the business responds with relevant information. No additional verbal or written permission is required since the user has actively started the exchange. This is a common opt-in method for customer care interactions via SMS. The business only responds to the customer’s inquiries or requests, ensuring no unsolicited messages are sent.

What to include the SMS consent description of your registration:

  • The workflow must clearly show that the customer is initiating the contact by sending the first message.

  • Location of the business' phone number for contact: where is the phone number advertised? So that customers know what number to send SMS? Provide a live URL or a screenshot of this advertisement, when applicable.

  • Links of your Privacy Policy and Terms of Service

Example of how to describe an implicit consent flow when registering for SMS:

The customer sees the business' phone number in our 'Contact Us' webpage at www.ourbrandexample.com/contactus and sends a text message to initiate communication with the business for customer care purposes. Business' agents will only respond to the customer’s inquiries or requests, no unsolicited messages are sent. See our Privacy Policy www.ourbrandexample.com/privacy and Terms of Services www.ourbrandexample.com/ToS.

7. Collect SMS consent to send OTP or 2FA codes

Consent to send a One-Time Password (OTP) aka Two-Factor Authentication (2FA) is often collected by the act of sharing the number itself. To avoid registration declines, it is extremely important that all required disclaimers are provided in your call-to-action and that OTP or 2FA code via SMS is optional.

What to include the SMS consent description and in your registration:

  • Explicit and Optional SMS Opt-In Mechanism: Use a checkbox or another explicit opt-in option to ensure users consent to receiving SMS messages by taking an action - e.g. checking a box, clicking a button. Any checkbox must not be pre-selected. SMS consent is ALWAYS optional.

  • Description of SMS use case (e.g. 2-factor authentication code)

  • Disclosure about message frequency (e.g., "1 SMS/request").

  • Disclosure about potential charges (e.g., "Msg & Data rates may apply")

  • Help instructions (e.g., "Text HELP for support")

  • Opt-out instructions (e.g., "Text STOP to unsubscribe")

  • Links of your Privacy Policy and Terms of Service & other active URLs mentioned in the consent form

  • Location of the SMS consent form: live URL of your call-to-action or screenshot attachment (showing consent form's required verbiage)

Example of a SMS consent form for OTP or 2FA codes:

Example of how to describe a consent flow for OTP or 2FA codes when registering for SMS:

The customer consents to receive 2FA SMS by sharing their number in our App during the sign up process. Users are informed that SMS consent is optional and limited to 2FA and not transferred to other kinds of SMS. All SMS disclaimers are presented. As this occurs in our app, we have attached a screenshot for your review. Review our Privacy Policy (www.ourbrandexample.com/privacy) and Terms of Services (www.ourbrandexample.com/ToS) for additional details.

Privacy Policy: CTA includes a link to Privacy Policy.

Marketing SMS (which includes abandoned carts) can only be sent to users who ACTIVELY agreed to receive this type of message. Review marketing-related regulations

Consent to send Marketing SMS (which includes abandoned carts) can only be sent to users who explicitly agreed to receive marketing SMS. Review marketing-related regulations

Consent to send Marketing SMS (which includes abandoned carts) can only be sent to users who explicitly agreed to receive marketing SMS. Review marketing-related regulations

How to set up a SMS compliant Privacy Policy.
check this article
Explicit consent to send SMS
Collect SMS consent via text message
Collect SMS consent via private forms (App, Paper or Non-public Webpage)
Collect SMS consent via Public Webpages
Collect SMS consent via Verbal consent
Collect SMS consent via Implied consent
Collect SMS consent to send OTP or 2FA codes
here
here
here