Pre-Built A2P Campaign (Widget-First) Registration Flow

Modified on: Mon, 9 Mar, 2026 at 12:28 PM

Overview


The Pre-Built A2P Campaign (Widget-First) registration flow is a structured campaign submission experience designed to:

  • Improve compliance accuracy

  • Reduce carrier rejections

  • Eliminate manual compliance writing

  • Prevent classification errors

  • Streamline the A2P registration process

This flow enforces a Chat Widget–based opt-in method and automatically applies carrier-aligned compliance standards.

By locking required compliance elements and auto-generating mandatory disclosures, the system significantly reduces submission errors and approval delays.


Note: This campaign registration flow is not available for:

  • Mixed use-case campaigns

  • Sole Proprietor (Sole-prop) campaigns


Accessing the Pre-Built Campaign Flow


Users can now select “Pre-Built Campaign (Chat Widget)” when starting Campaign Registration in the Standard A2P flow.


This guided experience:

  • Enforces Chat Widget as the only opt-in method

  • Automatically generates compliant consent language

  • Locks required compliance elements

  • Prevents financial and marketing misclassification

  • Reduces rejection risk

  • Automatically attaches the compliant widget to the campaign


Messaging Use Case Selection

Messaging Use Case Selection defines the type of messages your campaign will send and determines how the campaign is categorized during registration.

The flow includes a structured two-step selection process.

Step 1: Message Type


OptionDescription
Marketing / PromotionalAdvertising, offers, sales, promotions
Transactional / Non-MarketingInformational or service-related messages



Step 2: Use Case Selection

The available use cases depend on the selected message type.

If Marketing / Promotional is selected:

  • Only Marketing will be available.

If Transactional/Non Marketing is selected:

Choose from:

  • 2FA

  • Account Notification

  • Customer Care

  • Delivery Notification

  • Fraud Alert

  • Higher Education

  • Polling and Voting

  • Public Service Announcement

  • Security Alert


Why This Structure Matters

This controlled selection process:

  • Prevents incompatible combinations

  • Reduces classification errors

  • Aligns campaigns with carrier requirements

  • Decreases rejection rates


Automatic Age Gating (Carrier-Compliant)

Age gating is automatically enforced when:

  • Age-gated content is selected

When Triggered:

ActionSystem Behavior
Age-gated checkbox selectedDate of Birth (DOB) field appears
DOB fieldMandatory and non-removable
SubmissionBlocked until DOB is completed

 


 Note- 1. If age-gated content is not selected, the DOB field does not appear.

            2. This ensures automatic compliance for regulated industries.


Auto-Generated Compliance Widget

The system automatically generates a compliant Chat Widget that includes:

  • Business name injected into disclosure language

  • Required disclosure text

  • STOP/HELP instructions

  • Data rate disclosure

  • Message frequency disclosure

  • Campaign attachment

  • Embed code generation


Locked Compliance Controls

Users cannot:

  • Edit disclosure text

  • Remove required fields

  • Add custom compliance fields

  • Modify compliance language

  • Select alternative opt-in methods

This ensures consistent compliance and reduces manual errors.


Widget Structure

Required (Locked Fields)

FieldStatus
Phone NumberMandatory
Disclosure BlockLocked
STOP/HELP LanguageLocked
Data Rate DisclosureLocked
Message Frequency DisclosureLocked


Conditional

FieldCondition
Date of BirthMandatory if age-gating is triggered


Optional

FieldEditable?
NameYes
Message FieldYes
UI Styling (colors/header only)Yes


Removed

Removed ItemReason
Email FieldNot required for SMS compliance
Custom Compliance FieldsPrevents deviation from carrier-approved language
Editable Disclosure TextPrevents compliance violations
Opt-in Method SelectorWidget-only enforcement

Marketing Consent Checkbox

For Marketing / Promotional campaigns:

  • A dedicated Marketing Consent checkbox is now included.

  • The checkbox is mandatory before submission.

  • Users cannot proceed without explicitly confirming marketing consent.

This adds an additional compliance safeguard for promotional messaging.


Read-Only Widget Preview

Users can preview:

  • The full widget

  • Disclosure placement

  • DOB field (if triggered)

The preview is non-editable to maintain compliance integrity.


Final Consent Review

Prior to submission:

  • Required fields are auto-filled

  • Compliance sections are locked

  • Sample messages are generated

  • Opt-in method is defined

  • Website compliance checklist confirmation is required

This final review ensures that all compliance elements are correctly configured before submission.


At this stage, users cannot:

  • Edit disclosure text

  • Remove required fields

  • Add consent checkboxes

  • Edit any compliance fields

  • Select alternative opt-in methods

All compliance elements remain non-editable to ensure consistency and prevent submission errors.


Who Can Use This Flow

The Pre-Built A2P Campaign (Widget-First) registration flow is available to:

  • Agencies submitting new A2P campaigns

  • Sub-accounts registering new campaigns

  • Marketing-only campaigns

  • Transactional-only campaigns

  • Campaigns that include age-gated content

Not available for:

  • Mixed use-case campaigns

  • Sole Proprietor (Sole-prop) campaigns


Key Benefits

  • Reduced rejection rates

  • Automatic age-gating compliance

  • Prevention of financial and marketing misclassification

  • Faster submission process

  • Elimination of manual compliance writing

The Pre-Built A2P Campaign (Widget-First) flow provides a structured, compliance-focused registration experience designed to improve approval outcomes and simplify campaign setup.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article