> ## Knowledge Base Index > Fetch the complete knowledge base index at: https://help.crisp.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 *Learn how SaaS teams can set up Crisp for onboarding, product questions, billing conversations, and long-term customer support.* SaaS teams usually need more than a basic live chat. Sales, support, onboarding, and customer success all need shared context, reliable product knowledge, clean routing, and a way to bring account data into support conversations. Crisp works especially well here because the Inbox, knowledge base, routing, customer data, workflows, and Hugo can live in the same environment. --- # ${color}[#0080dd](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. __Crisp can help SaaS teams:__ * **Support trials and paying customers in one place** → keep onboarding, sales, billing, and product support conversations together * **Bring account context into the Inbox** → sync plan, lifecycle stage, usage signals, product area, 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, success, and escalation flows without splitting tools * **Automate repeated requests** → use workflows and Hugo for frequent questions, qualification, and handoff * **Help operators reply faster** → use shortcuts, internal notes, knowledge articles, AI Tools, and Copilot when available This foundation is useful whether your company is still handling founder-led support or already works with separate sales, success, and support teams. --- # ${color}[#0080dd](Recommended setup) A good SaaS setup usually starts with channels and customer context, then moves into knowledge, routing, and automation. Most configuration starts from [**Crisp**](https://app.crisp.chat). #### ${color}[#445055](Install Crisp where users need help) Install the Crisp chatbox on the pages or product areas where customers are most likely to need help. For SaaS companies, this often includes the marketing website, pricing page, onboarding flows, dashboard, billing area, and help or documentation pages. You can copy the chatbox script from **Settings → Workspace Settings → Setup & Integrations → Chatbox setup instructions**. If your app uses a framework or CMS, use the platform-specific installation guide instead of pasting the generic snippet blindly. __Useful setup resources:__ * [How to install the Crisp live-chat chatbox on my website](/en/article/how-do-i-add-a-live-chat-to-my-website-10wcj3l/) * [Crisp Web SDK](https://docs.crisp.chat/guides/chatbox-sdks/web-sdk/dollar-crisp/) * [Crisp REST API quickstart](https://docs.crisp.chat/guides/rest-api/quickstart/) #### ${color}[#445055](Connect support email and key channels) Most SaaS teams need a shared support email even if chat is the main contact channel. Forwarding support emails into Crisp keeps chat, email, and social conversations in the same Inbox, with the same assignment, notes, history, and customer context. Depending on your audience, you can also connect channels such as Messenger, WhatsApp, Instagram, X, Line, or SMS. Start with the channels your customers already use rather than trying to connect everything at once. __Helpful guides:__ * [How to receive emails in Crisp](/en/article/how-to-receive-emails-in-crisp-wp7jug/) * [How to link your Facebook Messenger pages to Crisp](/en/article/how-to-link-your-facebook-messenger-pages-to-crisp-1gbgm9d/) * [Connect WhatsApp Business Platform with Crisp](/en/article/connect-whatsapp-business-platform-with-crisp-11rcwkw/) * [How to link Crisp with Instagram DM](/en/article/how-to-link-crisp-with-instagram-dm-14xg8xl/) #### ${color}[#445055](Sync customer and product data) Account context is one of the biggest differences between basic chat support and strong SaaS support. If agents can see the customer's plan, trial status, company, usage signals, billing state, or product area, they can answer more accurately and route faster. __Useful data points often include:__ * **Plan and billing state** → free, trial, paid, enterprise, past due, canceled, or renewal date * **Lifecycle stage** → lead, trial, onboarding, active customer, churn risk, or VIP * **Product usage** → feature usage, last login, workspace size, limits, or activation status * **Ownership** → account manager, success manager, support tier, or region * **Technical context** → app version, browser, platform, integration status, or workspace ID You can synchronize this through the **Web SDK**, **REST API**, **Segment**, integrations, or CSV import depending on your stack. __Helpful guides:__ * [How can I automatically set custom data?](/en/article/how-can-i-automatically-set-custom-data-1xh7pqk/) * [How can I automatically set user segments?](/en/article/how-can-i-automatically-set-user-segments-oerdox/) * [How to import my user data](/en/article/how-to-import-my-user-data-dcukz8/) * [How to Connect Segment.com with Crisp](/en/article/how-to-connect-crisp-with-segmentcom-jthlv7/) #### ${color}[#445055](Build a knowledge base for product and policy answers) A SaaS knowledge base should answer what customers repeatedly ask during discovery, onboarding, daily usage, and troubleshooting. It also becomes a strong training source for Hugo and a fast resource for agents to share directly from the Inbox. __Good first article categories include:__ * **Getting started** → installation, onboarding, first setup, and recommended workflows * **Account and billing** → invoices, plan limits, payment issues, upgrades, cancellation, and refunds * **Product usage** → core features, permissions, roles, integrations, and settings * **Troubleshooting** → common errors, unsupported cases, known limitations, and diagnostic steps * **Policies and expectations** → SLAs, security, privacy, support scope, and escalation paths Start with the top repeated questions instead of trying to document the entire product immediately. A smaller but accurate knowledge base is more useful than a large one with outdated articles. __Helpful resources:__ * [Crisp Knowledge Base](https://crisp.chat/en/knowledge/) * [How to use the Knowledge Base](/en/article/how-to-use-the-knowledge-base-i2tsm1/) * [How can I import my knowledge base from a previous provider?](/en/article/how-can-i-import-my-helpdesk-from-a-previous-provider-rpa7tv/) #### ${color}[#445055](Use routing and sub-inboxes for ownership) As soon as several teams share the same workspace, ownership needs to be explicit. Routing and sub-inboxes help you separate sales, support, success, billing, partnerships, and technical escalation without losing conversation history. __Common SaaS routing patterns include:__ * **Sales vs support** → demo requests and buying questions separated from product support * **Billing** → payment failures, invoices, plan limits, and refund questions sent to the right team * **Technical escalation** → bugs, incidents, API issues, and integration problems routed with context * **VIP or enterprise support** → high-priority customers handled by a specific group * **Language or region** → distributed teams handling conversations by geography or locale __Helpful guides:__ * [How does Operator routing & assignation work?](/en/article/how-does-operator-routing-assignation-work-qjl2d2/) * [How to create and use sub-inboxes](/en/article/how-to-create-and-use-sub-inboxes-ke3xk7/) * [How do I create a department routing Chatbot?](/en/article/how-do-i-create-a-department-routing-chatbot-11f6pij/) #### ${color}[#445055](Deploy Hugo and workflows progressively) Hugo can answer repetitive questions, route conversations, and use integrations when configured. For SaaS teams, it is especially useful when trained on product documentation, policies, pricing explanations, onboarding content, and troubleshooting articles. Workflows are useful when the conversation needs structure before or after the AI answer, such as collecting a workspace ID, asking for the product area, qualifying a demo request, or routing a billing issue. __Good first SaaS automations include:__ * **Onboarding help** → answer setup questions and send users to the right next step * **Demo qualification** → collect company size, use case, timeline, and contact details before handoff * **Billing triage** → identify invoice, plan, payment, or cancellation questions early * **Bug report intake** → collect environment, steps to reproduce, screenshots, and account context * **After-hours support** → answer documented questions and route urgent cases to the right process __Helpful resources:__ * [Getting started with Hugo AI Agent](/en/article/getting-started-with-hugo-ai-agent-w6gbux/) * [How to train Hugo AI Agent on your data](/en/article/how-to-train-hugo-ai-agent-on-your-data-ijkdrl/) * [Getting started with Workflows](/en/article/getting-started-with-workflows-hrmysb/) * [How to build MCP integrations with Hugo](/en/article/how-to-build-mcp-integrations-with-hugo-tlrqmn/) --- # ${color}[#0080dd](Daily habits for SaaS support) Once the setup is live, day-to-day quality depends on consistent operating habits. The goal is to reduce context loss, keep answers reliable, and make escalations easier for the next person. __Simple habits that help a lot:__ * **Use shortcuts for repeated phrasing** → keep common answers fast and consistent * **Share knowledge articles** → send durable answers instead of rewriting everything from scratch * **Use private notes for context** → explain what happened before mentioning or assigning a teammate * **Keep customer data updated** → routing, prioritization, and AI answers improve when context is accurate * **Review repeated questions** → turn them into knowledge base articles, Q&A snippets, or workflows * **Escalate with useful details** → include customer goal, plan, workspace ID, issue summary, and what was already tried ${youtube}[Tilkee's testimonial](xCwa_k90nvY) --- # ${color}[#0080dd](Next steps) A strong SaaS setup usually improves in layers: install the chatbox, centralize channels, sync customer data, publish knowledge, configure routing, then add Hugo and workflows once the foundations are clean. __Helpful resources to continue:__ * [Getting Started With Crisp for Customer Support](/en/article/getting-started-with-crisp-for-customer-support-1ts8txn/) * [Getting started with AI for customer service at Crisp](/en/article/getting-started-with-ai-for-customer-service-at-crisp-j6xa76/) * [Crisp Shared Inbox](https://crisp.chat/en/shared-inbox/) * [Crisp CRM](https://crisp.chat/en/crm/) * [Crisp AI](https://crisp.chat/en/ai/)