Skip to main content

Setting Up RCS Consent Collection with Klaviyo

Learn how to configure your Klaviyo RCS setup to work with Alia popups.

Written by Cory Gill

What is RCS?

RCS (Rich Communication Services) is the next generation of SMS messaging, allowing brands to send more interactive mobile experiences with features like:

  • Verified sender profiles

  • Rich media

  • Buttons and branded messaging

  • Improved engagement experiences

You can learn more about Klaviyo RCS here:


Why This Matters for Alia Popups

Some merchants using Klaviyo RCS may run into approval issues when submitting Alia popup screenshots during the RCS onboarding process.

This happens because certain Klaviyo RCS agent configurations require disclosure language that includes both:

  • Promotional consent

  • Transactional consent

By default, many Alia popup disclosures only include promotional consent language.


Your Two Options

To use RCS with Alia signups, merchants currently have two options.

Option 1: Temporarily Update Your Disclosure Language (Recommended)

This is the easiest self-serve option and does not require contacting Klaviyo support.

During your RCS submission process, temporarily update your popup disclosure language to include both promotional and transactional consent.

Once your RCS agent is approved, you can remove the additional transactional language afterward if you do not plan to send transactional messages through that popup.

Temporary Disclosure Language

Use the following disclosure language in your popup screenshot submission:

By entering your phone number and submitting this form you consent to receive general marketing (incl. cart reminders) related messages and transactional messages (incl. order alerts) from COMPANY NAME at the number provided, including messages sent by autodialer. Consent is not a condition of any purchase. Message and data rates may apply. Message frequency varies. You can unsubscribe at any time by replying STOP or clicking the unsubscribe link (where available) in one of our messages. Text HELP for help. View our Privacy Policy and Terms of Service.

Make sure to:

  • Replace COMPANY NAME with your brand name

  • Keep your Privacy Policy and Terms of Service underlined to indicate hyperlinks

  • Include the updated disclosure in the screenshot submitted to Klaviyo

These screenshots do not need to come from a live popup. Mockups are acceptable for submission purposes.


Option 2: Update Your Klaviyo Agent Use Case

Merchants can also ask Klaviyo Support to update their RCS agent configuration from:

  • Promotional + Transactional
    to:

  • Promotional Only

This allows brands to continue using Alia’s default disclosure language without modification.

However, this option currently requires contacting Klaviyo Support directly.


Frequently Asked Questions

Does changing my agent use case impact my ability to send RCS?

At this time, Klaviyo has confirmed that updating your agent configuration to promotional-only does not functionally impact or block your ability to send RCS messages.

However, because RCS is a rapidly evolving channel with changing carrier requirements, Klaviyo cannot guarantee future requirements will remain the same.


Can merchants self-serve this without contacting Klaviyo Support?

Yes — but only through Option 1.

Merchants can fully self-serve RCS approval by temporarily updating their disclosure language during submission.

Changing the actual agent use case configuration still requires contacting Klaviyo Support.


Will updating my disclosure language affect future consent collection?

Temporarily updating your disclosure language for approval purposes should not create downstream issues for most merchants.

Once approved, many brands choose to revert back to their standard disclosure language if they are not collecting transactional consent through that popup.

If you have specific compliance concerns, we recommend reviewing your setup with your legal team.


Is this a permanent requirement?

Not necessarily.

Klaviyo has shared that they are actively working with their RCS vendor to reduce or eliminate this approval friction in the future. However, there is currently no guaranteed timeline for changes.

As RCS continues to evolve, carrier requirements and onboarding processes may continue to shift over time.

Did this answer your question?