Live WhatsApp voice calls, on real WebRTC.
WhatsApp voice calling, live in WBIZ. Real WebRTC with trickle ICE signalling, inbound ringing with browser push notifications, an in-app call card, outbound dial-out from the agent, and the call permission flow wired in for the customer pre-authorisation gate.
Live now. Production needs HTTPS and a TURN server. A call permission flow handles the 7-day customer pre-authorisation window.
Real WebRTC, real signalling
Real SDP and trickle ICE, not a wrapper.
WBIZ implements WhatsApp voice calling on real WebRTC, with an SDP offer and answer exchange and trickle ICE candidate signalling. Outbound dial-out works from the agent UI, and inbound calls trigger a browser push notification and surface as a live call card inside the inbox.
- Real WebRTC with SDP offer and answer plus trickle ICE
- Inbound ringing via browser push notifications
- Outbound dial-out from the agent UI
- A live call card surfaced in the inbox
Acme Customer Care
Connecting via WhatsApp · 00:14
Call permission gate
Customer pre-authorisation, handled.
WhatsApp blocks outbound calls (errors 138006 and 2593090) unless the customer has pre-authorised your business to call. WBIZ wires the call permission request into the inbox toast, with a 7-day permission window, so when an agent dials out the gate is enforced and re-requested cleanly.
- Call permission request wired into the toast
- A 7-day customer permission window, tracked
- Handles the call-permission error codes automatically
- Permission state surfaced on the contact
Call routing
IVR + agentsStep 1 · Greet
“Welcome to Acme. Press 1 for sales, 2 for support.”
Step 2 · Route
If 2 → Support team (round-robin, 5 agents online)
Step 3 · Connect
Aman P picks up · 00:04 to connect
Calls and chats in one surface
Calls live next to the same conversation thread.
Inbound and outbound calls attach to the conversation thread they belong to, so the call history sits right alongside the chat history, in the same agent surface with the same contact context. Outbound-call UI polish and a reconnect flow are deferred. The core call path is live today.
- Call history per conversation thread
- The same agent UI as the inbox
- A push notification on every inbound ring
- Live now, with no waitlist, no flag and no beta
Acme Customer Care
Connecting via WhatsApp · 00:14
By the numbers
What teams ship on WBIZ.
0
Real WebRTC implementation
0d
Call-permission window tracked
0
PBX or hardware required
0
TURN server required in production
The end of "please call us at this number."
Customers can call your business number on WhatsApp directly. WBIZ wires up the WebRTC signalling, the call-permission gate, the push for inbound ringing, and the in-app call UI. Production needs HTTPS and a TURN server. Outbound-call UI polish and reconnect are deferred, and the core path is live.
Real WebRTC
An SDP offer and answer with trickle ICE, not a third-party wrapper.
Permission gate
The pre-authorisation flow surfaced in-app, with a 7-day permission window.
Push ring and call card
Inbound calls push a notification and surface as a live call card inside the inbox.
Call history per thread
Every call attaches to the conversation thread, so chat and voice sit next to each other.
Plays nicely with
Voice calling inherits the rest of WBIZ.
Your existing inbox, automations, contacts and templates carry through to voice. Push call events into your stack via outbound webhooks. There is no prebuilt connector.
WBIZ Inbox
Calls and chats in one surface
Automations
Trigger templates around the call
Contacts
Caller identified by phone
Permission template
Pre-auth via an approved template
Webhooks
Stream call events into your stack
REST API
Manage call permission programmatically
FAQ
Calling, answered.
Yes, live now, not behind a flag and not on a waitlist. The implementation is real WebRTC, with an SDP offer and answer plus trickle ICE signalling, inbound ringing via push, outbound dial-out from the agent UI, and a live call card inside the inbox.
WhatsApp requires customer pre-authorisation for outbound calls (errors 138006 and 2593090). WBIZ wires the call permission request into the in-app toast and tracks the 7-day permission window per contact, so the gate is handled cleanly when it triggers.
Two things. The calling page must be served over HTTPS, which the browser requires for WebRTC, and a TURN server is needed so calls work across NAT and firewalls. Both are operational requirements you arrange in your hosting.
Call recording, transcription and queueing are not shipped today. The core call path is live, and recording and QA workflows are on the roadmap.
No. Voice calling happens inside the same WhatsApp app they already have. They tap to call your business number directly inside their existing WhatsApp conversation.