How to set up your SMS disclosure language

read
Last updated at:

You will learn

Learn how to create SMS disclosure language on the account-level, making it easy to add to your signup forms. 

Note that this article is only for people who have not already set up their disclosure language; it is only for those who didn’t complete that step in the SMS setup wizard. 

This information is not legal advice. Klaviyo recommends that you consult with your legal counsel to make sure that you comply with applicable laws in connection with your marketing activities.

Why do I need disclosure language?

Disclosure language is critical to SMS compliance. By law, you need to include it anywhere you’re collecting SMS consent. 

Where should disclosure language go in a form? 

As a best practice, disclosure language should be placed above the SMS opt-in button in a form, so your customers read it before subscribing. 

Before you begin

Before creating your disclosure language, you must:

Create your SMS disclosure language

  1. Click your organization name in the bottom left corner.
  2. Navigate to Settings > SMS.
  3. Scroll down to SMS opt-in disclosure
  4. Click Configure opt-in disclosure
  5. Include your full company name.
    The SMS Opt-in disclosure menu page where you can fill in your company name, privacy policy URL and terms of service URL.
  6. Add a link to your privacy policy. 
  7. Add a link to your mobile terms of service. 
  8. Check the box labeled I have updated my privacy policy to include SMS sending information.
  9. Click Submit

Sample disclosure language

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. Unsubscribe at any time by replying STOP or clicking the unsubscribe link (where available). Privacy Policy [link] & Terms [link]

Additional resources

x
Was this article helpful?
0 out of 1 found this helpful