Marketplace number masking: connect people without revealing phone numbers
An intermediate number links a buyer and a seller. Each calls that number and never sees the other. Custom quote pricing.
Custom quote
Number masking keeps a platform from exposing its users' contact details. Instead of swapping numbers, the two parties go through an intermediate number provided by TELQIO.
Each connection gets its own intermediate number. The call is forwarded to the other party according to the pairing your application declared. Logs keep calls by connection, without showing real numbers to users who lack the rights.
Your application defines how long a pairing lasts. When the job is over, the number is released and can be reassigned to another connection.
How it flows
Practical uses
Delivery and transport
The customer and the courier reach each other during the job without knowing their numbers.
Peer-to-peer rentals
Owner and renter talk by phone without sharing their contact details.
Home services
A platform connects a provider and a customer for a visit.
Real estate
A buyer contacts an agent from a listing without exposing a personal number.
Features
- Intermediate number per connection
- Pairing between two parties declared by your application
- Release and reassignment of numbers
- Call log by connection
- Real numbers masked according to the console user's rights
- Numbers and costs attached to a project
Limits to know
- How many intermediate numbers you need depends on how many connections are active at the same time.
- Masking hides the number only in exchanges that go through TELQIO. It does not control what people say or share elsewhere.
- How the caller's number appears on the recipient side depends on the country and the carrier.
- Call recording is off by default. Turning it on is a decision for your platform, with the people informed.
- A call through an intermediate number has two segments: it can produce two usage lines, depending on the contract.
curl -X POST "https://api.example.test/v1/calls" \
-H "Authorization: Bearer tq_test_EXEMPLE" \
-H "Idempotency-Key: 7b1d2c4e-0000-4000-8000-000000000005" \
-H "Content-Type: application/json" \
-d '{
"from": "+33199001234",
"to": "+33199001235",
"project_id": "marketplace_a",
"flow_id": "flow_masking_example"
}'
# => { "id": "call_example", "status": "ringing", "simulated": true }
# "from" is the connection's intermediate number.
# The recipient does not see the other party's real number.Technical details
| Principle | One intermediate number per connection, paired with two parties |
|---|---|
| Control | POST /calls with a masking flow |
| Log | Calls by connection, numbers masked according to rights |
| Release | Number reassignable when the connection ends |
Frequently asked questions
Do the two parties see each other's number?
No. Each sees the intermediate number. How the caller's number finally displays still depends on the country and the carrier.
How long does a pairing stay active?
Your application declares and closes it. The number is then released and can serve another connection.
Can I record masked calls?
Recording is off by default. If you turn it on, people must be informed in an appropriate way.
Related use cases
Documentation
Related services
Protect your marketplace's phone numbers
Describe your connections, their duration and the countries. We will size the intermediate numbers with you.