UK business texting that looks like you and lets people answer

Text messaging in the United Kingdom works differently from the United States. There is no US-style 10DLC mandate for the common case: UK business messaging does not need a national registration regime before you can send. What it does need is an understanding of sender identity, because the UK market is split between two distinct approaches.

The first is the alphanumeric sender ID, up to 11 characters that appear in the recipient's inbox as your name or brand rather than a phone number. The second is a numeric sender: a virtual or dedicated UK number, which recipients can reply to. Both are legitimate and both have constraints. Alphanumeric IDs are subject to reserved and restricted lists maintained by UK networks, and recipients generally cannot reply to a brand name. A number invites a conversation. Choosing between them is the first decision in any UK deployment, and it changes what the recipient sees and what your system receives. Compare this with the US approach on our US messaging overview, where registration is the dominant constraint.

A UK alphanumeric sender ID can contain up to 11 characters, using letters A-Z, digits 0-9 and spaces, for example "ACME LTD". The ID is what the recipient sees before they read a word, and a recognisable name makes a transactional message immediately believable. It is why British businesses overwhelmingly choose brand names over long numbers, and why the identifier is worth designing rather than inheriting from an account default.

The constraint is that UK mobile networks, including BT/EE, O2, Vodafone, Three and others, maintain reserved or restricted sender ID lists. If your alphanumeric ID sits on a reserved list, a network may substitute another sender or reject the message altogether, and BT/EE publish restricted lists rather than keeping them secret. Some networks support or require sender-ID registration through the aggregator before first use. Where a network requires it, we can check and register your sender ID with the networks, so a launch never stalls on a name nobody checked.

Because replies do not work to a brand name, organisations that need two-way conversations send the outbound message from a number. Our two-way SMS in the UK page covers that trade-off in detail.

When a recipient needs to answer, the sending identity changes to a number. WorldText provisions UK virtual and dedicated long numbers that look like a normal mobile number and can be used for inbound and two-way messaging. They are the mainstream route for UK conversations, and replies reach you over webhook, SMPP or email rather than dying in a portal.

For receiving-only traffic the options widen. SIM hosting lets a business receive text messages on an ordinary SIM or mobile number with forwarding over API, webhook or email; it is focused on receiving rather than bulk outbound termination. Short codes remain available for high-volume or recognisable campaigns: UK text short codes are Ofcom-allocated, commonly 5-6 digits in the 7000 series, and several ranges such as the familiar 80xxx, 84xxx, 86xxx and 87xxx family are still in use (check with us if you have a specific range in mind). An auto-responder and free SMS-to-email complete the picture for simple workflows. See inbound SMS in the UK for the full options list.

WorldText is a specialist SMS infrastructure provider rather than a campaign tool, and the UK offering is built around that. We are the layer between your application and the UK networks: message submission over HTTP or SMPP, sender-ID handling, delivery receipts, retries and inbound delivery back to you.

UK destinations are listed on our coverage page, which names the networks we deliver to. Pricing is destination-based credit bundles in GBP including VAT, with multipart messages charged per part; see the pricing page for the current bundle structure. No delivery-rate estimates that we cannot back up, no hidden per-operator fees in our copy: what you see is what the portal shows.

For developers, the route into all of this is the HTTP API with per-account credentials, documented at the developer reference, and SMPP v3.3/v3.4 is available on request for approved accounts, usually activated within 24 hours. Message states and error codes are documented on the message state reference so retries are decisions rather than guesses, and delivery receipts are configured in the portal rather than negotiated. If your traffic needs replies, the two-way SMS page explains the number side; if it needs to stay on the right side of UK rules, the compliance page does the same for consent.

Start with the two decisions that shape everything else: what identity your messages should carry, and whether recipients should be able to reply. Then create an account, tell us about your use case, and we will check your sender ID and recommend a number type before you build. The API is documented and sandbox-friendly, so development can proceed while any sender-ID checks are resolved. Send a real test message through the portal, verify delivery with a receipt, and only then scale the traffic. The UK market rewards preparation: identity checked, consent handled, and an interface your systems already speak.

A sensible first week looks like this: decide the sender identity, ask us to check it, send a real test message to a UK number, and inspect the receipt rather than the portal's optimism. Then build against the documented API, where the developer reference covers submission, receipts and encoding in one place. Registration takes minutes and no sales conversation is required; the pricing page is public, so the only unknown in the whole setup is the use case you bring us.