Four Things That Are Not the Same Thing
| Term | What it means here |
|---|---|
| Canadian phone number | A number issued in Canada that you send from: a Canadian 10DLC local number or a Canadian toll-free number |
| Canadian recipient | A person whose phone number receives the message, regardless of who sent it |
| Canadian business | The company registering the Brand, which may or may not match where the number was purchased |
| Canadian 10DLC vs Canadian Toll-Free | Two different number types with two different compliance processes; this guide is mainly about the 10DLC one |
The rule that actually governs your situation depends on the route, meaning the combination of sending number and recipient country, not simply on whether "Canada" is involved somewhere. A Canadian business can trigger US rules by texting a US contact. A US business can trigger the same domestic requirement by texting a Canadian contact. Keep sender and recipient separate through the rest of this guide.
Does A2P 10DLC Apply to Canadian Numbers?
Sometimes, and the answer changes by route. HighLevel's current documentation frames domestic messaging within the US, Canada and Puerto Rico as requiring A2P registration, with one specific carve-out for older Canada-only numbers. So the honest short answer is not "no" and not "always yes"; it is "check the route below."
Canadian 10DLC Decision Table
| Route | Number purchase date | Requirement | Notes |
|---|---|---|---|
| Canada → United States | Any date | A2P registration required | Persona does not substitute here |
| Canada → Canada | Before March 26, 2025 | A2P not required for this route | Consent, content and carrier rules still apply |
| Canada → Canada | On or after March 26, 2025 | A2P or Persona | Either path is valid; Persona is not required if A2P is completed |
| Canada → Puerto Rico | Any date | A2P registration required | Treated as domestic, not the CA → CA exception |
| Canada → International (outside US/Canada/PR) | Any date | Persona verification only | A2P is not required for this route |
| United States → Canada | Any date | A2P registration required | Domestic messaging rule applies to the sending US number |
| United States → United States | Any date | A2P registration required | Standard US A2P 10DLC |
| Canadian Toll-Free (either direction) | Not applicable | Toll-Free Verification, not A2P | See Toll-Free vs A2P 10DLC |
This table reflects two HighLevel articles read together: its Canadian 10DLC policy (updated September 4, 2026) and its broader US and Canada messaging guidelines (updated August 11, 2026). The second one is what confirms that US → CA is a domestic route requiring A2P, and that CA → PR is domestic too, not covered by the CA → CA exception.
Canada to Canada Messaging
This is the one route with a purchase-date exception, and it is worth restating precisely because it is easy to over-generalize.
- Purchased before March 26, 2025: A2P registration is not required for Canada-only messaging on that number. This exemption is scoped to the A2P registration requirement specifically. HighLevel is explicit that consent, prohibited content, carrier filtering, opt-out and other messaging requirements still apply regardless.
- Purchased on or after March 26, 2025: the number can send Canada-only messages once either A2P Brand and Campaign registration or Persona identity verification is complete. Neither is mandatory over the other for this specific route; you pick one.
Do not read the pre-2025 exemption as "this number is exempt from everything." It is exempt from A2P for Canada-only traffic. The moment that number messages a US recipient, a completely different rule takes over, covered next.
Canada to United States Messaging
HighLevel's rule here has no exceptions: A2P registration is required when a Canadian 10DLC number sends SMS or MMS to US recipients, regardless of when the number was purchased. HighLevel states plainly that Persona verification does not replace A2P registration on this route, and that relying on Persona alone for CA to US messaging is not sufficient.
Practically, this means completing an approved Brand, an approved Campaign, and associating the sending number with that Campaign before any US-bound message goes out. The field-level process is the same as the standard walkthroughs in A2P Brand Registration and A2P Campaign Registration; this guide will not repeat those steps. For a Canadian Standard Brand, use the BN-9 format, the first nine digits of the Business Number, entered exactly as it appears in official records, per HighLevel's Brand Approval guidance.
United States to Canada Messaging
This is the direction the older version of this guide did not clearly address, and it is not automatically the same as the Canada-to-US rule. HighLevel's US and Canada messaging guidelines treat this as ordinary domestic messaging: any message sent between US, Canada or Puerto Rico numbers, including US to CA, must originate from a registered A2P number. There is no Canadian-recipient exception on this side, and no purchase-date carve-out, because the exemption in HighLevel's Canadian policy applies specifically to Canadian numbers sending Canada-only traffic, not to US numbers sending to Canada.
What Changed on March 26, 2025
Before that date, HighLevel did not require A2P or Persona for Canadian numbers sending Canada-only messages. From that date forward, newly purchased Canadian 10DLC numbers need one of the two paths for Canada-only sending. What the date does not do:
- It does not touch Canada to US messaging, which has always required A2P regardless of purchase date.
- It does not exempt pre-2025 numbers from consent, content or carrier rules.
- It does not apply to toll-free numbers at all.
- It does not retroactively require anything of numbers purchased earlier, as long as they stay on Canada-only traffic.
If you are not sure when a number was purchased, HighLevel's guidance is to contact Support with the phone number and Location ID before choosing a compliance path, rather than guessing.
A2P Registration vs Persona Verification
These solve different problems and are not interchangeable outside the one scenario where HighLevel allows either.
| A2P Brand and Campaign | Persona | |
|---|---|---|
| What it verifies | The sender's business identity and the specific messaging use case, reviewed against the A2P 10DLC ecosystem | The identity associated with the sub-account |
| Where it applies here | Required for Canada to US, Puerto Rico, and any US route. Also valid for Canada to Canada | Only as an alternative for Canada to Canada, on numbers purchased on or after March 26, 2025 |
| Frequency | Per Brand and Campaign | Generally completed once per sub-account, per HighLevel |
Persona is not a lighter version of A2P that happens to work everywhere Canada is involved. It is a specific alternative for one specific route. Using it for Canada to US traffic, expecting it to hold, is one of the most common mistakes covered below. Persona itself is described in HighLevel's identity verification guide.
International Messaging From Canadian Numbers
For messages sent from a Canadian (or US) number to a destination outside the US, Canada and Puerto Rico, HighLevel's guidance is that A2P registration is not required and Persona verification alone is what's needed. If neither A2P nor Persona is in place on a route that needs one of them, HighLevel returns error 1002, message blocked. This guide does not cover Toll-Free international behavior or the separate UK exception HighLevel documents; that is outside Canadian-number scope.
Canadian Toll-Free Numbers
Toll-free numbers, Canadian or US, do not use A2P 10DLC Brand and Campaign registration at all. They go through Toll-Free Verification instead, a separate process covered in HighLevel's Toll-Free Verification guide and compared to A2P in Toll-Free vs A2P 10DLC. None of the purchase-date rules on this page apply to a toll-free number.
Consent Is Not the Same as Registration
A2P registration and Persona verification are telecom-ecosystem mechanisms. They tell carriers who is sending and, for A2P, what the messaging program is. Neither one is legal consent from the recipient, and completing either does not by itself satisfy Canadian legal requirements.
If your recipients are in Canada, Canada's Anti-Spam Legislation (CASL) is the relevant framework to be aware of. Per the CRTC, sending a commercial electronic message, which explicitly includes SMS text messages, generally requires the recipient's prior consent, sender identification information in the message, and a working unsubscribe mechanism; CASL applies to messages received in Canada even when sent from outside the country. This guide is not legal advice, and CASL's exact application to your messaging program, including which consent category applies and how the identification and unsubscribe requirements should be implemented, is a question for your own counsel. For consent language and opt-in evidence generally, see A2P opt in language and requirements.
Trust Score, MPS and Canadian Numbers
HighLevel's Trust Score and MPS documentation describes throughput for US Standard Brands specifically, tied to secondary vetting performed as part of that registration. I found no HighLevel documentation stating that this same Trust Score and MPS model applies to Canadian 10DLC numbers, to Persona-verified numbers, or to Canadian toll-free numbers. Treat Canadian throughput as a separate, undocumented question rather than assuming the US tables in A2P Trust Score and MPS carry over, and confirm current behavior with HighLevel Support if throughput matters to your Canadian sending volume.
What Canadian Businesses Need Before Sending SMS
Identify every route you actually use. Canada-only, Canada to US, US to Canada, and international are four different questions.
Know your Canadian number's purchase date, if the route is Canada to Canada. Contact HighLevel Support if you cannot confirm it.
Choose A2P or Persona for a qualifying Canada to Canada number, or go straight to A2P if any US recipients are in scope.
For Standard Brand registration, have your legal business name and BN-9 exactly as recorded, business address, website, use case, sample messages and consent evidence ready.
Confirm your consent process actually satisfies your recipients' jurisdiction, not just the registration form.
Test on the real route with a genuinely opted-in recipient before relying on any automation.
What Happens If You Expand From Canada to the US
A Persona-only setup stops being sufficient the moment US recipients enter the picture. HighLevel's guidance is explicit: if a Canada-only messaging program later begins messaging US recipients, the Persona-only path is no longer sufficient and A2P registration becomes required before that traffic goes out. In practice this means completing Brand and Campaign registration and confirming the number is associated with the approved Campaign, not just checking a box somewhere. A common way this actually happens is not a decision at all: a CRM database gets US contacts added to it, and an existing automation quietly starts targeting them. If you are not certain your contact list is Canada-only, assume it is not, and complete A2P registration before the workflow runs.
Canadian Clients for Agencies
Everything above applies per number, per sub-account, the same as it does for a single business. An agency managing Canadian clients needs to track, for each client: which country the client's numbers were purchased in, which routes that client actually sends on, the purchase date for any Canada-only Canadian number, and whether A2P or Persona was completed. This is a subset of the broader multi-client tracking problem, covered in A2P registration for GoHighLevel agencies; this page does not repeat that operational framework.
Common Mistakes
- Assuming every Canadian number is exempt from A2P, rather than checking the route
- Ignoring the destination country and looking only at the sending number
- Treating the March 26, 2025 date as if it affects Canada to US messaging
- Using Persona for Canada to US traffic
- Assuming US to Canada messaging needs nothing because the recipient is "just Canadian"
- Confusing Canadian 10DLC with Canadian Toll-Free
- Treating A2P or Persona approval as proof of legal consent
- Launching a workflow before confirming which recipients are actually in the contact list
- Applying the US Trust Score and MPS tables to Canadian numbers without verification
Canadian SMS Decision Framework
Where is the recipient: Canada, US/PR, or international?
What type is the sending number: Canadian 10DLC, Canadian Toll-Free, or US?
If Canadian 10DLC and the route is Canada to Canada, what is the purchase date?
If the route touches the US or Puerto Rico in either direction, go straight to A2P registration.
If the route is Canada to Canada and the number is post-March 26, 2025, choose A2P or Persona.
If the route is international, confirm Persona verification.
If the number is toll-free, use Toll-Free Verification instead of any of the above.
Verify your consent process separately, regardless of which registration path applies.
Test on the real route with a real opted-in recipient before launching.
Canadian Messaging Checklist
Recipient countries for this number identified
Sending number type confirmed (Canadian 10DLC, Canadian Toll-Free, or US)
Purchase date confirmed, if Canada-only 10DLC
Correct path chosen: A2P, Persona, Toll-Free Verification, or none required
BN-9 and legal name match CRA records, if registering a Canadian Standard Brand
Consent process reviewed against CASL where recipients are in Canada
Contact list checked for any US numbers before activating a Canada-only automation
Test message sent on the real route
Frequently Asked Questions
Do Canadian numbers need A2P 10DLC registration?
It depends on the route. Canada to US always needs A2P. Canada to Canada needs A2P only if the number was purchased on or after March 26, 2025, and even then Persona is a valid alternative. Toll-free numbers never use A2P.
Do I need A2P if I only send to Canadian recipients?
Only if your Canadian 10DLC number was purchased on or after March 26, 2025, and even then you can choose Persona instead. Numbers purchased before that date do not need A2P for Canada-only traffic.
Can Persona replace A2P for messages to the US?
No. HighLevel is explicit that Persona does not replace A2P registration when a Canadian number sends to US recipients.
Does a US number sending to Canada need A2P?
Yes. HighLevel treats US to Canada as domestic messaging requiring A2P registration, with no Canadian-recipient exception.
What Tax ID do Canadian businesses use for Standard Brand registration?
The BN-9 format, the first nine digits of the CRA Business Number, entered exactly as it appears in official records.
Do Canadian toll-free numbers need A2P registration?
No. They use Toll-Free Verification, a separate process from A2P 10DLC.
What happens if I send without the required registration?
A route requiring A2P without it returns error 30034. A route requiring A2P or Persona with neither completed returns error 1002.
Does completing A2P or Persona satisfy CASL?
No. These are separate telecom registration and identity mechanisms. Recipient consent, sender identification and unsubscribe requirements under CASL are a distinct question; consult counsel for your specific program.
Does Trust Score apply to Canadian numbers?
HighLevel's Trust Score and MPS documentation covers US Standard Brands specifically. I found nothing confirming the same model applies to Canadian numbers, so don't assume it does.
What if I don't know when my Canadian number was purchased?
Contact HighLevel Support with the phone number and Location ID before choosing a compliance path.
Still have questions about Canadian A2P requirements?
Talk to our A2P specialists directly. We've handled Canadian A2P registrations and can help you understand your specific requirements.
Related Articles
Need A2P registration for your Canadian GHL numbers?
GHL Scale Up handles Canadian and US A2P registration for agencies and their clients. BN-9 verification, brand registration, campaign submission, and rejection troubleshooting end to end.
Book Your Free Strategy Call
This guide was checked against HighLevel's Canadian 10DLC A2P Registration Requirements (updated September 4, 2026), its Updated Messaging Guidelines for the U.S. & Canada (updated August 11, 2026), its Persona identity verification guide, and the CRTC's CASL FAQ, current as of September 2026. Requirements change, so confirm current rules in your Trust Center. This is not legal advice.
ghlscaleup.com