Website grounding
Train from your MkDocs pages as sources.
Integration
Connect MkDocs
Connect MkDocs when chats need follow-up.
- Ready in five minutes
- Built for small businesses
- Human handoff
Common outcomes
- Docs portals
- Internal wikis
- Developer onboarding
- Support deflection
Works with
- Knowledge base
- Embeds
- Analytics
- Models
Context
Why it matters
The practical reason to use it.
Connect InsertChat to the tools your business already uses. It answers from your pages, documents, policies, and product information, then passes conversations to your team when needed.
Start with one common customer question, test the answer and handoff, then expand once the workflow is working well.
How it works
How it works
A step-by-step look at the workflow.
- Step 1
Connect the integration and decide which pages or workflows should stay in scope.
- Step 2
Ground the assistant in your content so it can answer with the same source of truth your team uses.
- Step 3
Define the handoff and access rules that keep the workflow controlled once the conversation gets complex.
- Step 4
Review the questions and improve the setup until the deployment is reliable enough to expand.
Coverage
Connected data
Ground responses in the docs you publish and maintain.
Embeds
Deploy a branded widget on docs pages.
Files support
Include PDFs and resources when needed.
Visibility
See what people ask and fill gaps.
Coverage
Chat follow-up
Refresh sources and tune assistants based on real questions.
Freshness
Refresh sources as docs change.
Assistant controls
Tune prompts and tools per assistant.
Multi-model
Choose models per chat in one assistant setup.
Scope control
Keep data scoped per workspace and assistant.
Coverage
Access rules
A dependable mkdocs rollout needs clear ownership, current context, and a review loop that keeps the workflow useful after launch.
Operational ownership
MkDocs works better when every automated path has a visible owner, a clear escalation boundary, and an explicit definition of the context required before the next step runs.
System-specific context
Connect MkDocs to knowledge base so the assistant uses current state instead of leaving the team to reconstruct missing details after the conversation.
Bounded rollout
Start with docs portals, prove the workflow under real traffic, and expand into internal wikis only after the permissions and handoff rules are dependable.
Review loop
Review conversations that touched embeds, inspect where the workflow stopped, and tighten the setup until mkdocs stays predictable outside ideal demos.
Outcomes
What you get
The first improvements you should notice.
- Fewer manual steps in common workflows
- Faster handoffs with the right context attached
- Less tool switching across conversations
- More consistent outcomes per assistant
Product details
See what is included
Review current plan details, product capabilities, and verified customer reviews.
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.
Training runs on your sitemap, PDFs, docs, and YouTube transcripts. Answers cite the source pages they came from.
Five clients at $300/mo on a $198/mo Agency plan is $1,300+ of monthly margin before usage.
Questions and answers
Common questions
Practical answers about connect mkdocs.
How do we roll this out safely?
Start with one page or workflow, connect the content that already answers the common questions, and keep the handoff rules tight. That gives you a controlled first deployment and a clear baseline for what the integration is improving.
What should the integration connect to first?
Connect the pages, docs, and policies that hold the answers users already expect. Once the assistant starts from a clear source of truth, the rest of the workflow becomes easier to manage and easier to trust.
Can the assistant hand off to a human?
Yes. The integration should preserve context so a human can take over without asking the same questions again. That keeps the customer experience smooth and keeps internal workflows from getting duplicated.
How do we know it is working?
Look for fewer repetitive questions, cleaner handoffs, and better coverage of the pages or workflows you connected. If the widget still depends on manual follow-up for routine questions, the rollout needs another tuning pass.
Related resources
Explore related resources
Mixmax
The #1 Sales Engagement Platform for Gmail. Mixmax provides email tracking, scheduling, sequences, and productivity tools for sales teams.
Mixpanel
Mixpanel is a product analytics platform tracking user interactions and engagement, providing cohort analysis, funnels, and A/B testing to improve user experiences
Mocean
Mocean enables SMS, voice, and verification services, integrating messaging capabilities into applications for multifactor authentication or customer engagement
Moco
MOCO is a business management software offering project management, time tracking, and invoicing solutions.
More integrations
Browse more integrations related to MkDocs AI chat widget.
Explore AI tools
Find tool-enabled workflows that connect assistant conversations to useful actions.
Compare AI models
Review model choices available for different quality, speed, and workflow needs.
Compare alternatives
Evaluate InsertChat against other platforms using consistent product criteria.
Read the AI glossary
Understand the concepts behind assistants, retrieval, models, and automation.
Explore InsertChat features
Review the capabilities available for grounded answers, lead capture, handoff, and automation.
Ready to get started?
Paste your website, test the answers, and launch in five minutes. Start with the website assistant or set up a receptionist for your calls.