> ## Knowledge Base Index > Fetch the complete knowledge base index at: https://help.chrisp.chat/sitemap.xml > Use this file to discover available pages before exploring further. > Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash). # Getting started for the SaaS industry __This guide helps SaaS companies get started with Crisp around onboarding, product questions, billing conversations, and long-term customer support.__ SaaS teams usually need more than a basic live chat. You need a place where sales, support, onboarding, and customer success can share context, route conversations cleanly, and respond with reliable product knowledge. Crisp works especially well here because it combines the inbox, knowledge base, routing, customer data, and Hugo in the same environment. --- # SaaS at a glance For SaaS companies, Crisp is most useful when it helps your team answer product questions faster and gives each conversation enough context to avoid back-and-forth. __What Crisp can help you do:__ * ****Support trials and paying customers in one place**** → keep onboarding, sales, and support conversations in the same workspace * ****Bring account context into the inbox**** → sync plan, lifecycle stage, usage signals, or customer metadata * ****Make product knowledge easier to reuse**** → publish a knowledge base and share articles directly from conversations * ****Separate ownership cleanly**** → route sales, billing, support, and escalation flows without splitting tools * ****Scale with AI**** → train Hugo on your product and let agents use Copilot and AI writing tools when needed --- # Recommended setup A strong SaaS setup usually starts with customer context and product knowledge, then adds routing and AI once the underlying information is solid. Most of the steps below start from [Crisp](https://app.crisp.chat). #### Install the widget where product questions happen Start with the Crisp widget on the pages where prospects and customers actually need help: your marketing site, app, docs, billing pages, onboarding flows, and help center. You can retrieve the installation code from ****Settings → Workspace Settings → Setup & Integrations****. That gives your team one consistent entry point for sales questions, trial friction, and support requests. __Useful starting points:__ * ****Website widget**** → [Live chat widget](https://crisp.chat/en/livechat/) * ****Installation guide**** → [How do I add a live chat to my website?](https://help.crisp.chat/en/article/how-do-i-add-a-live-chat-to-my-website-10wcj3l/) * ****Web SDK**** → [How do I use the $crisp chatbox SDK?](https://help.crisp.chat/en/article/how-do-i-use-the-crisp-chatbox-sdk-1lp254r/) #### Connect account and subscription context Being able to identify who is writing matters a lot in SaaS. Your team usually needs to know whether the user is on trial, which plan they have, which workspace they belong to, or whether they are already affected by a billing or technical issue. Crisp can receive that information through imports, APIs, or integrations, which makes routing and personalized replies much easier. __Common context to sync first:__ * ****Plan and subscription status**** → useful for billing and entitlement questions * ****Workspace or company details**** → important when several users belong to the same customer account * ****Lifecycle stage**** → lead, trial, active customer, churn risk, or enterprise prospect * ****Product usage signals**** → helpful when support depends on what the user has already done __Helpful guides:__ * ****Import contacts**** → [How to import my user data](https://help.crisp.chat/en/article/how-to-import-my-user-data-dcukz8/) * ****REST API quickstart**** → [Developer Hub](https://docs.crisp.chat/guides/rest-api/quickstart/) * ****Segment integration**** → [Segment for Crisp](https://crisp.chat/en/integrations/segment/) #### Build a knowledge base for onboarding and troubleshooting A SaaS knowledge base is valuable both for customer self-service and for team consistency. It gives sales and support one reliable source to reuse during conversations, and it also becomes one of the best training sources for Hugo. __The best first articles usually cover:__ * ****Getting started and onboarding**** → account setup, installation, first steps, and common blockers * ****Billing and subscriptions**** → invoices, plan changes, cancellations, and renewals * ****Core troubleshooting**** → the issues your team solves every week * ****Integrations and technical setup**** → important when adoption depends on connecting other tools * ****Status or incident information**** → useful when customers need reassurance during outages __Helpful guides:__ * ****Knowledge Base**** → [Crisp Knowledge Base](https://crisp.chat/en/knowledge/) * ****Import existing content**** → [How can I import my helpdesk from a previous provider?](https://help.crisp.chat/en/article/how-can-i-import-my-helpdesk-from-a-previous-provider-rpa7tv/) * ****Status Page**** → [Crisp Status Page](https://crisp.chat/en/status/) #### Separate sales, support, billing, and success flows As soon as volume grows, routing starts to matter. SaaS teams often handle very different conversations in the same inbox: demo requests, bug reports, plan changes, onboarding help, enterprise questions, or incident follow-up. Crisp can separate those flows with routing rules, workflows, and sub-inboxes without forcing you to run separate tools for each team. __Useful guides:__ * ****Routing and assignment**** → [How does Routing / Assign work?](https://help.crisp.chat/en/article/how-does-routing-assign-work-qjl2d2/) * ****Department routing**** → [How do I create a department routing chatbot?](https://help.crisp.chat/en/article/how-do-i-create-a-department-routing-chatbot-11f6pij/) * ****Sub-inboxes**** → [How can I create sub-inboxes in my Crisp workspace?](https://help.crisp.chat/en/article/how-can-i-create-sub-inboxes-in-my-crisp-workspace-ke3xk7/) #### Add Hugo for repetitive product questions Hugo is especially useful in SaaS when a large share of incoming requests are already documented somewhere: setup questions, feature availability, billing basics, account steps, or troubleshooting guidance. The relevant setup lives under ****AI Agent****. Train it on your product pages, docs, knowledge base, and internal Q&A snippets first. Then let your team use ****Copilot**** and the inbox ****AI Tools**** to move even faster on the conversations that still need human review. __Useful guides:__ * ****Hugo setup**** → [Getting started with Hugo AI Agent](https://help.crisp.chat/en/article/getting-started-with-hugo-ai-agent-w6gbux/) * ****Training**** → [How to train Hugo AI Agent on your data](https://help.crisp.chat/en/article/how-to-train-hugo-ai-agent-on-your-data-ijkdrl/) * ****AI overview**** → [Crisp AI](https://crisp.chat/en/ai/) #### Add integrations when you want Hugo to use live data For SaaS companies, the biggest AI step often comes when Hugo can do more than answer documentation-based questions. With native integrations or MCP servers, Hugo can retrieve live information from your systems when the situation requires it. That is what makes use cases such as checking subscriptions, retrieving invoices, or looking up workspace details much more valuable. __Useful guides:__ * ****Native Hugo integrations**** → [How to use Hugo Integrations](https://help.crisp.chat/en/article/how-to-use-hugo-integrations-6z9yhh/) * ****Custom MCP**** → [How to build MCP integrations with Hugo](https://help.crisp.chat/en/article/how-to-build-mcp-integrations-with-hugo-tlrqmn/) --- # Common SaaS workflows to launch first Once the foundations are in place, a few workflows usually create value quickly. __Good first workflows for SaaS teams:__ * ****Trial and demo qualification**** → collect the right information before a sales handoff * ****Billing and subscription routing**** → separate plan questions from technical support * ****Bug report collection**** → gather the product area, severity, and reproduction details early * ****Onboarding help**** → guide new users toward setup articles, videos, or the right team * ****Incident communication**** → route urgent conversations consistently and point users to your status updates when relevant --- # Next steps The best SaaS support setups keep improving in layers: better customer data first, better knowledge second, better routing third, and deeper AI once the core information is reliable. __Helpful resources:__ * ****Customer support guide**** → [Getting Started With Crisp for Customer Support](https://help.crisp.chat/en/article/getting-started-with-crisp-for-customer-support-1ts8txn/) * ****Hugo**** → [Getting started with Hugo AI Agent](https://help.crisp.chat/en/article/getting-started-with-hugo-ai-agent-w6gbux/) * ****Status Page**** → [Crisp Status Page](https://crisp.chat/en/status/) * ****Workflows**** → [Getting started with Workflows](https://help.crisp.chat/en/article/getting-started-with-workflows-hrmysb/)