Browser calling lets your users place and receive phone calls from a web page, with a headset and no handset or separate app. Your server asks Sautikit for a short-lived token, the @sautikit/webrtc SDK in the browser registers with it, and Sautikit connects the browser to the phone network. Calls to Kenyan numbers cost KES 3.00 a minute billed per second, and incoming calls are free.
It suits support and sales teams who work inside a CRM or ticketing screen, and products that want a "call us" or click-to-dial button.
The API key never leaves your server. Only the short-lived SIP token (5-minute TTL) is handed to the browser. Even if intercepted, an expired token grants no access. Each browser session should receive its own token; do not share one token across multiple users or tabs.
Your token endpoint should be behind your own authentication layer so that only logged-in users receive tokens. A user who obtains a valid token can place calls that are billed to your workspace, so treat the token endpoint with the same care as any billing-sensitive route.
The browser SDK can also receive inbound calls. When a call arrives at a Sautikit number whose routing webhook returns a Dial action targeting a SIP URI associated with the browser session, the SDK fires a client.on("incoming", (call) => ...) event. The user can accept or reject the call from the UI.
Minting a token, or a browser that is connected and idle
Free
Incoming calls answered in the browser
Free
Outgoing calls to Kenyan numbers
KES 3.00 a minute, billed per second after the call is answered
Unanswered calls
Free
Number
KES 500 a month
An agent who makes 10 outgoing calls of 4 minutes each in an hour costs 40 × KES 3.00 = KES 120 for that hour. An agent who only answers incoming calls costs nothing in call charges. There is no extra charge for WebRTC.