A2P 10DLC Registration for Agencies: A Client Setup Checklist

A2P 10DLC registration identifies the business and messaging use case behind application-sent texts using US local ten-digit numbers. For an agency, the practical task is to connect the correct client identity, campaign and sending numbers before launching that client's SMS workflow. Registration is a prerequisite for this route, not a guarantee that every message will arrive.

The agency's CRM setup and the provider's registration process are separate pieces of the launch. A successful CRM connection does not establish that the sender is approved. Keep both checks on the onboarding sheet so nobody treats a saved credential or a purchased number as permission to start a campaign.

Know which messaging route you are using

Twilio explains that application-sent SMS/MMS over ten-digit long-code numbers to US recipients requires registration, including messages sent through its platform by individuals. This is not limited to bulk marketing. Toll-free numbers and short codes use different processes; they are not shortcuts around sender requirements. See Twilio's A2P 10DLC overview.

Inventory the actual sender for each client before preparing an application. Record the number type, account owner, intended recipients and purpose. A small appointment-reminder workflow and a large promotional campaign may have different requirements, but low volume alone is not a reason to assume registration is unnecessary.

Do this separately for unrelated clients. An agency operating the software is not automatically the brand that should appear as the sender for every customer it serves.

Which 10DLC setup should an agency use?

Start with who owns the Twilio account and whose customers receive the messages. An agency workspace in Chirply does not determine the provider's registration route.

Twilio distinguishes an ISV sending for customers from one sending only for itself. Its ISV guide also explains how customer profiles, brands, campaigns and Messaging Services fit together. Review Twilio's ISV onboarding overview before choosing an account structure.

For your onboarding sheet, add a named owner beside every provider-side task and a separate owner for the Chirply connection. This prevents a common handoff gap: each person assumes the other checked the approval status. Keep provider credentials out of the shared sheet; store only non-secret references and the responsible person's name.

Prepare the brand and campaign information

Twilio's registration process includes a brand describing the sender and a campaign describing the messaging purpose and opt-in, opt-out and help arrangements. Choose the provider's current path for the business type rather than copying another client's application. Twilio's registration quickstart is the starting reference.

As an agency working file, collect the client's legal identity details, public website, authorized contact, intended message examples and the real consent journey. Verify each field with the client. Do not invent an identifier, borrow another business's details or describe a web form that is not actually published.

Keep screenshots or other evidence of the actual signup experience in the client's own onboarding records. Make sure the wording in the campaign description matches the service the customer sees. If the client changes its offer or collection method, review whether the registration also needs updating instead of assuming an old approval covers the new workflow.

Submission is not approval. Assign someone to check the provider's status and resolve requests for information. Record the current state and the date it was checked, rather than a promised launch date based on an assumed turnaround time.

Separate registration, consent and delivery

These are three different checks. Registration describes the sender and campaign. Consent concerns the recipient's permission. Delivery is the outcome of an individual message. An approved sender can still encounter delivery failures, and an existing contact record does not prove permission for every message type.

For a controlled launch, maintain a small acceptance sheet:

1. The sender identity matches the client whose message is being sent.
2. The actual signup path matches the campaign description.
3. The sending number is assigned as required by the provider.
4. The provider shows the required approval state, not merely a submitted request.
5. Your application respects opt-outs and does not re-enroll suppressed recipients.
6. A permitted test message reaches a team-controlled recipient and its status is reviewed.

If a test fails, record the provider's status and error details before editing the template repeatedly. Check the number, account restrictions and campaign state. Changing CRM software does not itself repair a registration problem at the carrier or provider.

What should you check when a 10DLC campaign is rejected?

Read the provider's actual rejection details before changing the application. Twilio's campaign troubleshooting guide is the reference for the reported issue. Use this agency triage sheet to collect evidence for the next review:

This sheet organizes your investigation; it does not replace the provider's instructions or establish approval. Record the rejection reason, evidence reviewed, correction owner and resubmission date. Keep the client's workflow inactive until the required checks are complete.

Where registration fits into Chirply setup

For a workspace using its own Twilio connection, open Settings → Integrations → Twilio and connect the account intended for that workspace. Chirply configures its supporting voice resources when the credentials are saved. Follow the Chirply Twilio setup guide for the connection and number workflow.

Complete A2P registration in Twilio for the relevant local-number messaging setup. Chirply does not grant carrier approval, and this guide does not promise an in-app registration service. Keep the provider approval check separate from the Chirply connection check.

In an agency pilot, use a single client workspace and confirm its identity before buying or importing a number. Review who owns the provider account, who pays registration and usage charges, and who will retain access if the client leaves. Put those responsibilities in the onboarding record before expanding to more accounts.

Then prepare one permitted SMS workflow. Verify the recipient and sending identity, confirm the plan includes the channel, and review suppression behavior before activation. Chirply's public plans describe channel availability; provider charges are separate. A subscription trial does not waive Twilio account or carrier requirements.

Budget and handoff without promising a launch date

Use the provider's current fee information for the exact registration route. Keep number rental, messaging usage, registration-related charges and the CRM subscription as separate budget lines. Do not quote a universal fee or approval time from a blog post when the actual account determines the applicable process.

For example, a fictional agency onboarding a plumbing company can prepare the CRM workspace and draft appointment reminders while the client's registration is reviewed. The draft stays inactive. The launch owner records approval, confirms the sender and tests the final message before the account begins messaging customers. This is an operating example, not a promise of a particular review time.

Hand the client a short record of the approved sender, account owner, support contact, workflow purpose and opt-out handling. Give the person maintaining the account enough context to diagnose failures without searching an old email thread. Revisit that record when numbers, ownership or message purposes change.

Start with the Twilio connection guide, then review Chirply's trial terms if you are evaluating the CRM. A card is required for the trial and provider usage is separate. Evaluate the workflow using controlled records while the provider registration is handled through the appropriate account.