Two-way SMS lets recipients reply to your messages; it requires a numeric sender (a dedicated or shared number) because alphanumeric sender names cannot receive replies.
Most application traffic is one-way: the message goes out from a name or a shared number and there is nothing to reply to. Two-way messaging uses a real number as the sender so that replies come back, are matched to the conversation, and are forwarded to you by webhook or shown in an inbox. A reply is a mobile-originated message: the recipient's phone sends it to the number, the operator routes it to whoever holds that number, and the gateway turns it into an event your system can read.
Two-way messaging is the basis of confirmations (reply C to confirm), keyword campaigns, support over text and, in the simplest case, STOP handling. The number is rented per country, because replies must terminate on a number the local operators can reach.
Matching a reply to its context needs design. At the SMS level, a reply carries the two numbers, the text and a timestamp, but no reference to an earlier message, so the gateway links it to the conversation from the pair of numbers. If a clinic sends two reminders to the same patient from the same number, a bare "C" is ambiguous; asking for "C1" or "C2", or keeping one open question per recipient, avoids the guesswork.
A hypothetical example: a garage texts "ACME Motors: your car is ready. Reply 1 to collect today, 2 for tomorrow." The booking system parses the digit in each reply, and anything else goes to a person.
Common mistakes: asking for a reply under an alphanumeric sender, which cannot receive one; parsing replies too strictly, when people write "yes", "Yes please" or "ok thx"; and ignoring STOP or its local equivalents when the flow expected something else.
At SMSMeteor: alphanumeric senders are one-way. Turning on replies for a campaign attaches a two-way number for each destination in the list, an optional monthly rental priced per country. Replies land in the panel inbox, grouped by campaign, and reach your webhook as inbound events carrying the id of the message being answered. Keyword rules match replies such as C, X or HELP and send the answer you wrote, billed as a message, and a STOP reply removes the number from the list and from later campaigns to that list. See two-way SMS.
