Turn visitor questions into handoffs
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.
Workflows make the assistant useful after a source-backed answer.
How it works
A step-by-step look at the workflow.
Step 1
Choose the visitor outcome you want, such as a qualified lead, booked meeting, support ticket, product lookup, or human review.
Step 2
Enable the tool, integration, or webhook that should run when the conversation reaches that outcome.
Step 3
Pass contact details, source page, transcript, intent, and relevant metadata into the destination system.
Step 4
Review handoff quality and refine routing rules before adding more paths or systems.
Core job
The main job this feature handles.
Lead capture
Collect contact details in context and hand qualified leads to the team or CRM without forcing visitors through a separate form flow.
Booking paths
Move from interest to scheduled next step inside the conversation when a meeting, demo, or service slot is the desired outcome.
Human handoff
Route complex or sensitive conversations to a person instead of pretending the bot can or should finish every interaction alone.
Resolution status
Mark chats resolved or hand them into a follow-up path so AI activity maps cleanly to the operational outcome your team tracks.
Daily use
How teams use it after launch.
Real-time webhooks
Push events to your backend as chats happen so downstream systems can respond immediately rather than waiting on manual exports.
Ticketing and CRM sync
Create or enrich records in helpdesk and CRM tools when a conversation reaches the point where human follow-up matters.
Lookup tools
Answer with current operational context by querying commerce, shipping, search, or platform data during the conversation.
Custom backend automation
Pair webhooks with the API when the handoff needs custom validation, proprietary business logic, or system updates.
Control points
What to keep controlled.
What you get
The changes teams should notice first.
- More conversations converted into booked meetings, leads, or resolved outcomes
- Less manual copy-paste between chat, CRM, support, and operational systems
- Faster handoff from the assistant to humans when a conversation needs real ownership
- Clearer next steps without building a separate orchestration layer first
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.
Workflows questions
Can workflows trigger external systems?
Yes. You can use webhooks, integrations, and built-in actions to send approved conversation outcomes into the CRM, helpdesk, calendar, ecommerce, or backend systems your team already uses. The operational question is whether workflows 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 I need a separate automation stack?
No. Many teams can start with InsertChat tools, integrations, and webhooks. Use a separate automation system only when the handoff needs custom validation, enrichment, or routing logic. The operational question is whether workflows 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.
Can I use workflows for support and sales?
Yes. The same handoff model can route support issues, capture leads, book meetings, or send product context depending on the assistant, page, and visitor intent. The operational question is whether workflows 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