Everything worth knowing, nothing that isn't.
P2A vs A2P — direction is everything
A2P is software sending to a handset (mobile-terminated, MT); P2A is a handset sending to software (mobile-originated, MO). P2A is billed to the consumer on their tariff, arrives at your gateway as an SMPP deliver_sm with the MO flag set, and is the technical foundation of two-way conversational SMS. See /answers/what-is-mo-vs-mt for the MO/MT distinction and /products/two-way-sms for the product.
Where P2A shows up
Opt-out and opt-in keywords (STOP, START, HELP) that regulators require on marketing SMS; competition and voting entries; two-way customer support; and consent capture where a subscriber texts a keyword to a short code to join a programme. P2A always needs an inbound-capable number: a long number (always two-way), or a short code provisioned for MO.
How BroadNet handles P2A
Inbound MO messages are delivered to your webhook in real time, matched to the originating conversation, and available over the same SMPP bind or REST webhook you use for A2P. Because the reply path is MO, it is priced and routed as a legitimate operator service — not a grey route. See /products/two-way-sms.