Configure

Voice chat

Visitors can switch to a spoken conversation with your agent at any point. A single tap on the headphone chip starts a real-time voice call through xAI’s Grok voices. Interruption, transcript capture, and graceful fallbacks to text are all handled for you.

Turn it on

Open Settings → Voice in the dashboard.
Pick your provider (xAI Grok, OpenAI Realtime, or Google Gemini Live) and how to authenticate. The simplest option is Reuse my text-chat key — if text chat already works with that provider, voice just works too. Otherwise paste a voice-enabled key (console.x.ai for xAI, platform.openai.com for OpenAI, aistudio.google.com for Gemini).
Pick a silence timeout (default 10s) and max call length (default 15 min).
Open Billing → Voice and pick a plan (see below). Metered customers get minute bundles; BYOK flat gets unlimited minutes for a flat $49/mo platform fee.
In Customize & Deploy → Appearance, pick a voice UI layout and flip the Enable voice chat switch for each widget you want the chip to appear on. Voice stays hidden on widgets where the toggle is off.
Click Try voice live on the same page to test the selected layout and voice end-to-end in an embedded preview before visitors ever see it.

You don’t need your own xAI key to try voice — Quincer ships a platform-default key that works out of the box on every plan. Pasting your own only matters if you want to bill xAI directly (BYOK) or use a region-specific key.

Pricing

Two billing models, both requiring you to bring your own xAI API key:

Model	Minutes	Price	Best for
Voice 60 Monthly	60/mo	$26/mo	Trying voice on a single widget
Voice 180 Monthly	180/mo	$59/mo	Moderate use across a couple of widgets
Voice 960 Monthly	960/mo	$249/mo	High-volume support / lead teams
Voice 60 / 180 / 960 Add-on	one-time	$29 / $69 / $299	Top up a busy period without changing your plan
Voice BYOK (unlimited)	Unlimited	$49/mo	You pay xAI directly for usage; we charge a flat platform fee

Monthly plans are ~10–17% cheaper than the equivalent one-time add-on.

UI layouts

Voice is visually distinct from text, so Quincer offers four layouts for how the call is presented inside the widget. Pick one under Customize & Deploy → Appearance → Voice layout. A live preview shows exactly how your chosen layout looks before you save.

Layout	What it looks like	Best for
Hybrid default	A compact voice strip slides in above the chat transcript. Transcripts for both sides render inline in the message list as italic bubbles with a mic glyph, so visitors can scroll back through what was said.	Most widgets. Works on desktop and mobile; auto-promotes to takeover under 480px.
Takeover	The whole chat panel swaps to an orb-centric voice UI while the call is live. Text history is hidden until the call ends. Maximum focus.	Support flows where voice is the primary channel, or mobile-first deployments.
Inline	No dedicated strip or orb — transcripts simply appear in the normal message list while a mic-state dot in the header indicates listening / thinking / speaking.	Minimal UIs that want voice to feel like dictation rather than a “call”.
Strip	A slim always-visible control strip at the top of the chat when a call is active. Transcripts render in the message list like Inline, but with richer on-strip controls.	Teams that want the call state obvious without taking over the whole panel.

On screens narrower than 480px, Hybrid and Strip automatically promote to Takeover — there’s not enough room to show a transcript and voice controls side-by-side. The dashboard preview has a Desktop/Mobile toggle so you can see both states.

How it works

Chip in the widget header. When voice is enabled, a small headphone icon appears next to the close button. Visitors can also type “call me” or “switch to voice” to trigger the same flow.
Server-side relay. All voice audio is brokered through our dedicated relay service at voice.quincer.com. Your xAI API key never touches the browser; the relay authenticates with xAI and streams audio both ways.
Knowledge-grounded answers. On every user utterance the relay queries your knowledge base — the same cross-persona vector search text chat uses — and injects the top matches into the model’s context before it speaks. You maintain one KB; both channels stay on the same facts.
Real-time barge-in. The moment the visitor starts speaking, the bot stops talking. No waiting, no hold-to-talk.
Integration tools. Every tool enabled on a persona (HubSpot, Pipeline CRM, Calendly, Gmail, etc.) is callable from voice too. Ask the agent to book a meeting, create a contact, or log a ticket — it narrates what it just did.
Silence + max-length protection. If the agent hears nothing for your configured silence window (default 10s), it politely winds down and switches back to text. Same behavior when it hits the max-call-length safeguard (default 15 min).
Graceful cap handling. Metered customers who run out of minutes mid-call hear a natural wind-down line (“I need to switch back to text as my voice time has run out”) rather than a silent hang-up.
80% warning email. Metered customers get a one-time email per period when they cross 80% usage, with a one-click link to buy more minutes.
Transcripts persist to the inbox. Every voice turn — visitor and assistant — is saved as a message on the same Conversation row a text chat would use, so the live inbox, lead timeline, and Slack escalations all see voice and text as one unified conversation.

Voice providers

Quincer ships with three production voice providers — xAI Grok, OpenAI Realtime, and Google Gemini Live. Pick a default provider under Settings → Voice → Default voice provider; individual personas can select any voice from any enabled provider. All three run over the same relay pipeline, so everything else (layouts, billing, transcripts, knowledge grounding, integration tools) behaves identically.

Provider	Model	Good for
xAI Grok	grok voice	Fast, conversational, five curated voices. Lower latency on average.
OpenAI Realtime	gpt-realtime	Ten voices including the expressive marin and cedar. Strongest when you need nuanced delivery.
Google Gemini Live	gemini-3.1-flash-live	Eight voices (Aoede, Charon, Fenrir, Kore, Leda, Orus, Puck, Zephyr). 70+ languages out of the box, strong multilingual delivery.

Voices

Each persona picks one voice from a dropdown under Personas → [Persona] → Voice. A Preview button next to the dropdown plays a short sample so you can compare tone before saving. The dropdown groups voices by provider.

xAI Grok

Voice	Tone
Eve xAI default	Warm, balanced female voice. Good all-rounder.
Ara	Softer female, calmer cadence.
Leo	Friendly male, conversational.
Rex	Deeper male, more confident delivery.
Sal	Neutral, professional — works well for support.

OpenAI Realtime

Voice	Tone
alloy OpenAI default	Balanced, versatile. OpenAI’s neutral-tone pick.
marin recommended	Most natural delivery. Recommended for nuanced conversations.
cedar recommended	Most natural delivery. Slightly richer than marin.
ash	Expressive, natural male.
ballad	Warm, storytelling.
coral	Friendly, upbeat female.
echo	Clear, confident male.
sage	Calm, thoughtful.
shimmer	Bright, energetic female.
verse	Smooth, musical.

Google Gemini Live

Voice	Tone
Aoede Gemini default	Breezy, conversational.
Charon	Informative, measured.
Fenrir	Excitable, energetic.
Kore	Firm, assertive.
Leda	Youthful, bright.
Orus	Firm, deeper register.
Puck	Upbeat, playful.
Zephyr	Bright, clear.

Leaving the dropdown on Provider default falls back to your org’s default provider’s default voice (Eve for xAI, alloy for OpenAI, Aoede for Gemini).

Troubleshooting

Chip not showing. Confirm Enable voice chat is on for the current widget in Customize & Deploy, and that you’re on a voice plan. The chip is hidden per-widget so agencies can keep voice off on some deployments.
“Voice is not set up for this widget”. No voice API key resolvable. The Voice tab in Settings shows a Ready badge when either your own key is on file or the platform-default xAI key is available. If nothing is ready, paste an xAI key under Enter a separate voice key.
“You’ve used all your voice minutes”. Metered bundle exhausted this period. Buy an add-on on the Billing → Voice page or wait for the next reset. If you think your plan should include more minutes, contact support — comp minutes can be granted manually per org.
Agent invents things about your company. Voice is grounded in your knowledge base the same way text is, so missing facts usually mean the KB has no entry covering that topic yet. Add an “About” entry in Knowledge base describing what your company does, and re-test. Voice sessions always prime with an about/products summary at connect time, so improvements take effect on the next call.
Microphone blocked. The browser denied mic access. The visitor needs to grant permission in their browser settings and try again.
Mobile layout feels cramped. Hybrid and Strip auto-promote to Takeover under 480px. If the layout looks wrong at desktop widths, use the Desktop/Mobile toggle inside Try voice live on the Customize page to inspect both.