01Who this is for
- Agency owners who manage multiple client phone numbers need the correct verification path to keep campaigns operating without delivery errors.
- Ecommerce businesses that text U.S. customers from a Canadian number must complete A2P registration to satisfy carrier requirements.
- Healthcare providers sending appointment reminders within Canada benefit from the Persona alternative for newer numbers.
02Canadian 10DLC messaging compliance, explained
The feature identifies the compliance method for Canadian 10 digit long code numbers. It checks whether messages are sent to Canada only or also to the United States, then requires either A2P Brand & Campaign registration or Persona identity verification.
A2P registration registers the sender and use case with the carrier ecosystem, while Persona only verifies the subaccount holder’s identity for qualified Canada only traffic. The settings live under Settings > Phone System > Trust Center in the platform.
03How businesses use canadian 10DLC messaging compliance
- Digital marketing agency. The agency selects A2P registration for a client’s Canadian number that sends promotional SMS to U.S. leads. It registers the Brand, creates a Campaign, and links the number before launching the campaign.
- Local retail store. The store’s newly purchased Canadian number (after March 26 2025) sends only Canada based order updates. It completes Persona verification instead of A2P, avoiding the brand registration steps.
- Non profit organization. The organization’s older Canadian number (before March 26 2025) sends donation confirmations within Canada. It proceeds without A2P registration, ensuring compliance while focusing on consent and content rules.
04The numbers and rules that matter
- Messages from a Canadian 10DLC number to U.S. recipients require approved A2P registration.
- Persona verification can replace A2P only for Canada only messages from numbers purchased on or after March 26 2025.
- Numbers purchased before March 26 2025 do not require A2P for Canada only traffic.
05Before you start
- Identify the intended messaging route (Canada only or Canada > U.S.).
- Know the purchase date of the Canadian 10DLC number.
06How to set up and use canadian 10DLC messaging compliance in HighLevel
Set up Canadian 10DLC compliance
- Determine whether the number will send messages to Canadian recipients only or also to U.S. recipients.
- If the route is Canada only, check whether the number was purchased before or on/after March 26 2025.
- If the purchase date is unknown, contact Support with the phone number and Location ID before selecting a compliance path.
- For any U.S. messaging, navigate to Settings > Phone System > Trust Center and start A2P registration.
- Under A2P Messaging (SMS), complete the Brand registration.
- After the Brand is approved, create and submit a Campaign with use case, sample messages, and consent details.
- Wait for Brand and Campaign approval, then associate the Canadian sending number with the approved Campaign.
- If the route is Canada only and the number was purchased on or after March 26 2025, complete Persona verification when prompted. Do not rely on Persona alone for U.S. messaging.
- Send a test message to an opted in recipient on the intended route and confirm successful delivery.
- Monitor the registration status and resolve any errors before sending production traffic.
07Settings that matter
- Trust Center. Hosts the A2P Messaging (SMS) workflow where Brand and Campaign registration are initiated.
- A2P Messaging (SMS). Controls the start or continuation of A2P registration for a Canadian long code number.
08Things to know before you rely on it
- A2P registration is mandatory for any Canada > U.S. SMS or MMS traffic, regardless of number purchase date.
- Persona verification can replace A2P only for Canada only traffic from numbers purchased on or after March 26 2025.
- Numbers bought before March 26 2025 are exempt from A2P for Canada only messaging, but all other compliance rules still apply.
- Toll free numbers follow a separate Toll Free Verification process and are not covered by these rules.
- A2P approval does not guarantee delivery; carriers may still block messages based on content, consent, or other policies.
09If something goes wrong
- CA > US message fails with Error 30034. Confirm the Brand and Campaign are approved and that the sending number is linked to the approved Campaign. Allow time for carrier propagation.
- Newer CA > CA number cannot send. Verify that either A2P registration or Persona verification has been successfully completed for that number.
- Older CA > CA number still has delivery failures. Review recipient consent, opt out status, prohibited content, number status, and the specific delivery error; A2P is not required for this route.
- Toll free number cannot send. Check the Toll Free Verification status instead of the Canadian 10DLC A2P workflow.
- Messaging destination changed. If a Persona only number begins messaging U.S. recipients, complete A2P Brand and Campaign registration and associate the number before sending.
10How it connects to the rest of HighLevel
- Step by step guide to A2P 10DLC brand and campaign registration A2P brand and campaign registration
- Guide to A2P 10DLC registration fees and monthly charges A2P fees
- Instructions for Persona identity verification for phone number purchases Persona verification
- HighLevel pricing and plans Pricing
- Start a 30 day HighLevel trial Free trial
Michael's take

When you have a Canadian 10DLC number that will reach U.S. customers, the extra verification steps help keep your messages from being blocked.
If your traffic stays strictly within Canada and your number was bought before the March 2025 cutoff, you can avoid the A2P or Persona steps, which can feel like extra work for low volume campaigns.