Web chat consent that's A2P compliant, and yours to customize

Customize how the web chat widget collects consent, and clear a common blocker in SMS (A2P) registration with a new capability for AI Chat Receptionists that collects separate consent for transactional and marketing messages. 
A consent flow built for A2P approval
If you've ever had an A2P registration rejected because of your web chat widget, this is an important update for you! A new capability for AI employees collects separate consent for transactional and marketing messages, and
 you can customize or remove it to match how your business operates. It's added automatically to your AI Chat Receptionist when you submit A2P registration, and it's available to add for all existing accounts.
Why it matters
For US businesses wanting to empower their AI employees to send SMS messages, obtaining A2P approval for can be challenging. A fixed, uneditable consent widget made that harder; you could see it was holding up approval, but had no way to change it yourself. Now, a compliant consent flow is available, and you're in control: adjust the language, or remove it, to fit your business.
Who it's for
Partners and SMB clients submitting or resubmitting US A2P (SMS) registration
Partners and SMB clients with an AI Chat Receptionist - or other AI employee - connected to a web chat widget
Partners and SMB clients who want to adjust web chat consent language or behavior
How to get started
This update applies automatically. No action is required for existing accounts.
Any account that submits A2P registration automatically gets the new consent capability added to its chat receptionist.
To review or customize the consent language, go to your AI Chat Receptionist's configuration and locate the "Obtain SMS consent" capability.
Adjust or remove the capability as needed for your business. It's fully editable, unlike the previous version.
FAQs
Q: Do I need to do anything to get the new consent flow?
A: No. Existing accounts on the old widget have already been switched over automatically.
Q: Can I remove the consent capability entirely?
A: Yes, it's removable by the partner or the SMB, unlike the previous fixed widget.
Q: Does this guarantee A2P approval?
A: No single change guarantees approval, but this removes a specific, known rejection reason tied to the old widget's lack of proper consent collection.
Q: Does this affect channels other than web chat?
A: No, this update is specific to the web chat consent experience.