Nothing about a telephone number itself limits it to one person. A number is a routing key: the PSTN and IP interconnects deliver calls addressed to it, in E.164 form, to whichever service provider holds it. What happens after delivery is up to that provider's platform. A shared number is a DID whose platform fans inbound calls and messages out to a set of people, and lets any of them respond as the number.
The pattern predates VoIP: a family landline was a shared number, and key telephone systems let any desk pick up "line 1." Modern platforms implement the same idea in software, adding what copper could not: shared text threads, visible history, and presence, so the team can see who is on a call and what was already said.
How one number rings many endpoints
On the inbound side the platform receives one call and creates several. In SIP terms this is forking: a proxy that holds multiple registrations for the same address-of-record sends the INVITE to all of them (parallel forking) or one after another (sequential forking), as defined in RFC 3261. The first endpoint to answer wins, and the platform cancels the other legs. App-based platforms do the equivalent with push notifications to each teammate's mobile and desktop clients, which is why one call can ring a phone, a laptop, and a browser tab at once.
- A caller dials the shared number: ordinary inbound traffic to one DID.
- The platform answers or forks the call to every teammate assigned to the number, subject to schedules and availability.
- Someone answers; the remaining legs are cancelled. Nobody answers: the call overflows to voicemail, a forward, or an AI receptionist.
- The call, its recording if enabled, and any notes land in a history every assignee can see.
Outbound is the mirror image: whichever teammate places the call, the caller ID presents the shared number, and any CNAM listing on it shows the business name. Recipients see one consistent identity regardless of who dialed.
Texting on a shared number
SMS makes sharing more valuable and more delicate. A text conversation is a single thread per contact, so a shared number needs shared state: every teammate sees the same thread, replies appear under the same number, and the platform has to prevent two people from answering the same message differently. Common mechanisms are thread assignment (one owner at a time), typing and viewing indicators, and internal notes that ride alongside the customer-visible thread. In the US, application-to-person texting from a shared local number is still 10DLC: registration attaches to the number and campaign, not to how many people use it.
Shared number, extensions, hunt group, or separate DIDs
| Model | What callers dial | Who answers | Texting | Fits |
|---|---|---|---|---|
| Shared number | One number | Any assigned teammate; first to answer | One shared thread per contact | Small teams presenting one identity: support, sales, front desk |
| Main number + extensions | One number, then an extension or menu | The specific extension owner | Extensions have no texting identity | Larger orgs where callers seek a specific person |
| Hunt group | One number | Members in a configured ring order | Not defined by the hunt group itself | Voice-only distribution with ordered escalation |
| Separate DIDs per person | A different number per person | That person | Individual threads per number | Direct lines, personal follow-up, outbound-heavy roles |
The practical difference from a hunt group alone is scope. A hunt group is a voice routing rule: it decides which phones ring. A shared number as a product also covers the messaging thread, the shared history, and the outbound identity. The difference from extensions is direction: extensions ask the caller to know the structure; a shared number keeps the structure invisible.
Operational details that matter
- Collision handling: while one teammate is on a call, others should see the line as busy; a second inbound call becomes a second forked call or queues.
- Availability and hours: sharing works only as well as the schedule that drives it; after-hours the number should route to voicemail or an answering layer, not ring empty desks.
- Recording and consent apply per call, not per number: whoever answers, the same one- or two-party consent rules govern.
- E911 is per user location, not per number: a shared number used from three cities needs each user's emergency address registered, because the number's registered address will not match everyone.
- Porting: a shared number is portable like any other DID; see number porting. What moves is the number, not the sharing behavior, which is rebuilt on the new platform.