Hosted Messaging Explained: SMS on the Numbers Your Customers Already Know

A published business number is an asset: it sits on the website footers, the brochures, the delivery receipts, and the business cards customers hold onto. When a company decides its customers should be able to text instead of call, that number has to keep its identity — and a full carrier port is often unavailable, unpopular, or contractually blocked. Hosted messaging (also called "Hosted SMS" or "text-enable") is the carrier mechanism that adds SMS routing to a number whose voice service stays where it is. Comparison pages mention the feature in passing; the pattern itself rarely gets a definition. This one does — what the overlay does, when it beats a port, what a buyer should check, and how the lifecycle runs on Devotel Orbit.

What hosted messaging actually is

SMS routing and voice routing travel on separate paths in the carrier network, and a hosted-messaging order authorizes a hosting carrier to overlay the SMS path only. The number's carrier-of-record does not change — the hosting carrier adds an SMS delivery route, and messages received on the number follow that route to your messaging platform while voice calls keep ringing the existing PBX, carrier, or answering service exactly as they did before.

That separation is what makes the feature useful for the classes of number it exists for: a landline bound to a PBX contract, a toll-free number bundled into a voice plan, or a voice line whose carrier the business is contractually locked to. The customer sends a text to the number they already know, and the text arrives in your platform's inbox or webhook endpoint. The voice path is untouched from end to end.

Host, port, or buy — the three acquisition paths

Putting a number on a CPaaS platform is one of three paths, and hosting is only the right answer for one of them.

Buy a new number. Drawn from the platform's inventory. No paperwork, active in minutes, and the path for new campaigns and tracking numbers.

Port the number in. Moves voice and SMS together, and changes the carrier-of-record. The right answer when the whole number should live on the platform — and a port supersedes any hosted order on the same number.

Host the number for SMS. Moves SMS routing only; carrier-of-record is unchanged. The right answer when voice must stay with the current carrier, when the number is a landline or toll-free used mainly for messaging, or when a port is blocked but an SMS overlay is still allowed.

The increasingly common mistake is running both a port and a hosted order in flight on the same number — cancel the hosted order before a port completes, so the carrier never serves two overlapping requests.

The buyer checklist

Four checks separate a checkbox feature from a shipped capability.

Inbound-only, or also outbound? Some platforms scope hosted messaging to inbound delivery; others extend it to outbound sending. A buyer should know exactly which path their outbound traffic takes either way. On Devotel Orbit the agreement is inbound-only by design: the hosted order configures where received texts land, and outbound messaging continues on its standard path, unaffected.

Does voice stay untouched? The hosting mechanism should never reroute calls. Verify the platform treats the overlay as SMS-only — a provider that "text-enables" by porting the number has moved voice, not hosted it.

What does the LOA demand? The Letter of Authorization is the carrier's authorization record. Look for an in-platform signing flow that captures the signer's name, email, and acknowledgement, and a deliberate step between signing and submission — that break exists so a mistaken order can be revoked before the carrier ever sees it.

Who keeps the status honest? The lifecycle (draft → LOA signed → submitted → active, with rejection and cancellation paths) should be visible per order, with a human-readable rejection reason when the carrier refuses. A black-box submit-and-wait flow hides the one retry cause (an account-holder name mismatch) that is fixable in minutes.

How Devotel Orbit wires it

Hosted messaging ships on the Numbers pillar, reachable from Numbers → Hosted Messaging in the dashboard or driven over the Numbers API — the same order lifecycle either way:

1. Create the order with the number in E.164 format, the voice carrier, the number class (landline, tollfree, or mobile), the business name on the carrier billing record, and the initial inbound route (a webhook HTTPS URL, an inbox, or a messaging service).
2. Sign the LOA in-platform — signer name, email, and acknowledgement form the organization's authorization record.
3. Submit to the carrier. The signed order moves submitted, and the carrier verifies ownership against the billing record. A second in-flight order for the same number returns a 409 until the first resolves.
4. Track to active. The route stays editable until activation; the most common rejection cause is a businessName that doesn't match the carrier's billing record, and the rejectionReason field names it.

Once active, inbound SMS on the number arrives with the same event shape as any other inbound message — webhook receivers and inbox views pick it up with no special handling — and inbound billing matches inbound SMS on any other number in the workspace; the hosting arrangement adds no per-message surcharge. Reverting is explicit too: cancel before activation and the carrier never hosts; after activation, canceling a port reverses the overlay cleanly.

Frequently asked questions

Does hosted messaging change how we send outbound texts?

No. The order configures the delivery target for messages received on the number. Outbound messaging stays on whatever standard path the workspace uses — on Orbit, exit via the Devotel network with the voice service untouched.

Does voice service change?

No. Voice keeps ringing the existing PBX or carrier exactly as it did before the order, which is the entire point of the overlay — SMS routing is added without touching the call path.

Can a hosted number be ported later?

Yes. Hosting never blocks a later full port. Cancel the hosted order before the port completes so the carrier never serves overlapping requests; once the port is active, voice and SMS move together and the hosting arrangement is retired.

Which numbers qualify?

Landline, toll-free, and mobile numbers in E.164 format. Short codes and VoIP-assigned numbers aren't eligible, and some rate centers block hosting entirely — eligibility checks run before the order opens.

What if the carrier rejects the order?

The order lands in rejected with a rejectionReason — usually a business-name mismatch against the carrier billing record, or a signer not authorized on the account. Fix the LOA content and open a fresh order; a cancelled or rejected order stays retrievable, not chargeable.

Where to go next

The full walkthrough — API equivalents, route types, and the troubleshooting matrix — lives in the hosted-messaging guide. The Numbers API reference carries the request/response schemas for hosted messaging and porting, and the concept page defines the carrier-overlay mechanics behind both. For the messaging surface the hosted number feeds, see the SMS API page.