Turn inbound text messages into data your systems can use

Inbound SMS is any text message a recipient sends to a number you control. It is not a mirror image of outbound messaging: sending has one direction of trust, while receiving requires you to consider who owns the number, how the message is routed and what your systems do with it once it arrives.

For businesses, inbound SMS is usually one of two things. It is a reply to a message you sent: a customer confirming an appointment, answering a question in a support conversation or responding to a verification prompt. Or it is traffic that arrives unsolicited: a customer texting a number they found in an advert, a device acknowledging a command, or a monitoring system reporting back.

Inbound messaging stops being useful when the messages remain in a shared inbox. The value comes from messages arriving in your application, matched to the right conversation and carrying enough context to act. That is where infrastructure choices matter. The number type you receive on, and the interface through which messages are delivered to you, determine what is possible. This page covers both, and the honest limits of each.

WorldText offers several ways to receive SMS, and they are not interchangeable.

Virtual and dedicated numbers route inbound SMS directly to your endpoint, which makes them the right choice for two-way messaging and replies. Recipients see a real number, can text it back, and you receive the reply without involving a handset. Virtual numbers and dedicated numbers are covered in detail on the service pages.

Short codes are shorter, memorable numbers used for high-visibility campaigns and mass response situations. They are also a two-way path, but they are provisioned differently from long numbers, so they suit dedicated campaigns rather than everyday application traffic.

SIM hosting is the option most people misunderstand. You place ordinary mobile SIMs in our infrastructure, and inbound SMS to those numbers is forwarded to you over the API, webhook or email. It lets you receive messages on numbers you already have without buying new ones. The honest framing: WorldText SIM hosting is focused on receiving SMS. It is not a bulk outbound SIM-bank termination service, so do not expect it to carry large volumes of outgoing traffic from hundreds of SIMs.

Number ownership and registration requirements vary by market. Where a market requires registration for a number type, or where rules about who owns a number apply, we work through what applies with you.

Inbound messages can be delivered to you in three ways, and you choose per number.

An HTTP webhook is the most common integration. When a message arrives on your number, WorldText sends it to an endpoint you control, so your application can act immediately. Two-way SMS is built around this pattern and covers the full conversation lifecycle, including replies generated by the recipient. The developer reference documents the inbound request format.

SMPP delivery is available for systems that already speak SMPP. Rather than translating inbound traffic to HTTP, the platform can hand it to an SMPP receiver, which suits messaging gateways and carrier-grade integrations where the entire stack sits on SMPP.

Email delivery is the low-effort option. SMS-to-email is free and forwards each inbound message to an address you choose, which suits low-volume numbers that need a human reading rather than an API consumer. For numbers that should answer automatically when nobody is watching, an auto-responder can send a programmed reply without any code on your side.

The practical value of inbound SMS is in the workflows it closes, not in the texts themselves. The pattern is always the same: a message arrives at a number you control, and it has to become a record or a trigger inside your systems rather than a notification to a human with no context.

The common uses follow a small number of shapes. Two-way support conversations let a customer text a number and continue the conversation with an agent, with the transcript held in your systems. Appointment confirmations with replies let a patient or client answer directly and have that answer route to the booking system. Delivery updates from couriers and field teams turn a brief text into an auditable status. Verification and OTP flows close the loop by confirming that a code was received and acted on. Monitoring acknowledgements let devices and systems confirm alerts rather than silently failing. SMS-to-email is the fallback for anything that does not need automation.

Whatever the use case, the same integration decisions apply: which number type, which delivery interface, and what your system does with each message state.