Open Settings → Business Info → Compliance. Complete all five sections so Avoca can use the information when registering your business for supported messaging and voice traffic.
Use exact legal information. Carrier verification can be delayed or rejected when names, addresses, registration numbers, policies, or opt-in evidence do not match.
Enter the legal business details shown in the form, including:
- legal business name and an optional public DBA
- an HTTPS business website
- legal structure and A2P company type
- industry
- business registration number, such as an EIN
- stock exchange and ticker when the selected company type requires them
Use the legal name and registration number exactly as they appear on government records.
2. Business Address
Enter the primary physical business address. The form supports US and Canadian addresses and requires the appropriate state or province and postal code.
Do not enter a temporary address solely to complete the form. The address should correspond to the registered business.
3. Authorized Representative
Enter the first and last name, business email, direct phone number with country code, job position, and business title of the person authorized to represent the company.
That person may need to respond if Twilio or a carrier sends a verification email or text. Use an actively monitored business email and phone number.
4. Policy URLs
Add public HTTPS links to your Terms & Conditions and Privacy Policy.
- Confirm both pages are published and accessible without signing in.
- Confirm the terms include the applicable SMS and calling consent language.
- Confirm the privacy policy explains how phone numbers and messaging data are used.
- Choose Verify & Save to run the displayed checks.
Save Only stores the URLs without completing verification. The section is counted as complete only after its status is Verified. A status of Pending, Needs review, or Failed requires follow-up.
5. Opt-in Screenshots
Upload up to five screenshots that show how a customer consents to receive SMS messages. Include the consent language and enough surrounding context to make the opt-in flow understandable.
Choose Analyze & Save to run the displayed compliance checks. Save Only stores the screenshots without making the section verified.
Do not upload passwords, API keys, identity documents, or unrelated customer data. Capture only the opt-in experience needed for review and redact unrelated personal information.
Use the templates carefully
The page includes copyable examples for a privacy policy, terms and conditions, opt-in language, and an A2P message flow. Replace every placeholder and have your legal or compliance owner review the final text before publishing it. The templates are general examples, not legal advice.
Read progress and verification states
The progress bar counts a section only when its required data is complete. Policy and opt-in sections also need successful verification. Open any incomplete or failed pill to review its details, make the smallest correction, and verify again.
If verification continues to fail, confirm that the pages are public, use HTTPS, contain the required disclosures, and match the uploaded evidence. Then contact Avoca Support with the verification summary; do not send representative details or registration documents through an unapproved channel.