Live WhatsApp voice calls — real WebRTC, real SDP / ICE.
WhatsApp voice calling, live in WBIZ. Real WebRTC with SDP / ICE trickle signalling, inbound ringing with FCM push notifications, an in-app ActiveCallCard, outbound dial-out from the agent, and the Meta Call Permission Request flow wired in for the customer pre-authorisation gate.
Live now. HTTPS + a TURN server are required in production; a Call Permission Request flow handles Meta's 7-day customer pre-authorisation window.
Real WebRTC, real signalling
SDP offer / answer with trickle ICE — not a wrapper.
WBIZ implements WhatsApp voice calling with real WebRTC: SDP offer / answer exchange with Meta and trickle ICE candidate signalling. Outbound dial-out works from the agent UI; inbound calls trigger an FCM push notification and surface as an ActiveCallCard inside the inbox.
- Real WebRTC: SDP offer / answer + trickle ICE candidates
- Inbound ringing via FCM browser push notifications
- Outbound dial-out from the agent UI
- ActiveCallCard surfaced live in the inbox
Acme Customer Care
Connecting via WhatsApp · 00:14
Meta Call Permission gate
Customer pre-authorisation, handled.
Meta blocks outbound calls (errors 138006, 2593090) unless the customer has pre-authorised your business to call. WBIZ wires the Call Permission Request flow 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 flow wired into the toast
- 7-day customer permission window tracked
- Auto-handle Meta errors 138006 / 2593090
- 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 + 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. Same agent surface, same contact context. Outbound-call UI polish and a reconnect / re-ring flow are deferred — the core call path is live today.
- Call history per conversation thread
- Same agent UI as the inbox
- FCM push notification on inbound ring
- Live now — no waitlist, no flag, no beta
Acme Customer Care
Connecting via WhatsApp · 00:14
By the numbers
What teams ship on WBIZ.
0
Real WebRTC SDP / ICE implementation
0d
Meta 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 the WebRTC signalling, the Meta call-permission gate, the FCM push for inbound ringing, and the in-app call UI. HTTPS plus a TURN server are required in production; outbound-call UI polish and reconnect are on the deferred-list, the core path is live.
Real WebRTC
SDP offer / answer with trickle ICE — not a third-party wrapper.
Permission gate
Meta's pre-authorisation flow surfaced in-app with a 7-day permission window.
FCM ring + ActiveCallCard
Inbound calls push via FCM and surface as an ActiveCallCard inside the inbox.
Call history per thread
Every call attaches to the conversation thread — chat + voice 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; no prebuilt CRM connector.
WBIZ Inbox
Calls + chats in one surface
Automations
Trigger templates around the call
Contacts
Caller identified by phone
CALL_PERMISSIONS template
Pre-auth via approved template
Webhooks
Stream call events into your stack
REST API
Programmatic call permission management
FAQ
Calling, answered.
Yes — live now, not behind a flag, not on a waitlist. The implementation is real WebRTC: SDP offer / answer with trickle ICE candidate signalling, inbound ringing via FCM push, outbound dial-out from the agent UI, and an ActiveCallCard inside the inbox.
Meta requires customer pre-authorisation for outbound calls (errors 138006 and 2593090). WBIZ wires the Call Permission Request flow into the in-app toast and tracks the 7-day permission window per contact, so the gate is handled cleanly when it triggers.
Two requirements: the calling page must be served over HTTPS (browser WebRTC requirement) and a TURN server is required so calls work across NAT / 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; recording / 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.