Escalating A2P SMS Incidents Across Providers: Responsibilities and Evidence
A practical guide to coordinating A2P SMS investigations across multiple providers, documenting what has been observed, and avoiding causal claims without sufficient evidence.
Why an incident can cross multiple operational boundaries
In a wholesale chain, a message may pass through several companies or systems before reaching its destination. The evidence available for this guide does not establish what each participant can see, how records are correlated across operators, or which system originated an incident. A customer report alone is therefore not sufficient to attribute a cause.
As an operational precaution, it may be useful to distinguish data observed directly from information received from other parties. This organization can help describe what is known and what has not been confirmed, but it is not a procedure supported here by a technical standard.
- Describe which information you observed directly and which you received from another party.
- Do not assume that all participants use the same references, statuses, or time windows.
- State which aspects remain unconfirmed rather than presenting a provisional explanation as the cause.
Assign a case owner and contacts for each segment
As an internal organizational suggestion, you can designate a person or team to gather case information and coordinate communications. This does not mean they control third-party systems or can determine on their own where a problem originated.
The available evidence does not establish how responsibilities should be assigned among providers or what escalation channels, time frames, or requirements apply. If these are agreed internally or between the parties, identify them as agreements rather than presenting them as universal rules.
- If useful to your organization, assign an internal case reference.
- Identify the contacts and channels agreed by the parties.
- Do not present priorities or update times as universal requirements.
- Distinguish case coordination from each provider’s technical investigation.
Gather useful information before escalating
The available evidence does not establish which data are the minimum or sufficient to correlate a message across providers. As a practical suggestion, an inquiry can describe the information available in your own systems and ask the other party what data it needs to review its records.
State the source and context of each data point, and clarify times and time zones where relevant. When sharing information about destinations or senders, use only the data needed and channels approved by your organization.
- Internal case reference and any other available references.
- Destination and sender details relevant to the inquiry, handled appropriately.
- Date, time, time zone, and source system for each time-related data point.
- Received status, exact field or event name, and the source that reported it.
- Route or configuration, if recorded in the logs reviewed.
- Specific description of the observed impact and known scope, without extrapolating.
Distinguish observations, information received, and hypotheses
As a suggested documentation practice, you can separate records from your own system from statements received from providers and explanations that have not yet been confirmed. This distinction helps clarify the source of each claim; the available evidence does not establish it as a technical or official requirement.
Retain the context for data and communications relevant to the investigation. If you offer an interpretation, identify it as such and state what information is missing to confirm it.
- Own observation: identify the system and record reviewed.
- Information from a provider: state who communicated it and when.
- Hypothesis: describe it as provisional and state what remains to be checked.
- Do not attribute a cause solely because two events occurred at the same time.
Agree on priorities, updates, and escalation
The evidence provided does not establish response times, priorities, escalation milestones, or universal criteria for assigning them. If the parties need such guidance, they can agree on it based on their relationship and document it as an agreement between them.
Describe the observed impact and known scope. Do not promise a resolution or a time frame that the responsible parties have not confirmed.
- If priorities are defined, document the agreed criteria.
- Agree with the parties on the format and frequency of updates.
- Record any further escalation and the reason communicated.
- Use a consistent reference for related communications, if the parties can do so.
Interpret statuses and DLRs with caution
The available evidence does not include a relevant technical specification to determine what a DLR means in a particular implementation or which segment generates it. Based on the information provided, it cannot be claimed that a DLR confirms receipt or reading of the SMS on the handset.
Before describing a status, request documentation applicable to the implementation and the system that reports it. If that information is unavailable, limit the summary to stating which status was received, from whom, and in what context, and explicitly note what could not be verified.
- Retain the status text and note who reported it.
- Do not present a DLR as proof of receipt or reading on the handset without applicable supporting documentation.
- Do not assume that similar statuses have the same meaning in different systems.
- Distinguish the status received from anything verified separately.
Document a case timeline
As a case-management suggestion, you can gather relevant investigation information in a case file, noting its source and when it was received. The evidence provided does not establish audit requirements, record-keeping requirements, or retention periods for A2P incidents between providers.
If a route or configuration is changed during an investigation, describe the change and its stated purpose. Do not attribute a subsequent change in outcome to that modification without evidence that establishes the connection.
- Record communications and decisions you consider relevant to reconstructing the case.
- Note the source and time of recorded data when available.
- Describe route or configuration changes and the stated reason for them.
- Follow applicable internal policies and agreements on access and retention.
Close the case and record what remains unresolved
When closing a case file, you can summarize what was observed, which explanations were confirmed by the parties, and which questions remain unanswered. The evidence provided does not establish official closure categories or technical criteria for determining a cause.
If follow-up actions are agreed, identify who communicated them and what remains pending. Do not turn a provisional explanation into a general rule for future incidents.
- Summarize the observations and the sources that support them.
- State which aspects could not be confirmed.
- Record follow-up actions agreed by the parties.
- Distinguish the case’s conclusions from hypotheses that remain open.
Frequently asked questions
Does a DLR prove that the SMS reached the phone?
The technical evidence provided does not establish what a DLR confirms in a particular implementation. Do not claim that it proves receipt or reading on the handset without applicable supporting documentation.
What information should I include in an inquiry to a provider?
You can describe relevant references, destination and sender details, times and time zones, the status received and its source, and the observed impact. The available evidence does not establish a universal minimum data set; share only what is necessary through approved channels.
Who should coordinate an incident affecting multiple providers?
Your organization can designate a person to coordinate information and communications. The evidence provided does not establish a universal allocation of responsibilities among providers. Coordinating the case does not mean controlling third-party systems or independently determining the cause.
What should I do if providers give conflicting accounts?
As an organizational measure, record each account and its source separately, request the information each party considers necessary to review the case, and explicitly note the discrepancy if it cannot be resolved. The available evidence does not provide an official procedure for arbitrating it.
Sources consulted
- 3GPP specifications3GPP
- ITU-T E.164International Telecommunication Union
- GSMA resourcesGSMA