A2P SMS Routing Rules: Priorities and Conflicts
A practical guide to thinking through A2P SMS routing priorities, conflicts, and testing—distinguishing operational suggestions from what the available sources support.
What a Routing Rule Can Describe
A routing rule can express what decision to make for a message that meets certain conditions. Without specific technical documentation, it is not possible to claim that a universal logic exists for choosing a route, excluding one, or resolving a case when no permitted alternatives are available.
As an operational design suggestion, it may be useful to distinguish the conditions evaluated, the possible actions, and the reason for the outcome. Route selection should not be presented as a guarantee of delivery: the available evidence does not define the relationship between a routing decision and successful message delivery.
- As a suggested practice, document the input data used by each rule and how missing or invalid data is handled.
- Describe which routes are considered and what conditions could exclude them, without presenting that description as a universal technical standard.
- Define an expected outcome for cases with no alternative, in line with the implementation and applicable obligations.
Separate Eligibility Requirements from Preferences
As a design suggestion, it is useful to distinguish requirements a route must meet from criteria used to rank options. Depending on the case, requirements might relate to the destination, traffic type, sender, or technical and contractual restrictions. The available sources do not specify which criteria should apply in each operation.
The evaluation order is a policy choice that should be checked against the implementation and applicable obligations; it is not a universal precedence supported by the sources provided. If a sequence is documented, identify it as an operational decision specific to your organization, not as a regulatory rule.
- As a suggested practice, label each criterion as a requirement or a preference.
- Document how it is determined whether a requirement can be verified.
- Consult the relevant sources and responsible parties to establish applicable obligations; the available evidence does not allow them to be listed.
Document Precedence When Rules Overlap
The evidence provided does not establish a universal precedence for resolving conflicts between A2P commercial routing rules. Nor does it show how a particular implementation orders rules. Before relying on that behavior, specific technical documentation and verification of the system in use are needed.
As an operational suggestion, an organization can describe how it expects matches, incompatible outcomes, and cases requiring review to be handled. This description should be identified as its own policy and checked against the implementation; it should not be confused with a general standard.
- Check the system documentation to see how it behaves when rules overlap.
- As a suggestion, define what to do if rules at the same level appear to conflict.
- Review overlaps and record design decisions without assuming that a general or specific rule universally takes precedence.
Analyze Denials and Cases with No Alternatives
The available evidence does not establish a general technical rule for handling denials, ineligible routes, or the absence of alternatives. As a design suggestion, a policy can distinguish between a route that was not selected and one that does not meet the conditions defined for that operation.
The specific response—for example, stopping the decision or requesting review—depends on the system, agreements, and applicable obligations. Do not assume that a platform has a specific blocking or fallback mechanism.
- As a suggestion, distinguish between “not selected” and “ineligible” in your policy documentation.
- Do not interpret the absence of a route as automatic permission to change the requirements.
- If an exception is contemplated, document its scope and responsible party as part of your own process.
Consider Keeping a Decision Log
The sources provided do not establish what records an A2P routing operation must retain. As a suggested practice, an organization may consider storing a policy and version identifier, relevant conditions, the outcome, and the reason, in line with its privacy and data-retention policies.
If rejected alternatives are recorded, the reason should correspond to information that is observable and permitted for that purpose. A selection log should not be presented as proof that an SMS was delivered.
- As a suggestion, identify the policy version associated with each decision.
- Use clear reasons in any records you choose to keep.
- Distinguish selection data from transmission data or delivery reports.
Plan Tests for Overlapping Rules and Uncertainty
The available sources do not prescribe a testing procedure for A2P routing rules. As a suggested practice, a team can define expected cases for rules that match individually, rules that overlap or conflict, and incomplete data. It is useful to identify in advance the outcomes the implementation should produce and verify that the documentation matches observed behavior.
The evidence provided also does not specify how to resolve ported numbers, changing traffic classifications, or contradictory data. More specific technical or regulatory documentation is needed to address those cases. Do not invent an automatic resolution without support from the implementation and relevant agreements.
- As a suggestion, include cases with a single match, multiple matches, and conflicting rules.
- Check how the implementation responds to incomplete or malformed data.
- Verify cases relevant to the operation and record the observed behavior.
- Obtain specific sources before asserting a rule about number portability or traffic classification.
Review Changes and Consider Rollback
The available sources do not define procedures for changing, testing, or rolling back A2P routing policies. As a suggested practice, an organization can review and document changes, verify behavior in its implementation, and decide in advance what to do if the outcome differs from expectations.
Do not assume that a simulation, gradual rollout, or automatic rollback feature exists. Route selection and transmission outcomes are distinct; selection does not guarantee delivery.
- As a suggestion, record the scope of changes and who authorized them.
- Define review and rollback procedures in line with your system’s verified capabilities.
- Do not present illustrative metrics or results as evidence of performance or a delivery guarantee.
Avoid Conclusions That Go Beyond the Evidence
The evidence provided does not support a comprehensive factual guide to priorities, denials, auditing, testing, ported numbers, or rollback of A2P routing changes. The suggestions in this article describe possible operational design decisions; they are not technical standards or universal requirements.
Before stating how a route must be selected or how uncertain data must be handled, more specific technical or regulatory documents and verification of the implementation are needed. A selected route should not be confused with confirmation that a message was received on a phone.
- Present suggested practices as your own decisions, not as established standards.
- Avoid attributing universal precedence to A2P commercial routing rules.
- Do not present illustrative prices, scores, or availability as current commercial data.
- Do not describe route selection as confirmation of delivery.
Frequently asked questions
Is there a universal precedence for A2P SMS routing rules?
The evidence provided does not support claiming that there is a universal precedence for resolving conflicts between A2P commercial routing rules. Specific technical documentation is needed to establish how a particular implementation works.
What should happen if no route meets the requirements?
The available sources do not prescribe a general response. As an operational suggestion, define an explicit outcome that fits your system and obligations; do not silently relax a condition to force a selection.
Does selecting a route guarantee that the SMS will be delivered?
It should not be presented as a guarantee. The evidence provided does not define the relationship between the routing decision and successful message delivery.
How should ported numbers or uncertain traffic classifications be handled?
The available evidence does not specify a source or universal rule for these cases. More specific technical or regulatory documentation is needed before claiming how they should be resolved.
What should a decision log include?
The sources provided do not establish record-keeping requirements. As a suggested practice, an organization may retain a policy and version identifier, relevant conditions, the outcome, and the reason, in accordance with its privacy and data-retention policies.
Sources consulted
- Especificaciones 3GPP por series3GPP
- Recomendación E.164Unión Internacional de Telecomunicaciones (UIT-T)
- Recursos de redes móvilesGSMA