Launch the assistant where visitors ask
Use owned content to answer visitor questions with less friction.
7-day free trial · No charge during trial
What this feature covers
Why it matters
The practical reason to use it.
Channels matter because visitor questions do not all happen on the same page.
How it works
A step-by-step look at the workflow.
Step 1
Configure the assistant with approved sources, brand settings, answer rules, and the visitor job it should handle.
Step 2
Choose the launch path that matches the journey: widget for sitewide help, embed for resource hubs, hosted page for focused guides, custom.
Step 3
Keep the same source-backed behavior and analytics as the assistant appears in more places.
Step 4
Compare usage by channel and expand only where visitors ask useful questions or need clearer next steps.
Core job
The main job this feature handles.
Website widget
Add a branded assistant to high-intent pages, support pages, product pages, or resource hubs.
API surface
Bring the same source-backed answers into custom product or website experiences.
Embedded guide
Place the assistant inside a portal, collection, resource center, or guided content page.
Shared controls
Keep prompts, tools, sources, branding, and insight connected across launch paths.
Daily use
How teams use it after launch.
Start with one bounded workflow
Use Channels on the narrowest workflow where the team can measure whether the feature reduces friction, improves clarity, and creates consistent answers.
Keep edge cases visible
Review the conversations, prompts, and system actions tied to channels so operators can see where the rollout still depends on manual judgment.
Connect the surrounding systems
Channels 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 channels 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 channels is actually improving answer quality, reducing back-and-forth, and creating faster launch without rebuilding source.
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.
- Consistent answers across website widget, embed, hosted page, and API
- Faster launch without rebuilding source logic for every surface
- Better visitor coverage for support, product, content, and lead journeys
- Channel-level insight into where questions and handoffs happen
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.
Channels questions
Can one assistant run on multiple channels?
Yes. You can reuse the same approved sources, brand controls, and answer behavior across the widget, embeds, hosted pages, custom domains, and API-backed experiences. The operational question is whether channels 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.
Do all channels share the same knowledge?
Yes. The point is to keep the same assistant behavior and knowledge layer across every launch surface so the website does not end up with conflicting answers. The operational question is whether channels 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 adding another channel?
Avoid expanding channels when the first launch still has weak source coverage, unclear handoff rules, or low-quality visitor questions. Fix the answer path before putting the assistant in more places. The operational question is whether channels 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. No charge during trial.
7-day free trial · No charge during trial