> For the complete documentation index, see [llms.txt](https://help.ourarea.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.ourarea.in/ss/phone-system/a2p-registration-17/updated-messaging-policies-for-canadian-10dlc-numbers-a2p-registration-requirements.md).

# Updated Messaging Policies for Canadian 10DLC Numbers: A2P Registration Requirements

To align with industry standards, we are updating our messaging policies concerning Canadian 10-digit long code (10DLC) numbers. These changes pertain to messages sent from Canadian numbers to recipients in both the United States and Canada.

<br>

**Key Changes:**

1. **Messaging from Canada to the United States:**
   * Effective immediately, all messages sent from Canadian 10DLC numbers to U.S. recipients must originate from Application-to-Person (A2P) registered numbers. This requirement applies to both new and existing Canadian numbers.
2. **Messaging within Canada:**
   * For new Canadian 10DLC numbers purchased after 26th March 2025, A2P registration is mandatory to send messages to Canadian recipients.
   * Existing Canadian 10DLC numbers used for messaging within Canada are not required to undergo A2P registration at this time, except as noted in point 1.

<br>

**Important Notes:**

* These updates apply exclusively to 10DLC numbers. Toll-Free (TF) numbers are not affected and will continue to operate under existing guidelines.

<br>

**Understanding A2P 10DLC Registration:**

A2P 10DLC is a system that allows businesses to send Application-to-Person type messaging via standard 10-digit long code phone numbers. Registering your numbers under this framework helps ensure compliance with carrier regulations and enhances message deliverability. For a comprehensive overview of A2P 10DLC and answers to common questions, please refer to our [support article.](https://help.gohighlevel.com/support/solutions/articles/155000002380-what-is-a2p-10-dlc-brand-and-campaign-registration-summary-and-faqs)

<br>

**Action Steps:**

* **For Existing Canadian 10DLC Numbers Messaging to the U.S.:** If your number is not yet A2P registered, please initiate the registration process promptly to comply with the new requirements.
* **For New Canadian 10DLC Numbers:** Ensure A2P registration is completed before initiating messaging to recipients in either the U.S. or Canada.
* **For Toll-Free Numbers:** No action is required; existing policies remain in effect.

<br>

**How to Register:**

To register your Canadian 10DLC numbers for A2P messaging, please follow the step-by-step instructions provided in our [Campaign Registration Guide](https://help.gohighlevel.com/support/solutions/articles/155000004539-campaign-registration-step-by-step-guide-and-faqs). This guide offers detailed information on the registration process, including best practices to ensure approval.

<br>

**Support:**

We understand that these changes may raise questions or require adjustments to your current messaging practices. Our support team is available to assist you through this transition.

Thank you for your attention to these updates and for your continued trust in our services.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.ourarea.in/ss/phone-system/a2p-registration-17/updated-messaging-policies-for-canadian-10dlc-numbers-a2p-registration-requirements.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.