Build a branded assistant visitors can trust
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.
The assistant builder is where a question-heavy website becomes easier to ask.
How it works
A step-by-step look at the workflow.
Step 1
Choose the visitor questions the assistant should handle first and connect the approved website pages, documents, videos, or product information that answer.
Step 2
Set the brand voice, greeting, suggested prompts, source rules, and fallback behavior so the assistant knows how to respond when it has.
Step 3
Enable next-step paths only where they help, such as lead capture, support handoff, booking, or tool lookup for a specific visitor intent.
Step 4
Launch on a controlled page, review conversations, then add missing sources and tighter prompts before expanding the assistant across more of the.
Core job
The main job this feature handles.
Behavior rules
Set answer style, refusal behavior, and escalation guidance around the visitor job the assistant owns.
Suggested questions
Offer prompts that point visitors toward useful content, product answers, support paths, or buying next steps.
Conversation context
Keep the thread coherent so follow-up questions refer back to the same visitor need and source-backed answer.
Model profile
Choose the model setup behind the assistant without making model choice visible as the main visitor experience.
Next-step tools
Enable lead capture, booking, support handoff, ecommerce lookup, or search only where the visitor journey needs it.
Visitor insight
Review questions, unanswered topics, source gaps, and lead signals after launch.
Daily use
How teams use it after launch.
Visual fit
Match colors, logo, launcher placement, and chat layout to the page where visitors ask.
Audience fit
Tune copy for readers, shoppers, members, prospects, students, or support visitors.
Conversation review
Inspect chats so content, support, and digital teams can improve weak answers.
Metadata and routing
Attach page, source, intent, and visitor context when the conversation becomes a handoff.
Control points
What to keep controlled.
Workspace roles
Assign roles like owner, admin, manager, or client.
Assistant assignments
Grant access to specific assistants per teammate.
Privacy controls
Keep data isolated per workspace and assistant.
What you get
The changes teams should notice first.
- Source-backed answers on the pages where visitors need help
- A branded assistant that follows approved tone and behavior
- Cleaner lead and support handoff with the original question preserved
- Sharper content priorities from unanswered visitor questions
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.
Approved sources questions
What should I connect before launch?
Start with sources that already answer high-value visitor questions: core website pages, FAQs, policy pages, product information, support articles, guides, videos, and documents. A narrow source set is usually better than connecting everything before your team knows what visitors ask. The operational question is whether approved sources 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 is this feature a bad fit?
It is a bad fit if the business does not have approved content, cannot name the visitor questions it wants to answer, or expects the assistant to invent policy, pricing, product, or support guidance. In that case, document the source material first. The operational question is whether approved sources 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.
How does the assistant hand off to a person?
You can enable capture and routing paths when a visitor asks for pricing, booking, support, contact, or other follow-up. The handoff keeps the conversation context so the person receiving it can see what the visitor asked and what the assistant already answered. The operational question is whether approved sources 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