Twilio A2P 10DLC Registration (US)

If your boutique is based in the United States and you're setting up the Twilio Integration, US mobile carriers require you to register your business and messaging use case through Twilio's A2P 10DLC (Application-to-Person, 10-Digit Long Code) program before you can send SMS messages reliably. This guide walks you through the process with bridal-specific guidance and the most common pitfalls that cause Twilio to reject registrations.

What A2P 10DLC Is (In Plain English)

US carriers require any business sending SMS from a 10-digit number to identify itself and describe how it will use messaging. Unregistered numbers get heavily rate-limited or blocked as spam. A2P 10DLC is the registration program, and it has two pieces:

• Brand — who your business is (legal name, tax ID, address, website).
• Campaign — what you'll send (use case, sample messages, opt-in flow).

You complete both inside Twilio. Once approved, your Twilio phone number is attached to the approved Campaign and you're cleared to send.

Before You Start: What to Gather

The single biggest cause of rejection is mismatched business information. Twilio cross-checks what you enter against IRS and public business records, so have these ready and enter them exactly as they appear on your tax documents:

• Legal business name — exactly as registered with the IRS, not your storefront / "doing business as" name (unless they match).
• EIN — required for Standard tiers. If your business has an EIN at all, you must use a Standard tier — Sole Proprietor is only for businesses without one (see the next section).
• A personal mobile phone number — Sole Proprietor only. Twilio texts a one-time verification code to it, so it must be a real US or Canadian mobile number you can receive texts on — not a Twilio number, landline, or VoIP number.
• Business physical address — matching the address on your IRS records.
• Business website URL — must link to a privacy policy that covers SMS (see next section).
• Business type — LLC, Corporation, Sole Proprietorship, etc.
• Authorized representative — a real person's name, business email, and phone. Use a named email, not a generic info@ inbox.
• Industry / vertical — Retail is the standard choice for bridal boutiques.

Choose Your Registration Tier

Twilio offers three Brand tiers with different fees and daily caps. Which one you use is decided almost entirely by one question: does your business have an EIN?

• Sole Proprietor — only for businesses without a tax ID. You register as an individual (no EIN needed) and verify a personal mobile number via a texted code. Limits: 1 phone number, and a daily cap of roughly 1,000 message segments to T-Mobile customers (other carriers allow more) — plenty for a boutique. Cheapest tier.
• Low Volume Standard — requires an EIN. This is the right tier for boutiques organized as an LLC or corporation, which covers most established shops: every US LLC has an EIN, and having an EIN makes you ineligible for Sole Proprietor — even a single-member LLC taxed as a sole proprietorship. Registering as Sole Proprietor anyway is a guaranteed rejection.
• Standard — highest caps, highest fees. Rarely needed for a single-location boutique.

Most bridal boutiques send 50–500 segments per day (estimate by multiplying your busy-day message count by about 1.5), so volume is rarely the deciding factor. In short: no EIN → Sole Proprietor; EIN (LLC, corporation, or a sole proprietorship that registered for one) → Low Volume Standard.

Set Up Your Privacy Policy and Opt-In Disclosure

This is the step that most boutiques get stuck on. Twilio will reject your Brand and/or Campaign if your website doesn't clearly tell customers that you'll text them and link to a privacy policy covering SMS. Handle this before you submit anything to Twilio.

1. Add an SMS section to your privacy policy

If you don't already have a privacy policy published on your website, you'll need to create one before registering. A few common options:

• Your website platform's built-in tools. Shopify, Squarespace, Wix, and WordPress all offer free privacy policy generators or templates — check your platform's help docs. Usually the fastest route since it drops directly into your existing site.
• A dedicated privacy policy generator. Tools like Termly, TermsFeed, and PrivacyPolicies.com build a policy from a short questionnaire, and most have a free tier that's sufficient for a small business.
• AI tools. Ask ChatGPT or Claude to draft a privacy policy for a small bridal boutique that collects names, phone numbers, and email addresses for appointment booking and SMS communication. Treat the output as a starting point — read it over and adjust anything that doesn't match how your business actually operates before publishing.
• A lawyer. For peace of mind — especially if you also collect payment data or operate across multiple states — a short consultation with a small-business attorney is worthwhile.

Once you have a policy in place (or if you already do), add an SMS section to it. Here is a template you can adapt — replace [Boutique Name] and the contact details with your own:

SMS Messaging

[Boutique Name] sends SMS messages to customers who provide their mobile phone number. These messages may include appointment confirmations, appointment reminders, follow-ups after your visit, and occasional promotional offers (such as trunk shows or special events).

By providing your phone number when booking an appointment or otherwise opting in, you consent to receive these messages. Message frequency varies. Message and data rates may apply. You can reply STOP at any time to unsubscribe, or reply HELP for assistance.

We do not sell or share your phone number or SMS opt-in data with third parties for marketing purposes. For questions about our SMS practices, contact us at [email] or [phone].

The last paragraph about not sharing opt-in data with third parties is required — don't remove it.

2. Add your privacy policy URL to CloudBridal

Once your privacy policy is published, add its URL in CloudBridal under Settings > General > Privacy Policy URL. CloudBridal's booking form always shows an SMS disclosure explaining that booking means the customer will receive texts about their appointments and orders — once your privacy policy URL is set, the disclosure links to it automatically. You don't need to build anything yourself.

Two related options live in your appointment settings:

• Offer an optional marketing text opt-in during booking — adds an optional, unchecked checkbox so customers can opt in to marketing texts. It never blocks booking.
• Customize the SMS disclosure message — replaces the default disclosure wording if your registration needs specific language.

If you also accept bookings through a non-CloudBridal channel (such as a contact form on your own website), make sure that form also has a short SMS disclosure near the phone number field.

3. Link the privacy policy from your website footer

Twilio reviewers will visit your website and look for the privacy policy — make sure it's linked from your footer so it's easy to find.

Step 1: Register Your Brand

1. In the Twilio Console, navigate to Messaging > Regulatory Compliance > Onboarding (you may also see this referred to as Trust Hub).
2. Choose the Brand tier you selected in the previous section — Sole Proprietor, Low Volume Standard, or Standard.
3. Enter your business information exactly as it appears on your tax records (see the checklist above). For Sole Proprietor, this is your personal legal name, address, email, and mobile number; for the Standard tiers, your legal business name and EIN.
4. Sole Proprietor only: Twilio texts a one-time verification code to the mobile number you provided. You must reply within 24 hours or the Brand is not approved. The same mobile number can only be used for up to three A2P Brand registrations industry-wide, so use your own number, not a consultant's.
5. Submit and wait for approval. Sole Proprietor Brands are usually approved within a few minutes of completing the verification. Low Volume Standard and Standard Brands can take up to 1–2 business days if manual review is triggered.

Step 2: Register Your Campaign

Once your Brand is approved, you create a Campaign that describes how you intend to use SMS.

1. In Twilio, start a new Campaign under your approved Brand.
2. For use case: if you registered a Sole Proprietor Brand, there is only one option — the Sole Proprietor use case — and it covers both appointment-related and occasional promotional messages. If you registered a Standard tier, select Mixed, which covers appointment-related SMS (confirmations, reminders, follow-ups) and occasional promotional messages (trunk shows, sales, special events) under a single Campaign.
3. Write a clear campaign description (2–4 sentences). Example:

4. Provide sample messages. Twilio requires at least two, and they should match the use case you selected. Include your business name, clear purpose, and the opt-out instruction in every sample. Here are four that typically approve cleanly for a bridal boutique — submit any two or more:

5. Describe your opt-in flow. Reviewers want to see that customers actively consent. Example:

Two things to watch here:

• Don't claim verbal opt-in for marketing texts. Carriers accept verbal consent for appointment-related (transactional) messages, but marketing consent must be written or digital — that's what the optional checkbox on the booking form is for. Describing verbal marketing opt-in is a rejection reason.
• Make sure the marketing opt-in checkbox is actually on your form. It's on by default in CloudBridal ("Offer an optional marketing text opt-in during booking" in appointment settings) — if you've turned it off but your Campaign includes promotional messages, reviewers will look for it and not find it.

6. Upload or link to your privacy policy and opt-in disclosure screenshot if prompted. For the screenshot, capture the contact-details step of your CloudBridal booking form showing the SMS disclosure and the unchecked marketing opt-in checkbox.
7. Submit. Campaign review is a manual vetting process that typically takes 1–3 weeks depending on Twilio's current queue.

Costs and Timeline

Twilio charges a one-time Brand registration fee, a recurring monthly Campaign fee, and a small per-message surcharge. Sole Proprietor is the cheapest tier, Low Volume Standard is next, and Standard is the most expensive. See Twilio's current pricing page for exact numbers.

Timeline from start to being able to send: Brand approval is fast (minutes for Sole Proprietor, up to 1–2 business days for Standard tiers), but Campaign vetting is manual and typically takes 1–3 weeks regardless of tier. Budget 2–4 weeks end to end, assuming your business information matches IRS records cleanly and your website has a compliant privacy policy in place before you submit.

Common Rejection Reasons and How to Avoid Them

If your Brand or Campaign is rejected, it's almost always one of these:

• Registered as Sole Proprietor while the business has an EIN. Any LLC or corporation has an EIN and must register as Low Volume Standard. This is the most common tier mistake.
• Business name or address doesn't match IRS records. Copy the name and address exactly as they appear on your tax documents. "ABC Bridal LLC" is not the same as "ABC Bridal" to Twilio's verifier.
• No privacy policy, or privacy policy doesn't mention SMS. Add the SMS section described above and make sure the policy is linked from your website footer.
• Privacy policy doesn't say you don't share opt-in data with third parties. Include this line explicitly.
• No visible SMS disclosure on your booking form. CloudBridal's booking form shows the SMS disclosure automatically — set your privacy policy URL under Settings > General so the disclosure links to it. If you also collect phone numbers through a non-CloudBridal form, add a short disclosure there too.
• Consent is required to complete the transaction. Forcing customers to tick an "I agree to receive texts" box before they can book is itself a rejection reason — consent can't be a condition of the purchase. CloudBridal's booking form avoids this by design (disclosure plus optional marketing opt-in).
• Website doesn't load, is under construction, or doesn't describe the business. Twilio's reviewers will visit. Make sure the site is live and clearly identifies your business.
• Sample messages are too generic or don't include your business name. Every sample must include [Boutique Name] and the opt-out language. Vague samples like "Hi, your appointment is confirmed" will be rejected.
• Sample messages don't match the declared use case. If you pick Mixed, include at least one promotional example. If you pick Customer Care only, don't include marketing samples.
• Sample messages contain a public link shortener. bit.ly, tinyurl, and similar shared shorteners are rejected outright. Use your own domain, written out in full.
• Verbal opt-in claimed for marketing messages. Verbal consent only passes for transactional (appointment) messages — marketing consent must come from a written or digital opt-in like the booking form's checkbox.
• Opt-in description doesn't match what reviewers see on your website. If you tell Twilio opt-in happens via a disclosure on your booking form, reviewers need to find that disclosure on the form they visit.
• Using a generic email (info@, admin@) for the authorized contact. Use a named person's email.

If You're Rejected

Twilio's rejection email will include a reason code. Match it against the list above, fix the specific issue, and resubmit — you don't need to start over. Most boutiques who get rejected are approved on their second attempt after adding or tightening the privacy policy and opt-in disclosure.

If the rejection asks for specific wording on your booking form that the default disclosure doesn't include (for example, a link to messaging terms and conditions), use Customize the SMS disclosure message in your appointment settings to add exactly the language the reviewer asked for.

After Approval

Once your Campaign is approved and your Twilio phone number is attached to it, return to the Twilio Integration setup guide and finish the plugin configuration in CloudBridal. Send a test message from a customer record to confirm everything is working end-to-end.

Updated on: 14/07/2026