A2P (application-to-person) SMS is any text message sent by software to a person: verification codes, alerts, receipts, reminders and marketing campaigns, as opposed to messages typed by one person to another.
A2P stands for application-to-person. The application might be a login service issuing a one-time passcode, a shop sending a delivery notification, a clinic's booking system sending reminders, a bank's fraud engine raising an alert or a marketing tool running a promotional campaign. What makes the traffic A2P is that a system, not a person typing on a phone, decides to send.
Carriers treat it differently from person-to-person traffic on three counts. It is priced per message on wholesale routes, often on terms the destination operator sets for application traffic. It may require a registered sender in some countries before a name is shown. And it is filtered for spam more aggressively, because automation makes abuse cheap.
In practice, an application hands its messages to an SMS gateway through an API or a web panel. The gateway applies the destination's sender rule, prices each message and passes it to carriers over connections they accept for A2P traffic. Statuses and delivery receipts travel back the same way.
The distinction matters because carriers detect A2P traffic sent through person-to-person channels, SIM farms being the classic case, and block it. Suppose a hypothetical booking app sends its reminders from a handful of consumer SIM cards to save money. Identical texts, steady volume and no replies give it away; the cards are cut off, and the brand name in the text can end up on a filter list. Legitimate A2P traffic goes through a gateway connected to carriers on A2P terms.
A frequent misconception is that only marketing counts as A2P. A password reset is as much application traffic as a promotion: transactional and promotional messages differ in content and consent, not in channel. Another is that A2P is always one-way; with a number that can receive, replies come back to the application.
At SMSMeteor: everything sent from the panel or the API is A2P traffic, carried on one route per destination, chosen for measured delivery rate and reviewed daily. The route checker on the coverage page shows the rate and the sender rule for any destination.
