Two people talk.
Neither number is shared.
WOCOM365 Number Masking connects two parties through a temporary proxy number, so real phone numbers are never exposed to each other — with automatic expiry once the transaction ends, and full call recording for compliance on your side.
Privacy that doesn't get in the way of the call
Number masking connects two people who need to talk — a driver and a rider, a buyer and a seller, a doctor and a patient — through a temporary proxy number instead of exchanging their real phone numbers. When either party dials, the call bridges seamlessly through that proxy, and it feels like a normal phone call on both ends. Neither side ever sees, stores, or can later reuse the other's actual number.
That proxy number is session-based: it's tied to a specific order, booking or interaction, and once that context ends, the number expires and returns to a shared pool to be reused for someone else. This is what stops a delivery rider from being able to call a customer again after the order is delivered, or a marketplace seller from contacting a buyer outside the platform.
Masking the numbers from each other doesn't mean losing visibility yourself — every call can still be recorded and logged on your platform's side, so you retain full oversight for quality, disputes and compliance even while the two parties on the call stay anonymous to one another.
One masking layer, configured to how much privacy each side needs
Run all three from the same platform, with unified session management.
Two-Way Masking
Both sides connect through the proxy, with neither party's real number ever exposed to the other.
One-Way Masking
Protect just one side, such as an agent's direct line, while still capturing the customer's real number for CRM.
Session-Based Temporary Numbers
Proxy numbers expire automatically once a booking or transaction is complete, then recycle for reuse.
From two strangers to a connected call, without exposing either side
The privacy layer is invisible — both parties just dial and talk.
Two parties need to connect
An order, booking or enquiry links two users who need to talk without sharing numbers.
A proxy number is assigned
WOCOM365 links a temporary number to both real numbers for the duration of the session.
The call bridges seamlessly
Either party dials the proxy, and the call connects like a normal call, in under a second.
The session expires
Once the transaction ends, the proxy number deactivates and is recycled into the pool.
Everything a trust-and-safety team asks for, out of the box
Two-Way Number Masking
Protect both parties on a call with a single shared proxy number for the interaction.
Session-Based Temporary Numbers
Proxy numbers tied to a specific order or booking, active only for as long as needed.
Automatic Expiry & Recycling
Numbers deactivate the moment a session ends and return to the pool for reuse elsewhere.
Call Recording for Compliance
Every masked call recorded and logged on your side, for disputes and quality review.
Works via App or Direct Dial
Trigger masking from within your app, or let users dial the proxy number directly.
Session Management Dashboard
See every active masked session, its parties and status, from a single real-time view.
Trust that doesn't ask anyone to give something up
Two strangers can talk without either becoming reachable forever
Any platform that connects strangers — a marketplace, a ride-hailing app, a delivery service — asks users to trust people they've never met. Number masking removes the biggest personal risk in that exchange: neither party has to hand over a phone number they'll never be able to take back.
- Real numbers never exposed to the other party
- Reduces spam, harassment and misuse risk
- Makes platform trust a feature, not just a policy line
Once the order's delivered, the connection closes on its own
A phone number exchanged once tends to stay reachable forever, whether or not that's what either person wanted. Session-based masking builds in a natural end point: when the delivery, booking or transaction is complete, the proxy number simply stops working, and neither party can contact the other through the platform anymore.
- No lingering contact after the transaction ends
- Numbers recycled automatically, no manual cleanup
- Clear, enforced boundary between platform users
Anywhere a platform connects two people who don't already know each other
From a delivery rider to a telehealth doctor, number masking earns its place wherever trust and privacy both matter.
Logistics & Delivery
Real Estate
Healthcare
E-Commerce & Marketplaces
BFSI
Works with the tools your team already uses
Trigger masked sessions from your app or order system, and log every call automatically.
- Session triggers from app or order events
- Call logs synced to platform records
- API & SDK for direct app integration
Built for platforms running thousands of masked sessions at once
The privacy layer scales the same way the rest of your platform does.
Large-Scale Number Pooling
A shared pool of proxy numbers reused efficiently across thousands of concurrent sessions.
Sub-Second Call Bridging
Masked calls connect as fast as a direct call, with no perceptible delay from the privacy layer.
Multi-Party Masking
Bring a support agent or third party into a masked call without exposing anyone's real number.
Fraud & Abuse Monitoring
Flag unusual call patterns on masked sessions to catch misuse before it becomes a bigger problem.
Geo-Based Number Allocation
Assign proxy numbers with local area codes so masked calls still feel familiar to each caller.
API & SDK for App Integration
Trigger, manage and end masked sessions directly from your own app or platform code.
Privacy that customers actually noticed, and trusted
Logistics A delivery platform protected driver and customer numbers through every order +
Every delivery now connects driver and customer through a masked number that expires the moment the order is marked delivered, eliminating post-delivery contact while keeping full call logs for support.
Real Estate A property portal let buyers and agents connect without exchanging numbers +
Buyers now enquire about listings through masked calls, protecting their personal number from agents while giving the portal full visibility into call volume and lead quality by listing.
Healthcare A telehealth platform masked doctor-patient calls for privacy and compliance +
Patients and doctors connect through a session-based masked number for each consultation, protecting both parties' personal numbers while every call remains recorded for compliance review.
What businesses say
"Number masking was the single feature that made customers actually trust our platform with their phone number."
"Buyers enquire far more freely now that they know their number isn't going straight into an agent's phone forever."
"Our doctors were hesitant to take consultations on their personal number. Masking solved that concern in a single conversation."
Frequently asked questions
What is number masking and how does it work?
Number masking connects two people through a temporary proxy number instead of exchanging their real phone numbers. When either party calls, the call is bridged through the proxy, so neither side ever sees the other's actual number, while the call remains fully recorded and trackable for the business operating the platform.
Is number masking one-way or two-way?
WOCOM365 supports both. Two-way masking hides both parties' real numbers from each other, common in marketplaces and ride-hailing. One-way masking can hide just one side, such as protecting an agent's direct line while still capturing the customer's real number for your CRM.
What happens to the proxy number after a transaction ends?
Proxy numbers are session-based and expire automatically once a transaction, delivery or booking is complete, after which they're recycled into the number pool. This prevents either party from being able to contact the other directly once the reason for connecting them has ended.
Are masked calls still recorded for compliance and disputes?
Yes. Masking a number from the two parties on the call doesn't mean the business loses visibility — every masked call can still be recorded and logged on the platform side for quality review, dispute resolution and compliance.
How fast does a masked call connect?
WOCOM365 bridges masked calls in under a second on average, so the privacy layer is invisible to both parties — the call simply connects like a normal phone call.
Can number masking be integrated into our existing app?
Yes. WOCOM365 provides an API and SDK so number masking can be triggered directly from your app or platform whenever two users need to be connected, without any change to how either party dials.
Ready to let people connect without exposing a number?
Talk to a WOCOM365 specialist and get number masking integrated into your app this week.