HomeSolutionsIn-App Calling & Number Masking
WebRTC SDK & Privacy Proxy

Embed in-app voice calls and protect phone numbers with privacy masking.

Enable click-to-call directly inside web and mobile apps with @firetell/firetell-client-sdk and signed Client JWTs requiring call_flow_id, or connect marketplace buyers and drivers through proxy virtual numbers.
Client JWT signed with Console API Key secret
Mandatory call_flow_id outbound routing
PSTN number masking via JCA to_operator
$0.00 intra-workspace extension & team calls
Two Privacy & In-App Architectures
WebRTC + PSTN Proxy
In-App Calling • Client JWTApp Client -> Client JWT (call_flow_id) -> Outbound FlowSign short-lived JWTs on your backend. Every app-originated call enters your published outbound Call Flow.
Number Masking • JCACaller -> Virtual Proxy DID -> JCA Webhook -> to_operatorHide personal numbers on delivery or ride-hail calls while keeping the proxy DID as caller ID.
Communication patterns

Support internal teams, in-app support, and two-sided marketplaces.

Place & receive calls directly inside web and mobile apps

Authenticate browser or Flutter clients with a JWT signed using an API Key secret from the Console. The call_flow_id claim is mandatory so every app call executes your designated outbound flow.
Works across Web (@firetell/firetell-client-sdk) and iOS/Android (Flutter)
Receive call_ring and call_offer events for incoming calls
Optional recording and transcription attached automatically
Marketplace proxy flow

How Firetell executes PSTN number masking step by step.

0101

Dial Proxy DID

Courier or buyer dials your assigned Firetell virtual number.
0202

JCA Webhook POST

Call Flow invokes call_flow.jca with caller_number and destination_number.
0303

Order DB Lookup

Your backend resolves the matching counterparty's real phone number.
0404

Bridge to_operator

Return to_operator so Firetell connects legs showing only the proxy DID.
Production implementations

Sign Client JWTs, trigger WebRTC calls, and bridge masked PSTN numbers.

json
// Sign with an API Key secret from the Firetell Console
// call_flow_id is mandatory for Client API outbound calls
{
"iss": "sid-650000000000000000000001",
"aud": "client-api",
"sub": "partner_user_driver_12",
"domain": "yourcompany.firetell.app",
"exp": 1786022400,
"call_flow_id": "cf_outbound_in_app_default"
}
Built with Firetell Products

Everything powering in-app voice and proxy privacy.

JCA & Outbound

Call Flow Builder

Publish outbound flows for Client JWTs and JCA webhooks for masking.
Explore Call Flows
Web & Mobile SDK

Client Apps & SDKs

Open-source Web, iOS, Android, and Chrome examples using @firetell/firetell-client-sdk.
Explore Call Center
Proxy DIDs

Virtual Phone Numbers

Provision proxy numbers across 50+ countries for regional marketplaces.
Explore Phone Numbers
FAQ

Frequently asked questions

Requiring call_flow_id ensures every call placed by an in-app browser or mobile client enters the exact outbound Call Flow designed on the Console (for caller ID rules, recording, or routing security).
No. Firetell presents your virtual proxy DID on the call and dynamically bridges to the recipient's number returned by your JSON Call Action endpoint via to_operator.
Yes. Enable call recording inside the flow or pass the recording action alongside to_operator in your JCA response.

Protect user privacy and embed calling straight into your app.

Start building with WebRTC SDKs free using $3 API credit.