Skip to main content
InsiteChat lets SaaS teams turn their existing documentation into a self-serve support layer. Train it on your help center, API docs, and onboarding guides, then deploy it across your app, docs site, and marketing pages. Users find answers on their own instead of opening tickets.

​
Problems InsiteChat solves for SaaS teams

Users churn because they get stuck. New users hit a wall during setup, can’t find the answer in your docs, and cancel before they see the value of your product. Support tickets grow faster than headcount. Every new customer adds to the queue. Hiring to keep up is expensive and doesn’t scale. Onboarding is manual and creates bottlenecks. Your team walks users through the same setup steps repeatedly. It takes time and limits how fast you can grow. Help docs go unread. You’ve written hundreds of articles, but users still open tickets for questions that are already answered. They don’t know where to look.

​
What to train your chatbot on

Start with the content your support team uses most often to answer questions:
  • Help center and knowledge base articles — your primary source of truth for how your product works
  • API documentation — especially if developers are part of your user base
  • Onboarding guides — step-by-step setup instructions and getting-started walkthroughs
  • Changelog and feature announcements — helps users discover new functionality
  • Custom Q&A — precise answers to your most common “how do I…” questions
Connect your Notion or Google Drive workspace so your chatbot stays in sync automatically as your docs evolve. You don’t need to re-upload content manually after each update.

​
How to set up InsiteChat for your SaaS

1

Connect your knowledge base

Go to Sources in your dashboard and connect Notion, Google Drive, or use the website crawler to index your help center or docs site. InsiteChat syncs on a schedule so your chatbot stays current.
2

Upload your API docs and help articles

Upload any documentation that isn’t covered by your connected sources — API references, PDF guides, internal wikis. Add as many sources as you need.
3

Add custom Q&A for your top support questions

Open Custom Q&A and add entries for the questions your team answers most often. Start with your top 10 to 20 “how do I…” questions. These give you precise control over the answer the chatbot provides.
4

Deploy on your app, docs site, and marketing pages

Copy the embed snippet from Deployment and add it to each property where users need help. Deploying on your in-app pages is particularly effective for reducing support during onboarding.
5

Review analytics weekly to find knowledge gaps

Open the Analytics tab and check the unanswered questions report. Each entry shows a real question a user asked that your chatbot couldn’t answer. Use these to add new content or custom Q&A pairs.

​
What to expect

  • Self-serve onboarding — new users activate faster without waiting for a support rep to walk them through setup
  • Fewer repetitive tickets — common “how do I…” questions are handled automatically, so your team focuses on complex, high-value conversations
  • Users discover features faster — because the chatbot surfaces relevant help content in the context of what users are trying to do
The analytics dashboard is especially valuable for SaaS teams. Unanswered questions are a direct signal of where your documentation has gaps — review them regularly and your chatbot improves over time.

​
Next steps

Notion integration

Sync your Notion workspace as a knowledge source.

Google Drive integration

Connect Google Drive folders to your chatbot.

Analytics

Track performance and find gaps in your knowledge base.