A2P SMS Sender Qualification: An Operational Guide

Sender identity should not be reviewed in isolation

A2P describes messages sent from an application to a person. It can cover uses such as authentication, transactional alerts, notifications, and marketing. To assess a sender, link four elements: who authorizes it, which entity or brand it represents, what types of messages it will send, and where it will be used.

The review helps determine whether the available information and evidence are consistent and sufficient to continue the process. It does not replace the applicable official rules or checks that operators, aggregators, or registration platforms may require.

It also does not, by itself, determine route quality or guarantee that an operator will accept or deliver every message. Sender qualification, route eligibility, and delivery outcomes are separate matters.

What information and evidence to collect

Create a file for each sender and record the information so it can be compared with official sources for the destination. Do not assume that a particular document will be valid in every market: the required evidence depends on the applicable conditions.

At a minimum, include the following details and note their source and the date checked:

• Responsible entity: legal name or registered company name, and details that distinguish it from other entities with similar names.
• Authorization: the person or role requesting the sender, and evidence that they can act on behalf of the stated entity or brand.
• Displayed name: the proposed sender ID and an explanation of how it relates to the represented brand or entity.
• Purpose: a specific description of the use case, such as authentication codes, transactional alerts, or promotional messages. If multiple uses are planned, document them separately.
• Destination: the intended countries or markets and, where applicable, the type of numbering or sender ID to be used.
• Supporting documents: forms, registration records, authorizations, or other documents requested by the official source or applicable process. Record what each document establishes—and what it does not establish.
• Internal owner: the person or team reviewing the file and the channel for requesting clarification.

Check official requirements for each destination

The available information does not include a reliable matrix of A2P sender requirements by country. Therefore, do not reuse a rule from another destination or present brand or campaign registration in one market as a universal requirement.

For each intended destination, first consult the relevant official sources: the regulator, operator documentation, or registration platform identified by them. Confirm which senders and uses the rule covers, what documents it requires, how approval is obtained if applicable, and whether there are additional conditions.

Distinguish three statuses in the file: information registration, approval or authorization, and other conditions of use. Do not treat them as equivalent; use only the definitions provided by the official source consulted. If you cannot verify a requirement or whether it is current, record the uncertainty and request confirmation before enabling traffic.

• Record the official link consulted, the date checked, and the destination it applies to.
• Keep the response or reference supporting the decision, together with the version of the documents submitted.
• If official information is unclear, mark the case as pending; do not fill gaps with assumed practices from other markets.

Qualification workflow and decision records

A documented workflow helps reduce inconsistent decisions and makes it easier to recheck the file. The following steps are an operational practice for organizing the review; they are not a universal standard and do not replace official requirements.

1. Collect the sender’s details and supporting documents, along with information about the entity, brand, purpose, and intended destinations. 2. Check each element against the applicable source. 3. Confirm that names, authorizations, uses, and destinations are consistent. 4. Record what was verified, what remains pending, and why. 5. Assign a decision owner and a date or condition for reviewing the case again.

• Approved to proceed: the available evidence is consistent, and known applicable conditions have been confirmed. This does not guarantee acceptance or delivery.
• Pending information: documents, clarification, or official confirmation is missing. Keep the sender disabled for destinations or uses that have not been clarified.
• Not approved: there is a material inconsistency, sufficient authorization is missing, or the applicable source does not permit the proposed use. Record the reason and, where applicable, what information could allow reconsideration.
• Record who made the decision, when, which destinations and purposes it covers, and what evidence was consulted.

Discrepancies, changes, and exceptions

If the entity’s name does not match the displayed brand, do not assume the relationship is valid. Request an explanation and evidence of the relationship or authorization, and compare it with the destination’s requirements. Apply the same caution if the person requesting the sender does not appear to represent the stated entity.

A change to the brand, purpose, responsible entity, or intended markets may affect the assessment. Record the change and check which official requirements are affected before extending use. If the new scope has not been verified, limit the decision to the scope already reviewed.

Exceptions should have a documented scope, reason, approver, and review deadline or condition. If essential evidence is missing or there are conflicting indications, do not turn the exception into general enablement or authorization for destinations that have not been reviewed.

What sender qualification does not prove

A review of identity, brand, purpose, and destination does not prove that recipients have given their consent. Consent and privacy or messaging obligations must be assessed separately, in accordance with applicable rules.

Qualification also does not prove ownership of a number, route eligibility, operator acceptance, or message receipt on the device. A reported delivery status should not automatically be confused with verified receipt on the device.

HLR lookups may provide network information depending on the service used, but they do not prove consent, identity, number ownership, or guaranteed delivery. Keep these checks separate in records and operational decisions.

Checklist before enabling a sender

Use this checklist as a final control. If an answer is no or unknown, pause enablement for the affected scope and request the relevant evidence or clarification.

The decision should reflect what was actually verified, not what is expected to be true. Review the file when the brand, purpose, entity, or destinations change.

• Is the responsible entity identified, and is the requester’s authority documented?
• Is it clear which entity or brand the displayed name represents, and is there sufficient evidence of that relationship?
• Is each messaging purpose described and distinguished from other intended uses?
• Are the specific destinations listed, and have relevant official sources been checked for each one?
• Are registration, approval, and other conditions distinguished according to the source consulted?
• Have discrepancies, outstanding evidence, and the scope approved to proceed been recorded?
• Is there a decision owner and a date or condition for reviewing changes?
• Does the decision avoid presenting qualification as proof of consent, route eligibility, or delivery?