A2P SMS
Application-to-person SMS is traffic an application sends to a handset, such as a verification code or a transaction alert, via a registered sender.
Definitions only — a term explained here is not a service we sell.
Application-to-person (A2P) SMS is a message sent from an application to a person's handset. The origin and registration make it A2P, not the content: a code, a transaction alert and a consented marketing message all qualify.
A2P traffic leaves through a registered sender identity on a commercial route. Regulators in several markets require the sender and template to be registered first. Segment counts decide cost: three segments are billed as three.
What the route decides
The application submits to a gateway over SMPP v3.4 or an HTTP API, and the gateway passes the message to an SMSC. A registered sender ID and a delivery receipt separate this route from person-to-person messaging. What is A2P SMS explains the route.
Where an A2P message goes
- Application
- SMPP gateway
- SMSC
- HLR / HSS
- MSC / MME
- Handset
- Delivery receipt
Text description
The application submits to a gateway, which passes the message to the SMSC. The SMSC looks up the subscriber and routes to the handset. The receipt returns the same way.