Let visitors ask website questions out loud
Use owned content to answer visitor questions with less friction.
7-day free trial
What this feature covers
Why it matters
The practical reason to use it.
Voice is useful when typing is the barrier between a visitor and the answer your website already has.
How it works
A step-by-step look at the workflow.
Step 1
Choose the assistants and pages where speaking is likely to reduce friction, such as mobile product discovery, public information, or support-heavy journeys.
Step 2
Enable spoken input and, where useful, spoken output while keeping the same approved source rules and answer boundaries.
Step 3
Set greeting copy and response style so visitors know what kinds of questions the voice experience can handle.
Step 4
Review conversations to see whether voice improves completion, causes unclear requests, or needs a different handoff path.
Core job
The main job this feature handles.
Voice input
Let visitors ask longer or more natural questions without typing them into a small field.
Audio replies
Return spoken answers when listening is more useful than reading, while keeping citations and text available where needed.
Assistant-level control
Enable voice only for the branded assistants, pages, and visitor journeys that benefit from it.
Same launch paths
Use voice inside the same widget, embed, or hosted assistant experience instead of building a separate voice product.
Daily use
How teams use it after launch.
Start with one bounded workflow
Use Voice on the narrowest workflow where the team can measure whether the feature reduces friction, improves clarity, and creates lower friction.
Keep edge cases visible
Review the conversations, prompts, and system actions tied to voice so operators can see where the rollout still depends on manual judgment.
Connect the surrounding systems
Voice is stronger when the feature sits beside the knowledge, integrations, and routing rules that already determine what happens after the first.
Expand after the first proof
Once the first deployment is stable, teams can extend voice into more surfaces and assistants without rebuilding the same control model from.
Control points
What to keep controlled.
Review real visitor conversations
Use real conversation data to inspect whether voice is actually improving answer quality, reducing back-and-forth, and creating more natural discovery for long.
Check ownership and controls
Look at which team owns the feature, where approvals still matter, and how the capability interacts with surrounding systems.
Track downstream changes
A strong rollout shows up after the first response too: cleaner handoff, clearer escalation, less manual cleanup, and faster next-step execution.
Expand with evidence
Only widen the rollout after the first bounded workflow is clearly stable.
What you get
The changes teams should notice first.
- Lower friction for mobile and accessibility-sensitive visitors
- More natural discovery for long or detailed questions
- Consistent answers because voice uses the same approved sources
- Clearer rollout control by enabling voice only where it helps
The facts do the selling
Plan facts, platform capabilities, and worked examples — every claim here is checkable, not a pitch.
White-label included — never a paid add-on. Copyright removal from $98/mo. Full white-label — custom domain, branded portal, your-domain emails — from $198/mo.
The white-label wedge
Platform fact
Training runs on your sitemap, PDFs, docs, and YouTube transcripts. Answers cite the source pages they came from.
Trained on your content
Platform fact
Five clients at $300/mo on a $198/mo Agency plan is $1,300+ of monthly margin before usage.
A 5-client agency on one flat plan
Worked example
Your questions, answered.
Tap any question about the product, pricing, security, or setup to see a straight answer.
InsertChat
Answers about InsertChat
Hi! Tap any question below and I'll answer it for you.
Voice questions
Can I enable voice only for specific assistants?
Yes. Voice should stay scoped to the assistants and launch paths where it improves visitor access. You can keep other website assistants text-based if typing is clearer, faster, or easier to review. The operational question is whether voice makes the workflow clearer once real conversations, real ownership, and real edge cases show up. That is the bar teams should use before they expand the rollout across more assistants, more channels, or more teams.
Does voice help accessibility?
Yes. Spoken input and audio replies can help visitors who prefer speaking, are on mobile, or have difficulty typing long questions. Your team should still review source quality and answer clarity because accessibility depends on reliable content, not only audio. The operational question is whether voice makes the workflow clearer once real conversations, real ownership, and real edge cases show up. That is the bar teams should use before they expand the rollout across more assistants, more channels, or more teams.
When should I avoid voice?
Avoid voice when visitors need to compare dense details, review citations carefully, or enter sensitive information in a public setting. A text-based assistant or human handoff may be a better path for those conversations. The operational question is whether voice makes the workflow clearer once real conversations, real ownership, and real edge cases show up. That is the bar teams should use before they expand the rollout across more assistants, more channels, or more teams.
Ready to get started?
Start your 7-day free trial. Review current trial terms.
7-day free trial