Text UK customers from a sender they recognise

Business SMS in the UK is dominated by service messages, and the category is broad. One-time codes for login and payment verification, order and delivery notifications from retailers, appointment reminders from clinics and tradespeople, booking confirmations from hospitality, outage alerts from utilities, staff rotas and dispatch messages from logistics firms. What these have in common is that the recipient wanted them: the message exists because a specific event happened.

None of this is bulk marketing in the old sense. It is operational communication, and the standard for it is reliability rather than creativity. British customers engage with these messages precisely because they are short, expected and from a sender they recognise. That recognition is earned by design: a consistent alphanumeric sender ID, a consistent format and a clear call to action when one applies.

WorldText positions itself as the infrastructure behind these flows rather than a template system. The UK SMS API covers the integration side, including delivery receipts, and the transactional SMS page covers the service-message category in detail.

UK recipients are used to business text messages arriving from a name. An alphanumeric sender ID can be up to 11 characters long, using letters, digits and spaces: "ACME LTD", "DENMARK ST" or "MYCLINIC" are all legal shapes. The ID appears in the inbox and sets the context for the message, and a stable ID is worth more than a creative one, because recipients learn to trust what they recognise.

The caveat is the reserved list problem. UK mobile networks, including BT/EE, O2, Vodafone, Three and others, maintain reserved or restricted sender IDs. If yours collides, a network may substitute or reject the message. BT/EE publish restricted lists; other operators are less transparent. Some networks want registration through the aggregator before an ID is used. Where a network requires it, we can check and register your sender ID, so the ID that reaches customers is the ID you designed. This is the UK equivalent of the registration discipline US senders face, but it is list-based rather than a national mandate: see UK SMS compliance for the rules, or our US overview for the comparison.

UK law deliberately splits electronic messages into two categories, and the split is not cosmetic. Marketing text messages fall under PECR, the Privacy and Electronic Communications Regulations: you need consent, or the soft opt-in exception for your own customers receiving similar products or services where a clear opt-out was given at collection. UK GDPR separately requires a lawful basis for processing and a working opt-out.

Transactional or service messages are a different animal. They are not marketing, so they do not need marketing consent, although privacy law still applies to the data inside them. That is why the same organisation can send an OTP without asking, and cannot send a promotional offer without consent or a soft opt-in. Build the distinction into your systems rather than your copy: tag the message type, keep the opt-out channel operational, and never attach promotions to transactional sends without checking consent first. The transactional-vs-marketing comparison walks through the boundary, and our compliance page covers the UK legal context.

Some UK business messaging should end with the customer able to answer: confirming a delivery slot, asking a support question, replying YES to an appointment. An alphanumeric sender cannot receive replies, so those workflows need a reply-capable UK number. WorldText provisions virtual and dedicated UK numbers that look like ordinary mobile numbers to the recipient and deliver replies back over webhook, SMPP or email.

That combination is the practical UK pattern: brand-name sending for recognition and one-way traffic, a number where conversation matters, and an auto-responder for the replies that can be answered without a human. See two-way SMS in the UK and inbound SMS in the UK for the number-side options.

The auto-responder closes the loop on simple cases without code: a reply of CONFIRM or RESCHEDULE is answered by a template, and anything else is escalated to a person. That is the honest use of automation in UK business messaging. It handles the common path and hands the rest over, rather than pretending a menu of four options covers every customer problem, and it keeps the support inbox to the messages that genuinely need a human.

Rates for UK destinations are transparent: 10.71 credits per single-part message, multipart messages charged per part, and credits purchased in GBP including VAT. That means a UK business can cost a year of appointment reminders before sending the first one. Our pricing page shows the bundle structure, and the coverage page shows the networks we reach. What you see in the portal is what you are charged; there are no per-operator fees hidden behind a marketing sentence.

The coverage page lists the UK networks we deliver to, including EE, O2, Three, Vodafone, Sky, MVNOs and fixed-line style numbers such as the 994 range, so the destination check is public rather than something you discover at invoice time. Before you size a year of traffic, review the SMS length guide: a message that looks like one part can become several, and multipart messages are charged per part, so the guide is where budgeting actually happens. Keep promotional content out of transactional messages and the compliance line stays simple, which is a cost saving as well as a legal one.