Back to blog Wholesale SMS

A2P SMS Intermediary Chain: How to Document Dependencies and Verification Limits

A practical guide to recording who is involved in A2P SMS transport, what information supports each segment, and which conclusions remain unverified.

Diagram of an A2P SMS intermediary chain showing segments, information sources, and verification levels

What an A2P SMS intermediary chain means

An A2P SMS transmission may involve several entities between the sending company and the mobile network serving the destination. For procurement and operations teams, knowing who is involved can help describe dependencies, clarify responsibilities, and prepare questions for when issues arise.

A map of a particular chain should be treated as a record of available information, not as automatic proof of the complete physical or logical route. The evidence provided for this topic does not establish a universal standard for documenting individual segments. It is therefore useful to state what is known, who provided the information, and what remains unresolved.

  • Use the map to organize information and questions, not to promise delivery or assign responsibility without evidence.
  • Separate observed data from commercial statements and internal assumptions.
What an A2P SMS intermediary chain means

Do not confuse a declared route, a technical connection, and a destination

A declared route describes what a party says about how traffic is transported. By itself, that description does not confirm every participating entity or its role.

A technical connection—for example, an integration using HTTP or SMPP—identifies a way systems exchange information, but does not necessarily reveal the full downstream chain. Similarly, identifying a destination operator is not enough to establish which intermediaries were involved before the message reached that network.

Keep these categories separate in your records. If a source does not clarify the scope of a label or connection, note it as an open question rather than filling in the map by inference.

  • Declared route: what a counterparty says about the path or configuration.
  • Technical connection: the known integration point between systems.
  • Destination operator: the mobile network to which the message is directed, if identified.
  • Intermediaries: entities whose participation should be recorded only to the extent supported by the source.
Do not confuse a declared route, a technical connection, and a destination

Build a segment-by-segment record

Divide the map into consecutive segments based on the information you actually have. For each one, record the entity or description available, its stated role, the destination or scope it applies to, any known dependency, and the associated evidence.

If part of the chain is unidentified, explicitly mark it as unknown or unconfirmed. Do not fill the gap with the name of a presumed provider or extrapolate an answer that applies to one destination to other destinations.

A table can make review easier, although the evidence provided does not specify a required documentation framework. Apply the same format to every segment so differences and gaps are visible.

  • Segment: origin and next known point, without assuming the map is complete.
  • Entity and role: the name or description provided, and the role as defined by the source.
  • Destination and scope: the countries, networks, traffic types, or conditions specified by the source.
  • Dependency: a documented relationship or condition; if unknown, say so.
  • Evidence and status: source reference, date, record owner, and assigned level of certainty.

Organize evidence without overstating what it proves

Classify each data point by its source and scope. You can record contractual documents, written confirmations from a counterparty, your own technical logs, and operational observations, while specifying which particular statement each item supports.

The available information does not provide a basis for assigning these categories a universal evidentiary weight. A contract may describe a relationship or obligation, but it should not automatically be presented as proof that a specific configuration was used for a particular transmission. A technical log may show what a system observed without, by itself, proving what happened across every downstream segment.

Use clear internal labels, such as observed fact, counterparty statement, document reviewed, or pending confirmation. Explain what each label means so different people do not interpret the same status differently.

  • Link each statement to a source and date.
  • Record what the source supports and what it does not cover.
  • Distinguish a provider confirmation from an independent observation.
  • If sources conflict, preserve both versions and flag the discrepancy; do not resolve it without supporting evidence.

Add a date, record owner, and level of certainty

The map should show when the information was collected, who recorded it, and where it came from. Also include the period or conditions it applies to, if specified by the source. Without a date and scope, a statement can lose its context when the configuration changes.

Define operational levels of certainty for your organization rather than treating them as a universal scale. For example, you might distinguish documented information, confirmation received, limited observation, and pending information. Briefly explain each level and avoid turning it into a quality score or guarantee.

Record facts, statements, and open questions separately. This helps prevent a commercial claim from inadvertently becoming a verified fact when copied into a procurement or incident report.

  • Collection date and, if known, the effective date specified by the source.
  • Record owner and original source.
  • Destinations, traffic, or conditions covered.
  • Level of certainty and the reason for the classification.
  • Open questions and the next action to resolve them.

Specific questions to clarify dependencies and changes

Useful questions define scope and responsibility without assuming that a declared chain is complete. Request written answers and ask which destinations and traffic types each answer covers.

The available evidence does not establish a shared obligation to notify customers of intermediary changes or a standard process for doing so. Buyers can therefore raise these conditions in their agreements and ask for them to be expressly clarified, without presenting them as a general industry rule.

  • Which entities can you identify in each segment, and what role do you assign to each?
  • Which destinations and traffic types does this information cover, and what exceptions or segments remain unconfirmed?
  • Which dependencies are known to you, and which are outside your visibility?
  • How do you communicate changes to subcontracting, intermediaries, or configuration, if such a process has been agreed?
  • What notice, timeframe, and scope details can you include in a change notification?
  • What records can you provide during a review or incident investigation, and what limitations apply?

Verification limits: labels, DLRs, and isolated tests

The available information does not support the conclusion that a route label, by itself, proves which intermediaries participated. It may be useful as configuration data or as a statement, but its meaning and scope should be confirmed with the source that generated it.

A DLR is a status reported by a system. It should not automatically be confused with independent verification that the message appeared on the recipient’s device. To interpret a DLR, document who issued it, what status it represents, and which part of the process it reflects. Do not extend its scope to segments the record does not observe.

An isolated test provides only a limited observation under its specific conditions. Without additional evidence, it does not allow you to conclude that the same chain was used for other messages, destinations, or times, or that the intermediary map is complete.

  • Do not interpret a label without knowing its definition, source, and scope.
  • Distinguish a received DLR from independent confirmation that the message reached the device.
  • Record the conditions of each test and limit conclusions to what was observed.
  • Mark segments without sufficient evidence as unverified.

Use the map to inform decisions, not as a guarantee

A segment-by-segment record can support commercial due diligence, incident preparation, and dependency reviews. To make it useful, link each decision to the information available at the time and make visible any limits that could affect its interpretation.

During an incident, compare the event’s scope with the documented destinations and segments, gather the available records, and note which hypotheses remain unconfirmed. For continuity planning, identify confirmed and unknown dependencies; do not treat an alternative route as available unless it has been substantiated for the scope you need.

Update the map when you receive new information or documented conditions change. Periodic review may be part of your internal process, but the interval should suit your risk and agreements: the evidence provided does not establish a universal frequency.

Incomplete transparency cannot be addressed by using a more precise label. Manage it by recording uncertainties, requesting proportionate clarification, and avoiding the presentation of a partial description as full verification of the chain.

  • Before contracting: define which chain is being described and what evidence can be obtained.
  • During an incident: relate observations and records to their scope without inferring unobserved segments.
  • For continuity: note dependencies and gaps; verify any alternative separately.
  • During reviews: update the source, date, scope, and open questions.
FAQ

Frequently asked questions

Does a declared route confirm the entire intermediary chain?

Not by itself. The available information does not support concluding that a statement or label identifies every segment. Record who provided it, what scope it describes, and which parts remain unconfirmed.

Does a DLR prove that the recipient received the SMS on their phone?

Do not assume so. A DLR is a status reported by a system and may not be equivalent to independent verification of receipt on the device. Document its issuer and the scope it represents.

What should I do if a provider does not identify an intermediary?

Mark that segment as unknown or unconfirmed, record the response and its date, and ask what scope the provider can confirm. Do not fill in the missing information by assumption.

Is there a standard format for documenting each segment?

The evidence provided does not support the claim that a universal standard exists. You can establish a consistent internal format covering entity, role, scope, dependency, source, date, record owner, certainty, and open questions.

How often should the map be reviewed?

The available information does not support a universal review frequency. Set an interval according to your risk and agreements, and update the record when you receive new information or documented conditions change.

Sources consulted

  1. 3GPP specifications3GPP
  2. ITU-T E.164International Telecommunication Union
  3. GSMA resourcesGSMA
  4. El mercado de mensajería A2P: problemáticas, retos y oportunidadesTelefónica / Analysys Mason