MT (mobile terminated) is a message delivered to a phone; MO (mobile originated) is a message sent from a phone, for example a reply or a STOP.
The terms come from the GSM specifications and describe direction relative to the handset. A mobile-terminated message ends on a phone: everything a gateway sends on your behalf, from a code to a campaign, is MT. A mobile-originated message starts on a phone: a reply, a keyword such as JOIN, an opt-out such as STOP. Pricing, routing and reporting are different for each direction, and MO traffic needs a number that can receive.
| Aspect | MT | MO |
|---|---|---|
| Direction | Application to phone | Phone to application |
| Sender shown | A name or a number | The subscriber's own number |
| Needs | Any sender the destination allows | A number that can receive |
| Reported as | Delivery receipt | Inbound message event |
On the network side, an MO message goes from the phone to its own operator's SMSC, which routes it towards the operator or provider holding the destination number. An MT message travels the other way: from the gateway, through carriers, to the SMSC that delivers it to the handset. Delivery receipts describe MT messages; inbound webhooks describe MO messages.
When a provider quotes an "SMS price", it is the MT price. MO is usually free to receive, but it implies renting a number, because a reply needs an address that the recipient's operator can route to.
A hypothetical appointment flow uses both: an MT reminder asks "Reply C to confirm", and the patient's MO reply arrives a minute later on the clinic's rented number, where the booking system marks the slot as confirmed.
A common misconception is that a reply is a kind of delivery receipt. It is not: a receipt is a status report the network generates about an MT message, while a reply is a new message written by a person. Another is expecting MO traffic after sending under an alphanumeric name; there is no number for the reply to go to.
At SMSMeteor: the rate card lists MT prices, one per destination per segment. MO replies need a two-way number, an optional rental priced per country, and they reach your webhook endpoint as inbound events carrying the id of the message being answered, alongside message.sent, message.delivered and message.failed.
