Skip to main content
Outbound calls and messages must use approved business identity, phone numbers, consent sources, schedules, and opt-out behavior. Complete the dashboard’s compliance process before activating a campaign.
This guide explains Avoca configuration, not legal advice. Your business is responsible for its consent, outreach, retention, and calling practices. Involve your legal or compliance owner when requirements are unclear.

​
Complete Business Info → Compliance

The compliance workflow collects the business information used during brand and messaging registration:
  1. Enter the legal business identity and tax information exactly as registered.
  2. Add the business address and authorized representative.
  3. Add the public Privacy Policy and Terms & Conditions URLs, then choose Verify & Save and review the results.
  4. Document how customers opt in and upload representative opt-in screenshots.
  5. Choose Analyze & Save and review the screenshot findings.
  6. Correct incomplete or failed checks, then run the corresponding verification action again.
The policy pages and opt-in experience must be publicly reachable and consistent with the outreach the business intends to send.
Save Only preserves a draft but does not verify policy URLs or analyze opt-in screenshots. A section is not ready for registration until its required verification or analysis succeeds.

​
Review Brand Onboarding

Business Info → Brand Onboarding shows the registration work associated with phone numbers and messaging. Depending on the channels enabled, it can include:
  • Business identity and profile
  • Authorized representative
  • A2P messaging profile and trust product
  • Brand registration
  • Messaging services and campaign registration
  • Voice identity or branded calling products
Some steps are completed with Avoca. Do not create duplicate registrations or replace a production messaging service to resolve a warning without coordinating with Support. Before creating the campaign, answer:
  • Where did each contact provide their phone number?
  • What type of communication did they agree to receive?
  • Is the planned call or message consistent with that agreement?
  • When and how is the consent recorded?
  • Which contacts have opted out or requested no further contact?
  • Is the audience subject to an internal suppression or exclusion list?
An audience filter describes who matches business criteria. It does not create consent and does not override an opt-out.

​
Configure operational safeguards

Review the campaign and workflow for:
  • Approved execution hours and timezone
  • The sending or calling phone number
  • Clear business identity in opening messages
  • Expected message frequency and nudge count
  • STOP and other supported opt-out handling
  • Recently contacted exclusions
  • Campaign-specific exclusions
  • Recurrence behavior
  • Human escalation or follow-up ownership
Use Preferences and exclusions to maintain team-level contact controls and review workflow execution hours before launch.

​
Pre-launch review

  1. Preview the final audience and sample representative records.
  2. Confirm the audience count with the business owner.
  3. Open every workflow branch and verify that it ends intentionally.
  4. Test with approved internal recipients.
  5. Confirm caller ID, message identity, links, opt-out behavior, and notifications.
  6. Verify the resulting call, conversation, campaign event, and CRM note when applicable.
  7. Record the launch owner and monitoring window.
  8. Activate the campaign only after the compliance and business owners approve it.

​
Ongoing monitoring

Pause and investigate when you see:
  • An unexpected increase in opt-outs or complaints
  • Contacts outside the intended service area or audience
  • Messages sent outside approved hours
  • A phone number or messaging service losing its approved status
  • A workflow sending more attempts than intended
  • A campaign continuing after its business purpose ended
Stopping a campaign prevents new campaign execution but does not erase calls or messages already sent. Preserve the campaign and interaction IDs when contacting Support. See 10DLC compliance for common messaging questions.