A dedicated number is a phone number rented for your exclusive use as an SMS sender in one country, so that replies reach you and recipients can recognise and save it.
A dedicated number turns one-way notifications into a channel. Because nobody else sends from it, replies come back to you, keywords such as STOP, YES or C can trigger actions in your system, and the number stays the same across campaigns, so recipients can save it and see every message in one thread. Its reputation is yours as well, whereas a pooled number's reputation depends on everyone who sends from it.
The number is provisioned with an operator in the destination country and mapped to your account. Outbound messages use it as the originating address; inbound messages to it, the mobile-originated traffic, reach the gateway and are passed on to you, typically by webhook. It is rented per country, usually by the month, because a number must belong to the destination's numbering plan to be reachable locally. Some countries attach conditions to numbers used for application traffic, such as 10DLC registration in the United States.
Example
A hypothetical dental practice in Canada sends reminders from a dedicated local number: "ACME Dental: cleaning on Thursday at 09:00. Reply C to confirm or R to reschedule." Replies arrive at its booking system as inbound events; a C marks the appointment confirmed, an R opens a task for the front desk. Patients who saved the number find a year of reminders in a single thread.
Common mistakes
- Expecting one number to serve several countries.
- Publishing the number with no person or system handling the replies.
- Ignoring STOP replies that arrive on it.
- Renting numbers where a name would be delivered and one-way messages are all that is needed.
At SMSMeteor: in destinations with the "Numeric sender" rule, the Americas and China, a local number is substituted for names free of charge, and a dedicated number with inbound can be rented when you need replies. Inbound messages on rented numbers are delivered as webhook events, signed with HMAC-SHA256 like every other event. See two-way SMS for the use case.
