Overview
The Compliance Embeddable is a white-label offering designed to help Internet Software Vendors (ISVs) seamlessly integrate compliance onboarding into their web application. This product enables ISVs to securely collect and process compliance information from their customers, streamlining compliance onboarding and your customer’s time-to-market. The solution enables ISV developers to easily implement intuitive onboarding flows across hundreds of programs, enabling ISVs to enter new markets swiftly and adapt to regulatory changes with ease.
Environment
legacy Twilio Console
What You Need To Know
Frequently Asked Questions
Which onboarding programs does the Compliance Embeddable support?
The Compliance Embeddable currently supports the following compliance programs:
- Regulatory Compliance Bundles for Long Codes
- US Toll-Free Verification for Programmable Messaging
- US A2P 10DLC for Programmable Messaging
- Secondary Customer Profiles for Voice Trust
- US Voice Basic Branded Calling
If you are interested in using the Compliance Embeddable for any of these programs, please submit the Compliance Embeddable registration form.
What’s the pricing of the Compliance Embeddable product?
The Compliance Embeddable product is offered for free to help customers streamline their onboarding experience.
Will I be notified of the outcome when a customer submits the required information through the Compliance Embeddable?
Yes. All submitted inquiries using the Compliance Embeddable use the same compliance registration objects used in the Twilio Console and API. This means you can set up the same webhooks or event streams that come standard with each compliance program. Additionally, you can listen to client side events to monitor progress of end users as they fill out the form.
I already have some information about my customers. Does the Compliance Embeddable support prefilling information?
Yes. You may prefill information by sending it during the initialize API call.
What happens after submission and on the final screen?
All Compliance Embeddable inquiry flows will complete on a finish screen with a Done button. The submission of the inquiry occurs on the second-to-last screen on a Done button, and the final finish screen is there for confirmation. When a user lands on the last screen, an event handler onInquirySubmitted will be fired. You can use this client side event to navigate your user away from this screen. Similarly, when a user clicks the Done button on the finish screen an event handler onComplete will be fired that you can use for navigational purposes.
Will the Compliance Embeddable allow end users to fix rejected registrations?
Yes. An end user can resume and resubmit a rejected inquiry. This process varies by program. In all programs, the error codes rendered are meant to be user friendly and whitelabel so end users can self-serve the resubmission.
What if the end user cannot finish submitting the form in a single session? Can they resume their submission later?
Yes. An end user can resume an inquiry by using the same ID on the initialize API call, and the end user will land on the page where they last left the inquiry.
How can I know if my end user starts a form but doesn’t finish it? I want to be able to send notifications to these users and remind them to complete the form.
When the user submits the form and lands on the last screen, an event handler onInquirySubmitted will be fired. Additionally, you will receive server side webhooks or event streams that you have subscribed to for the program. You can monitor a users progression through the Compliance Embeddable with client side events.
Will I be able to access the data that my end user submits?
Yes. If you’d like to get detailed information of the submitted data in the compliance registration (e.g., what legal business name did this customer use), you can retrieve that information using the Twilio Console or the program specific APIs.
Are there any steps not included in the Compliance Embeddable but are needed to complete onboarding?
Yes. The Compliance Embeddable solves the customer journey step for registration by collecting KYC information and registering the end user with the appropriate third parties as applicable. You may have additional steps to fully provision the end user (e.g., API calls to purchase a phone number using the Regulatory Compliance Bundle SID). Additionally, you may still need to make additional calls to support the end-to-end process to onboard new end customers, such as creating Twilio subaccounts.
Does the Compliance Embeddable support language translation?
No. The Compliance Embeddable will render on the page in English.
Will the Compliance Embeddable allow me to customize how the form UI looks?
Yes. We support customizing UI styles - specifically, theme color and font. Our team can work with you to do the customization, but there’s no self-service capability for you to manage this. Once we have a UI style set, you can pass a parameter called ThemeSetId in the server-side call to enable the customization. If you don’t have an account team, please submit a Support Ticket with “Compliance Embeddable UI Customization Request” as the subject line.
Will the Compliance Embeddable allow me to customize the content in the form?
No. The Compliance Embeddable does not support customizing the content of the form, such as changing copy language or re-arranging questions.
What happens when Twilio services are down? Will the UI render? Will the onboarding process pause or status communication get affected in any way?
If the Compliance Embeddable service is down, it means the end customer will not be able to create new compliance registrations or edit existing submissions via the Compliance Embeddable UI. The data in the Twilio backend will not be impacted. If part of the flow is down, the UI would render an unavailable screen.
Where is this data stored? Can you share more details on the privacy aspect?
All data is stored in the US. All data and workflows covered in this document would fall under the scope of Twilio compliance practices. Please review the privacy policies which covers various topics ranging from how we handle PII to working with 3rd parties.
What domains do I need to add to the allow list for my firewall rules?
Please add http://www.withpersona.com/ to the allow list.