Requirements
- Plan: Growth or Pro (the AI Receptionist must be enabled)
- Voice assistant configured: see AI Receptionist
- Microphone access: visitors will be prompted by their browser to allow mic; if they decline, the button gracefully degrades to text chat
How visitors use it
When a visitor opens the chat widget on your site, they see two interaction options: type a message, or tap Call (or the “Talk to us” button under the greeting) to start a voice call. Tapping:- Browser prompts for microphone access (one-time per origin).
- Connection initializes — usually under 2 seconds.
- The AI greets the visitor with the same greeting it uses on phone calls.
- They can talk naturally; the AI Receptionist responds in real time.
- Either side can end the call.
Enable / disable
The web call button shows when all of these are true:- You’re on Growth or Pro
- The AI Receptionist is configured
- Voice calls is switched on for the widget (Dashboard → Widget → Content)
- The voice safety cap hasn’t been hit for the period
Costs and minutes
Web calls count against the same monthly voice minutes allowance as phone calls. There’s no extra per-call fee on top of voice minutes — the only cost is the minutes the call uses.When this is most useful
- Visitors who hate calling. Younger demos especially — Gen Z and millennial customers often prefer voice over typing once they’ve seen the option, but won’t pick up a phone first.
- Mobile visitors. Easier to tap a phone icon than to copy a number, switch to the dialer app, and call.
- Out-of-area visitors. Visitors browsing your site from another country can’t easily call your local number; web call works regardless of geography.
Privacy
Visitors are anonymous unless they share a name during the call. The contact appears in your CRM as a “Web call” with whatever they introduced themselves as. If they book an appointment, the booking flow captures phone/email and a real contact is created.Browser support
Works on every modern desktop and mobile browser — Chrome, Edge, Safari, Firefox, plus iOS/Android Safari and Chrome. Some corporate networks block WebRTC; those visitors fall back to text chat automatically. If the Call button shows “Call failed”, the usual cause is a security header on your own website blocking the microphone — it typically fails in Chrome while still working in Firefox. See Voice calls not working.Next
You’re done with the widget. Next stops:Build a lead form
For longer-form lead capture (quote requests, intake forms).
Connect your calendar
So the AI Receptionist can book real appointments during these conversations.