> ## Documentation Index
> Fetch the complete documentation index at: https://docs.insitechat.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# SaaS

> Use InsiteChat to reduce churn, deflect repetitive support tickets, and help users onboard themselves — without hiring more agents.

# SaaS

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

<Tip>
  Connect your Notion or Google Drive workspace so your chatbot stays in sync automatically as your docs evolve.
</Tip>

## How to set up InsiteChat for your SaaS

<Steps>
  <Step title="Connect your knowledge base">
    Go to the **Sources** tab and link 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.
  </Step>

  <Step title="Upload your API docs and help articles">
    Upload any documentation not covered by connected sources — API references, PDF guides, internal wikis. Add as many sources as needed.
  </Step>

  <Step title="Add custom q&a for your top support questions">
    Go to the **Q\&A** tab and add entries for questions your team answers most often. Start with your top 10 to 20 "how do I..." questions for precise answer control.
  </Step>

  <Step title="Deploy on your app, docs site, and marketing pages">
    Copy the embed code from the **Embed** tab and add it to each property where users need help. In-app deployment is particularly effective for reducing support during onboarding.
  </Step>

  <Step title="Review conversations to find knowledge gaps">
    Open the **Conversations** tab and review sessions where visitors got unhelpful answers. Add custom Q\&A pairs to fill the gaps.
  </Step>
</Steps>

## What to expect

* **Self-serve onboarding** — new users activate faster without waiting for support
* **Fewer repetitive tickets** — common questions handled automatically
* **Users discover features faster** — chatbot surfaces relevant help content contextually

<Note>
  The analytics dashboard is especially valuable for SaaS teams. Unanswered questions are a direct signal of where your documentation has gaps.
</Note>

## Next steps

<CardGroup cols={3}>
  <Card title="Notion" icon="n" href="/integrations/notion">
    Connect your Notion workspace.
  </Card>

  <Card title="Google drive" icon="google-drive" href="/integrations/google-drive">
    Import from Google Drive.
  </Card>

  <Card title="Analytics" icon="chart-line" href="/managing/analytics">
    Track chatbot performance.
  </Card>
</CardGroup>