Phone Number Masking
Connect two people through a proxy number so neither sees the other's real one. The pattern behind every delivery app that lets you call your driver without learning their mobile number.
Number masking connects two parties through an intermediary number so neither sees the other's real number. Each side dials a proxy; the platform bridges the two legs into one conversation. The numbers on both ends stay private, and when the pairing is removed the route closes with it.
How a masked call actually works
There is no single call. The platform places two, and joins them. A customer dials the proxy number they were given; the platform answers that leg, looks up which pairing the proxy currently belongs to, dials the other party on a second leg, and bridges the audio. Each party's own number is only ever visible to the platform.
This is why masked minutes cost roughly double. You are paying for two call legs, not one — the leg in from the caller and the leg out to the recipient. Cost models that budget for a single leg are usually out by a factor of two, and that gap is the most common surprise in a masking rollout.
The pairing is the other half. A proxy number is not assigned to a person; it is assigned to a conversation, for as long as that conversation should exist. When the delivery completes or the listing expires, the pairing is torn down and the number returns to the pool. That expiry is the feature — it is what stops a customer calling a driver three weeks later.
Where it is used
- Delivery and ride-hailing A driver and a customer need to speak about one order, once. Both are given a proxy number that routes to the other for the life of the job, then stops working. Neither keeps a number they can call again next week.
- Marketplaces and classifieds Buyer and seller negotiate without handing over a personal mobile. If the deal falls through, the contact route closes with it, which removes the usual complaint about being called for months after a listing expires.
- Property and viewings An agent publishes a tracking number per listing rather than a direct line. Calls reach the right person, the listing number can be retired, and the enquiry is attributable to the property that produced it.
- Healthcare and support callbacks A clinician or agent calls a patient from a personal device while the practice number is presented. The patient can return the call and reach the practice, not the individual who happened to be on shift.
- Recruitment and field staff Temporary or contract staff make calls that present the employer number. When the contract ends the routing is removed, and no customer is left holding a private mobile number.
Masking, caller ID masking and spoofing
These three get used interchangeably and they are not the same thing. The distinction matters because one of them is illegal.
| Term | What it does | Legal status |
|---|---|---|
| Number masking | Two-way. Both parties are hidden from each other behind a proxy number you control. | Legal; standard in marketplace and delivery apps. |
| Caller ID masking | One-way. An outbound call presents a business number you are entitled to use instead of the device placing it. | Legal, provided you have the right to present that number. |
| Caller ID spoofing | Presenting a number you have no right to use, to deceive the person answering. | Illegal in the US under the Truth in Caller ID Act where intent is to defraud or cause harm. |
The practical difference is authorisation, not technology — the mechanism is the same in all three. Masking is legitimate because the proxy number belongs to you. STIR/SHAKEN attestation reinforces that: calls presenting a number the originating carrier can attest to are signed, and increasingly, calls that cannot be attested get labelled as spam before anyone answers. A masking deployment built on numbers you legitimately hold attests cleanly. One built on borrowed numbers does not, and the carrier labelling will quietly destroy your answer rates.
Sizing a number pool
The common mistake is buying a number per user. Pools are sized on peak concurrent conversations, not total users, because numbers are recycled as pairings expire. A service with fifty thousand users but four hundred simultaneous active jobs needs a pool in the hundreds, not the tens of thousands.
Two constraints shape it. First, area code: a proxy number should usually look local to the person receiving it, so a national service needs coverage across regions rather than depth in one. Second, the cooling-off period — a number returned to the pool should not be reissued immediately, or a customer calling back about yesterday's order reaches a stranger. A delay before reuse costs you a slightly larger pool and prevents the single worst failure mode this system has.
What this needs from a phone platform
Static masking is straightforward on a normal cloud phone system: a tracking number per listing, or a forwarding rule that presents the business caller ID rather than the mobile actually dialling. Our global numbers and SIP trunking cover that today, including guaranteed CLI delivery on wholesale routes.
Dynamic masking is a different requirement. Creating and expiring pairings per transaction means programmatic control over routing, and that is a scoped integration rather than a self-serve feature — our public API is not published yet. If you are building a marketplace or dispatch product that needs it, tell us the call volume and destinations and we will tell you plainly whether we are the right fit, rather than selling you a number pool you cannot drive.
Frequently asked questions
What is phone number masking?
Phone number masking connects two people through an intermediary number so neither sees the other’s real number. Each party dials or receives a proxy number, the platform bridges the two legs, and the actual numbers stay hidden on both sides. It is used wherever two strangers need to speak once — a driver and a customer, a buyer and a seller — without exchanging permanent contact details.
What is the difference between number masking and caller ID masking?
Caller ID masking changes what the recipient sees on an outbound call: the call presents a business number instead of the device actually placing it. Number masking is two-way — it hides both parties from each other by routing the whole conversation through a proxy number. Caller ID masking protects the caller; number masking protects both and also controls whether the two can reach each other again.
Is number masking legal?
Masking a number is legal where the intent is privacy, and it is standard practice in delivery, ride-hailing and marketplace apps. What is not legal is caller ID spoofing — presenting a number you have no right to use in order to deceive the recipient. In the US the Truth in Caller ID Act prohibits transmitting misleading caller ID with intent to defraud or cause harm, and STIR/SHAKEN attestation makes unauthenticated numbers increasingly likely to be labelled as spam. Masking works because the proxy number is one you legitimately control.
Does the recipient know the number is masked?
They see a real, dialable number — it simply is not the other party’s personal one. Most implementations do not announce the masking. If you need the caller to understand why the number is unfamiliar, a short whisper message before the call connects is the usual approach, and it measurably reduces the number of calls rejected as suspected spam.
How many numbers does number masking need?
Fewer than most teams expect. Numbers are pooled and recycled rather than assigned permanently: a proxy number is tied to a conversation for its duration, then returned to the pool. The pool size is driven by peak concurrent conversations in a given area code, not by total users. A cooling-off period before reuse stops a returning caller reaching the wrong party.
Can I do number masking with a normal phone system?
Partially. A cloud phone system gives you the pieces — DIDs in the right area codes, control over the caller ID presented, and routing rules — which covers static cases such as per-listing tracking numbers or presenting a business number from a personal device. Dynamic masking, where a pairing is created and torn down per transaction, needs programmable control over call routing. If that is what you are building, talk to us about requirements rather than assuming it works out of the box.
What does number masking cost?
Three components: the numbers in the pool, charged monthly per DID; the call minutes, which are billed on both legs because the platform bridges two calls rather than one; and the routing itself. Doubling the minutes is the part most cost models miss. For a pooled deployment the number rental is usually the smaller line item, because recycling keeps the pool far below the user count.
Related
Building something that needs masked calling?
Tell us the volume, the destinations and whether pairings are static or per-transaction. We will tell you what is possible today and what is not.