Business SMS with VoIP UK: Can Your Number Send Texts?

Can a UK business VoIP number send and receive SMS?

Sometimes—but a VoIP phone number is not automatically SMS-enabled. Whether a business can text customers from the same number it uses for calls depends on the exact UK number, the number holder and carrier, SMS routing arrangements, the messaging provider and the purchased service. Some 01/02 geographic numbers can be given a separate SMS route; some eligible 07 mobile numbers support two-way texting; an alphanumeric business sender name generally does not accept replies.

The first buying question is not “Does your phone system have an SMS button?” It is “Can this actual business number send and receive texts, and which supplier takes responsibility for both directions?” Get that answer in writing and test real messages before switching supplier or promising customers a text channel.

UK 01, 02, 03 and 07 numbers: SMS eligibility explained

Ofcom categorises 01/02 as geographic numbers, 03 as non-geographic and 07 as a range that includes mobile numbers and other services. These classifications establish what kind of number you hold; they do not prove that its current voice supplier enables text messaging. Ofcom explains UK number types.

For a customer-facing number, identify the existing voice provider, the number allocation/holder and the proposed messaging service. A reseller’s “SMS supported” feature label is not a substitute for approval of that particular number.

Why voice call routing and SMS routing are separate

VoIP voice calls usually travel over the business phone provider’s SIP or platform connection. SMS may instead travel through a mobile network, aggregator, number-level relay, SMS gateway or provider API. Adding a CRM inbox does not automatically activate the underlying number for mobile-network messaging.

Voice path: Customer calls the business’s main number → the contracted voice carrier/PBX → the department or user. SMS path: Customer texts that identity → mobile-network or SMS relay route → nominated messaging gateway → authorised users or automation. The two paths can have different suppliers, incidents and service agreements.

UK operator aql documents geographic-number SMS relay operating independently of voice routing. This demonstrates a technical possibility for appropriately enabled fixed-line numbers, not a promise that any UK landline or SIP service can use it.

Three practical ways to offer business texting

The suitable option depends on whether keeping your voice number visible in texts matters more than creating a new dedicated messaging channel.

Do not confuse choosing a number with proving its messaging capability. For 01/02/03/07 telephone identities, use our UK business phone numbers guide; this article remains focused on the message route and acceptance tests.

The exact-number SMS eligibility decision

Use this sequence with the number you already own or intend to order. Request answers from the supplier that controls the number and from the supplier delivering the SMS inbox.

Two-way messaging, replies and delivery evidence

Two-way SMS is a complete workflow, not merely a provider feature badge. A business needs its chosen sender identity displayed correctly, outbound delivery status, incoming messages associated with the correct number, and reliable staff ownership.

Ask what “delivered” means in the service contract: submitted to the gateway, accepted by a carrier or confirmed by a network receipt. No provider can promise that every handset will read every text.

If the workflow has legally significant communications, involve your organisation’s compliance lead before treating SMS delivery logs as conclusive evidence of recipient attention or consent.

Shared inbox and CRM integration checks

A shared SMS inbox is useful only if its permissions and record-matching rules match how the business serves customers. Evaluate the full conversation journey: who can see it, who replies, who may export it, and who investigates incorrect contact matches.

Our existing VoIP and CRM integration overview covers broad call-event and customer-record workflows. SMS-specific routing, sender eligibility and opt-out operations belong to this guide.

For API integrations, make sure inbound webhooks are authenticated, replay/retry behaviour is understood, personal data is minimised, and a failed downstream CRM request does not silently discard the customer’s message.

Can 3CX or Yeastar P-Series handle business SMS?

Some business PBX platforms provide messaging features or APIs. That does not prove SMS is available on an arbitrary UK business number. Compatibility depends on the exact platform version, feature entitlement, approved service provider, message API and number provisioning.

For example, 3CX’s SIP trunk requirements describe provider-dependent integrations; messaging support must be checked against the selected 3CX edition and compatible provider. Yeastar’s P-Series Cloud Edition SMS API documentation describes a service-provider SMS integration with firmware and API requirements. Neither source guarantees that your current UK geographic number will accept replies.

Buyer request: Obtain the provider’s current compatibility documentation, the number supplier’s written SMS routing approval, and a recorded end-to-end test on your intended setup. If these cannot be demonstrated, treat SMS support as unverified regardless of the PBX marketing page.

Keeping your number when changing provider

Porting an existing business number for voice does not necessarily transfer its SMS routing in the same operation. The two services may be administered by different carriers, and supported routes can change when the number holder or underlying operator changes.

1. Confirm who currently controls the phone number and who delivers SMS, if already enabled.
2. Identify whether the incoming provider offers the same SMS capability on the number after transfer.
3. Request dates for porting, any message-routing cutover and dual-running or fallback.
4. Document which supplier updates the SMS gateway when the voice port completes.
5. Test inbound, outbound and voice service again after migration; record any gaps.

Our UK number-porting guide explains the broader number-transfer process. For messaging continuity, require a separate documented SMS-routing acceptance.

Business SMS pricing: compare complete units, not just a text rate

SMS quotations are difficult to compare if they use different message-unit definitions or include only the outgoing segment fee. A single long or Unicode-rich message can consume more than one billed segment, depending on encoding and provider policy; rates and recipient coverage can also differ.

Do not substitute a generic public SMS platform rate for a written supplier quote that covers your number and UK mobile destinations. Obtain the itemised price basis and model your actual mix of service notifications, replies and peaks. A low outbound rate alone may hide higher inbox, setup or support charges.

UK PECR and GDPR: service texts versus marketing texts

A genuine service message is not automatically direct marketing. The ICO distinguishes communications sent solely for customer service or administration from marketing: adding promotional material can change its classification. The legal assessment depends on message content and context, not a label chosen by the sender. See the ICO’s key concepts.

For direct marketing by SMS, the Privacy and Electronic Communications Regulations (PECR) distinguish individual subscribers (which may include sole traders and some partnerships) from corporate subscribers. Marketing to individual subscribers generally requires appropriate consent unless a qualifying soft opt-in applies; corporate-subscriber rules differ, and UK GDPR obligations may still apply. Do not interpret an employee’s business contact number as automatically exempt from data protection requirements. The ICO’s electronic mail marketing guidance was updated 28 April 2026.

For marketing, provide a clear and functioning way to object or unsubscribe and maintain an accurate suppression list. An alphanumeric sender ID may not accept replies, so the opt-out route must work by another suitable means. Document a UK GDPR lawful basis, transparency, retention controls and processor responsibilities for personal data.

Sender identity, fraud prevention and customer trust

SMS is subject to spoofing and impersonation risks. Choose a provider that verifies sender identities, applies suitable anti-abuse controls, documents message-content restrictions and provides evidence when messages are filtered or rejected.

• Verify sender registration: Ask how the platform proves your authority to use a business name or telephone number as the displayed sender.
• Use recognisable content: Avoid unnecessary shortened links and unexpected requests for security codes or payment details.
• Protect API access: Restrict and rotate keys, protect webhook secrets, use least privilege and review logs without exposing message content widely.
• Control opt-outs: Prevent another team from re-importing suppressed numbers into a new campaign.
• Design for incidents: Have a route for failed delivery, compromised credentials, incorrect recipients, supplier outage and escalation.

Review GOV.UK’s secure SMS guidance for aggregator capabilities, delivery receipts and information protection, and consult Ofcom’s mobile messaging scam protections.

Two UK business use cases: what works and what does not

These are illustrative workflows, not customer case studies, live product tests or claims that any named provider currently supports every step.

12-point SMS acceptance checklist for your exact number

Ask prospective suppliers to run these tests in a controlled pilot before approving the new SMS channel. Record actual evidence (date, network, sending and receiving number, result, screenshot or provider log), the responsible party and the resolution for any failed step.

1. Exact number approved. Supplier confirms SMS provisioning for the actual complete UK number and account; note carrier and number holder.
2. Inbound on two UK networks. Text the number from two different eligible UK mobile networks; collect timestamped receipts in the chosen inbox.
3. Outbound on two UK networks. Send from the approved sender and capture what appears on both handsets.
4. Two-way reply continuity. Reply to the outbound text and prove the message returns to the correct existing conversation.
5. Correct displayed sender. Record handset screenshots and confirm alphanumeric/number display matches contractual approval.
6. Failure visibility. Demonstrate rejected/undeliverable status and the escalation process; distinguish acceptance from actual receipt.
7. Voice unaffected. Prove that calling and SMS routing both work on the identity where both are promised.
8. Segments and international characters. Send a deliberately long and Unicode/emoji test; reconcile billing segments and provider policy.
9. Shared inbox governance. Verify team permissions, unread assignment, audit trail, staff offboarding and export.
10. CRM matching and privacy. Use test contacts to prove accurate +44 matching, duplicate handling, minimal data and valid event workflow.
11. Marketing opt-out. Test STOP/unsubscribe through the actual sender setup, suppression and non-marketing service-message boundaries.
12. Porting and supplier exit. Obtain written transfer procedure, routing dependencies, account-data export and post-cutover retest requirements.

Questions to put in writing before choosing an SMS service

Send the same requirement brief to your phone supplier, SMS aggregator and any CRM integrator. Where two providers share a task, insist they state which one owns the incident and response time.

Request the exact current product and tariff sheet, not a generic “business texting” feature list. If the provider cannot name the number-level route or cannot demonstrate inbound replies, record that feature as unverified and avoid promising it publicly.

Business SMS with VoIP UK: frequently asked questions

These answers are deliberately conditional: capability and legal duties depend on the actual number, provider and message purpose.

Sources, methodology and what remains unverified

This guide draws on UK regulatory and vendor documentation reviewed on 23 October 2026. Vendor guides describe features or possibilities, not independently verified support for an arbitrary business account or number. No supplier SMS pilot, real-number compatibility testing, independent cost benchmarking or legal compliance assessment has been performed for this article.

1. Ofcom — UK phone numbers and call costs
2. aql — Geographic-number SMS relay technical explanation
3. ICO — 2026 direct marketing using electronic mail
4. ICO — Service messages and direct marketing concepts
5. GOV.UK — Sending text messages securely
6. Ofcom — Protections against mobile messaging scams
7. 3CX — Supported SIP trunk requirements
8. Yeastar — SMS API integration for P-Series Cloud Edition

Editorial boundaries: SMS availability, number class, carrier routing and marketing permissions must be checked with current primary sources and the actual contracted provider. The business phone numbers guide owns the UK number-selection task; the number-porting guide owns the wider migration process. This page owns SMS-specific eligibility and acceptance.