Canadian 10DLC messaging requirements depend primarily on where the message is being sent and, for Canada-to-Canada traffic, when the Canadian number was purchased. Messages sent from a Canadian 10DLC number to U.S. recipients require approved A2P 10DLC registration, while qualifying Canada-only traffic may use Persona verification instead.
Use this guide to determine which registration path applies before sending messages and to understand what changes if your messaging route expands later.
These rules apply specifically to Canadian 10-digit long code numbers. Toll-free numbers use a separate Toll-Free Verification process.
Persona verification does not replace A2P registration when a Canadian 10DLC number sends messages to U.S. recipients. Persona is an alternative only for qualifying Canada-to-Canada messaging from Canadian numbers purchased on or after March 26, 2025.
What is Canadian 10DLC A2P Registration?
A2P 10DLC registration identifies the business sending application-to-person messages and the messaging use case associated with those messages. For Canadian long-code numbers, whether A2P is required depends on the destination of the message and, for Canada-only traffic, the date the number was purchased.
A complete A2P setup includes an approved Brand, an approved Campaign, and the applicable sending phone number being associated with that Campaign. Persona verification is a separate identity-verification process and can be used instead of A2P only for specific Canadian messaging routes described below.
Toll-free numbers: Toll-free numbers do not use A2P 10DLC registration. They must follow the separate Toll-Free Verification process before eligible SMS/MMS traffic can be sent.
Key Benefits of Understanding Canadian 10DLC Requirements
Choosing the correct verification path before sending messages helps prevent avoidable delivery failures and ensures your registration matches the destination and use case you actually intend to use.
- Route Clarity: Know immediately whether CA → CA or CA → US traffic requires A2P, Persona, or no additional A2P registration.
- Fewer Delivery Blocks: Avoid sending from a Canadian number before the required verification path is complete.
- Correct Registration Path: Avoid using Persona where an approved A2P Brand and Campaign are required.
- Easier Expansion: Understand what must change if a Canada-only messaging program later begins messaging U.S. recipients.
- Faster Troubleshooting: Distinguish registration issues, Campaign-linking issues, and unrelated carrier or content filtering.
Canadian 10DLC Registration Decision Table
The fastest way to determine the correct compliance path is to identify the message destination first, then check the number purchase date only when the traffic remains entirely within Canada.
| Messaging Route | Number Purchase Date | Requirement | What to Do |
|---|---|---|---|
| Canada → United States | Any purchase date | A2P required | Complete Brand and Campaign registration, receive approval, and associate the sending number with the approved Campaign. |
| Canada → Canada | Before March 26, 2025 | A2P not required for this route | Continue Canada-only messaging while following all applicable consent, content, and carrier requirements. |
| Canada → Canada | On or after March 26, 2025 | A2P or Persona | Complete A2P registration or complete Persona identity verification if you choose not to register for A2P. |
| Toll-Free Messaging | Not applicable | Separate Toll-Free Verification | Follow the Toll-Free Verification workflow instead of A2P 10DLC registration. |
A2P Registration vs. Persona Verification
A2P and Persona solve different compliance needs. A2P registers the sender and messaging use case with the carrier ecosystem, while Persona verifies the identity associated with the sub-account. Treating them as interchangeable outside the qualifying CA → CA scenario can cause messaging failures.
| Verification | Purpose | Where It Works in This Guide |
|---|---|---|
| A2P Brand & Campaign | Registers the sender identity and messaging use case with the A2P 10DLC ecosystem. | Required for CA → US. Also valid for CA → CA. |
| Persona | Verifies the identity associated with the sub-account. | Alternative to A2P only for CA → CA when the Canadian number was purchased on or after March 26, 2025. |
Already Persona verified? Persona is generally completed once per sub-account. If the sub-account has already successfully completed Persona, you typically will not be asked to repeat the identity-verification process for future supported compliance actions.
Rules by Messaging Route
The recipient's destination is the first decision point. A Canadian number that works without A2P for Canada-only messaging may require a completely different compliance path as soon as U.S. recipients are added.
A2P registration is required when a Canadian 10DLC number sends SMS or MMS to U.S. recipients. This applies regardless of when the Canadian number was purchased.
Do not rely on Persona alone for this route. Complete the applicable Brand and Campaign registration and confirm the sending number is associated with the approved Campaign before sending.
A2P registration is not required for Canada-only messaging from qualifying Canadian 10DLC numbers purchased before March 26, 2025.
This exemption applies to the A2P registration requirement only. Consent, prohibited-content, carrier-filtering, opt-out, and other messaging requirements still apply.
Canada-only messaging can proceed using either:
- A2P Brand & Campaign registration, or
- Persona identity verification if you choose not to complete A2P.
If the messaging program later expands to U.S. recipients, the Persona-only path is no longer sufficient and A2P registration becomes required.
How to Set Up Canadian 10DLC Messaging Compliance
Complete only the verification path that matches your sending route. Correct setup before messaging helps prevent registration-related failures and avoids unnecessary rework if the same number will later be used for U.S. traffic.
Determine whether the Canadian 10DLC number will send messages only to Canadian recipients or whether any messages will be sent to U.S. recipients.
If the route is CA → CA, determine whether the number was purchased before March 26, 2025 or on/after March 26, 2025. If you cannot confirm the original purchase date, contact Support with the phone number and Location ID before selecting a compliance path.
- Go to Settings → Phone System → Trust Center.
- Under A2P Messaging (SMS), start or open your registration.
- Complete the appropriate Brand registration.
- After the Brand is eligible, complete the required Campaign registration, including messaging use case, sample messages, and consent details.
- Wait until the required Brand and Campaign reviews are approved.
- Confirm the Canadian sending number is associated with the approved Campaign before sending A2P traffic.
Canadian Standard Brands: When a Canadian registered business uses a Standard Brand, use the accepted Canadian BN-9 format—the first nine numeric digits of the Business Number. Enter the legal business information exactly as it appears in official records.
For the detailed workflows, see Registering Your A2P Brand and A2P Campaign Registration: Step by Step Guide and FAQs.
If the Canadian number was purchased on or after March 26, 2025, will message only Canadian recipients, and you choose not to register for A2P, complete Persona identity verification when prompted.
Persona is generally a one-time verification per sub-account. For details, see Identity Verification for Phone Number Purchases.
After the applicable verification is complete, test with a legitimate opted-in recipient on the intended route. If a message fails, review the displayed error and confirm the number's registration and Campaign association before changing message content or routing.
Troubleshooting Canadian 10DLC Messaging
A failed message does not always mean the Canadian-number policy itself is wrong. Check the route, verification path, number-to-Campaign association, and message compliance separately to identify the actual cause.
| Issue | What to Check |
|---|---|
| CA → US message fails with Error 30034 | Confirm the Brand and Campaign are approved and that the sending number is associated with the approved Campaign. Newly approved registrations may also require time to propagate across carriers. |
| Newer CA → CA number cannot send | Confirm that either A2P registration or Persona verification has been successfully completed. |
| Older CA → CA number still has delivery failures | The pre-March 26, 2025 exemption removes the A2P requirement for that route only. Review recipient consent, opt-out status, carrier filtering, prohibited content, number status, and the specific delivery error. |
| Toll-free number cannot send | Do not troubleshoot it as a Canadian 10DLC A2P issue. Check the number's Toll-Free Verification status instead. |
| Messaging destination changed | Re-evaluate the compliance path. A Persona-only Canadian number must complete A2P before it begins messaging U.S. recipients. |
A2P approval does not guarantee every message will be delivered. Carrier filtering, prohibited content, recipient opt-outs, consent requirements, number configuration, and other messaging policies can still affect delivery.
Frequently Asked Questions
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article