Skip to the guide
Educational guide only. This is not legal advice and does not guarantee Twilio, carrier, or campaign approval. Requirements can change. Have qualified counsel review your final implementation.

A2P 10DLC client blueprint

Build the pages reviewers need to see.

Align the lead form, consent language, SMS Terms, Privacy Policy, GHL records, and campaign submission before sending anything for review.

1. Compliance hubPrepare and verify the complete package.2. Landing pageSee two separate unchecked consent boxes.3. SMS TermsCopy the messaging-program terms.4. Privacy PolicyAdd the mobile-data non-sharing clause.5. MessagesPrepare matching registration text and samples.6. Batch generatorImport clients and export five copy-ready fields.7. Funnel generatorBuild all six client pages as paste-ready HTML.

Skip the copy-paste

Have the generator write all six pages for you.

This hub explains what reviewers require. The funnel generator produces it — enter the client's details once and get the home, about, contact, booking, privacy, and SMS terms pages as paste-ready HTML, plus the consent wording for the GHL form and calendar.

Open the funnel generator

Step 1: make it yours

Replace every red placeholder.

Enter the client's exact registered and public-facing details once. This browser will reuse them throughout the example pages.

Step 2: verify the package

Check only what is live and testable.

Progress stays in this browser. The policy and opt-in URLs still need to be accessible to reviewers even though this guide itself is unlisted.

Completion score

0 of 17

Website and identity

GHL records and workflows

Policies and submission

Step 3: choose the matching consent

If the campaign sends both marketing and informational messages, show both disclosures as separate optional controls and store each selection separately.

Marketing

Offers and promotions

Informational

Service and appointment updates

Step 4: assemble the reviewer file

Send Twilio one consistent package.

Provide exact, live URLs and plain-language opt-in steps. Screenshots help explain the flow but do not replace live pages. The campaign description, samples, and declaration answers must describe the exact traffic the location will send.

Campaign description template

[A2P-REGISTERED BUSINESS NAME / APPROVED DBA], operated by [YOUR LEGAL BUSINESS NAME], sends [MARKETING AND/OR INFORMATIONAL] messages to people who directly opt in on [WEBSITE URL]. Users enter their contact information and may select separate, optional, unchecked consent boxes for the applicable message categories. Messages include [LIST REAL MESSAGE TYPES]. Message frequency varies. Message and data rates may apply. Users can reply STOP to opt out or HELP for assistance. The message flow links directly to the Terms and Privacy Policy.

Attach these reviewer links

  1. 1. Opt-in page URL: the exact published form with unchecked controls.
  2. 2. PrivacyPolicyUrl: a direct URL to the complete policy.
  3. 3. TermsAndConditionsUrl: a direct URL to the SMS program terms.
  4. 4. Message flow: the page, fields, consent action, stored evidence, and links.
  5. 5. Screenshots: full-page proof plus close-ups of each unchecked checkbox.

Rejection map

Use the exact code to target the fix.

Do not assume a policy rewrite cures an incompatible business model or opt-in flow. Fix the underlying requirement named by the code.

On a small screen, scroll the table sideways. Keyboard users can focus the table region and use arrow keys.

Twilio A2P rejection codes, what they mean, and what to verify before resubmitting
Twilio codeWhat it meansWhat to verify
30908The privacy policy or privacy-policy evidence does not meet campaign requirements.Provide a dedicated PrivacyPolicyUrl, reference the policy and opt-in path in message_flow, and ensure the policy explains collection/use, frequency and rates, STOP/HELP, and mobile-data/consent non-sharing.
30882The Terms URL is missing/inaccessible or the business model conflicts with direct-consent rules.Provide a direct TermsAndConditionsUrl. Prohibited affiliate marketing or third-party lead-generation practices cannot be cured by policy wording; the actual campaign and flow must comply.
30924The opt-in disclosure is incomplete or not presented with the consent action.At the point of consent, state the type of messages, message frequency, message/data rates, and STOP instructions.
30925Consent is bundled, preselected, or not captured through a distinct affirmative control.Use a separate SMS consent control that is unchecked by default and optional.
30913Marketing and informational consent are combined when separate consent is required.Use separate optional controls and records for marketing versus informational/service messages.

Primary guidance

Verify against the latest rules.

Carrier and platform requirements change. Check the official sources again immediately before submission.