Can AI Answer Phone Calls From Your Website? (Browser Voice Explained)
Chirps Team
2026-06-06
Phone trees feel dated. Visitors on your pricing page want to ask a question the way they ask a colleague—by speaking—not by hunting through FAQ accordions. Browser voice puts a microphone inside your existing chat widget: no PBX, no new phone bill, same RAG-trained brain as text chat.
Chirps browser voice uses the visitor's device mic and speakers. The assistant listens, retrieves answers from your crawled site and PDF uploads, and responds in natural speech. For callers who dial your business number, a phone-line add-on is a separate path—but most SMBs start with in-widget voice because setup takes minutes.
Browser voice vs phone line
- Browser voice: Mic in widget; visitor stays on site; WebRTC audio; no telco setup; minutes to enable after crawl.
- Browser voice cost: Included in widget usage; no per-minute carrier fees for the web session.
- Phone line add-on: Visitors dial your published number; same trained assistant; for truck-sign and business-card callers.
- Phone line setup: Purchase number in dashboard; attach to assistant; number rental + usage fees.
- Both share: Same RAG knowledge, dispatch to WhatsApp/SMS/Telegram/Discord, same escalation rules.
Best use cases
When voice beats typing
High-consideration purchases (real estate, legal intake, HVAC emergencies), older users, vision limitations, and hands-busy scenarios—driving home, on a job site, cooking. Local trades, SaaS evaluators browsing docs, and ecommerce shoppers clarifying sizing all benefit.
Setup steps for browser voice
- Crawl your site and upload key PDFs so voice and chat share one knowledge base.
- Enable voice in the Chirps widget customizer.
- Write a clear mic-permission prompt: "Tap to talk—same answers as chat, hands-free."
- Add chat fallback for open offices and noise-sensitive users.
- Connect dispatch so voice sessions escalate to your phone with transcript.
- Test on iOS Safari and Android Chrome.
First-time visitor flow
1. Visitor opens widget on mobile → taps microphone. 2. Browser requests mic permission (after GDPR consent if enabled). 3. Visitor: "Do you install water heaters in Naperville?" 4. Assistant (service-area crawl): "Yes, Naperville is in our service area. Schedule a callback?" 5. If stuck: dispatch to owner SMS with session summary.
Latency and UX tips
- Keep responses to one or two sentences, then offer a follow-up.
- Confirm understanding: "You need emergency service tonight, correct?"
- Show transcript alongside audio so users can scan phone numbers.
- Use dark mode for night traffic; offer chat fallback after two recognition failures.
- Never auto-start recording—disclose voice processing in your privacy policy.
Add voice to your widget
Enable browser voice on your trained assistant—same crawl, same dispatch, no PBX required.