> ## 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 with Crisp for SaaS *Add chat and email support to your SaaS product, show account details in the Inbox, and prepare answers for setup, billing, and technical questions.* Start with a message sent from your app and answered by a teammate. Once that works, add customer identity and Custom Data, publish your recurring answers, then choose a first task for Hugo or Workflows. --- # ${color}[#1575dd](Connect in-app chat and support email) Install chat where customers get stuck, such as onboarding or the billing area. Keep support email available for requests that arrive outside your app. __Connect the two channels:__ 1. In **⚙️ Settings → Workspace Settings → Setup & Integrations → Chatbox setup instructions**, copy the installation script for the workspace that should receive requests. 2. [Install the widget in your product](https://help.crisp.chat/en/article/how-to-install-crisp-live-chat-software-on-a-custom-website-10wcj3l/). For a single-page application, follow the [SPA guide](https://help.crisp.chat/en/article/how-to-install-the-crisp-support-chat-sdk-on-single-page-applications-spa-1ptfyyx/). 3. Send a message from the app and reply from the Crisp Inbox. Confirm that it reaches the intended workspace before adding account data. 4. Open **Settings → Workspace Settings → Setup & Integrations → Email**, copy the incoming address, and [forward your support mailbox](https://help.crisp.chat/en/article/how-to-receive-emails-in-crisp-2zfgvl/) to it. Check an incoming email, an agent reply, and the customer's reply. #### ${color}[#405e80](Identify signed-in customers) Ask your developer to set the signed-in user's [email address](https://help.crisp.chat/en/article/how-to-automatically-set-users-email-addresses-udcs19/) through the SDK. When using Web SDK email verification, send the backend-generated signature in the first email setter call. Use [Session Continuity](https://help.crisp.chat/en/article/how-to-persist-a-single-chatbox-conversation-across-different-devices-browsers-and-apps-1oelweq/) when customers should recover their conversation across supported sessions. Clear the continuity token and reset the Crisp session on logout or expiry, before applying another account's profile. Test account A signing out and account B signing in on the same browser. Account B must see its own identity and conversation context. For an SPA, also check a normal in-app route change. --- # ${color}[#1575dd](Show account details in the Inbox) Use [Custom Data](https://help.crisp.chat/en/article/getting-started-with-custom-datas-43jgi3/) for details agents need to investigate a request. Choose fields that save a question or help the agent find the right record. __Useful SaaS fields include:__ * **Account ID:** find the customer in your internal tools. * **Plan:** choose instructions that apply to the customer's subscription. * **App version:** investigate a reported error. * **Product area:** identify where setup or usage has stopped. Send these values through the [Web SDK](https://help.crisp.chat/en/article/how-to-automatically-push-custom-data-from-the-chatbox-with-the-crisp-js-sdk-1xh7pqk/) or an integration. A [contact import](https://help.crisp.chat/en/article/how-to-import-contact-profiles-dcukz8/) can supply a starting list, but changing values such as plan and app version need ongoing updates. Use [Segments](https://help.crisp.chat/en/article/getting-started-with-segments-88hhzw/) for simple labels such as `trial` or `enterprise`. For example, a `trial` segment can identify customers who may need onboarding help. ![A test SaaS conversation with the identified customer and account ID, plan, and app version visible in the sidebar](https://screenshots.invalid/a-test-saas-conversation-with-the-identified-customer-and-account-id-plan-and-app-version-visible-in-the-sidebar-illustrating-the-context-an-agent-receives-before-investigating.png =1000xauto) --- # ${color}[#1575dd](Publish setup answers and organize your team) Write the answers customers need most often before automating them. Start with a setup task, a billing question, and a common error. __Publish your first answer:__ 1. Open **Knowledge Base** and create it with a name and help-center address if needed. 2. Select the intended language and click **New Article**. Include the requirements, actual steps, and result the customer should expect. 3. Preview and publish the article. Saving alone does not make it public. 4. Share it in a support conversation and check whether the customer can finish the task without additional instructions. The [Knowledge Base setup guide](https://help.crisp.chat/en/article/getting-started-with-the-crisp-knowledge-base-i2tsm1/) covers categories, languages, and the public site. Use [assignment](https://help.crisp.chat/en/article/how-to-route-and-assign-conversations-to-operators-bv8z4c/) to give each request an owner. Add [sub-inboxes](https://help.crisp.chat/en/article/how-to-create-and-manage-sub-inboxes-in-crisp-ke3xk7/) when sales, billing, or technical support needs a separate queue. Decide who handles an account-specific decision before automating its intake. --- # ${color}[#1575dd](Choose a first task for Hugo or Workflows) Use **Hugo** for questions answered in your documentation. Use a **Workflow** when the request needs a fixed set of questions before a teammate can act. For Hugo, open **AI Agent → Train** to review its sources. Set behavior in **AI Agent → Guidance → Instructions** and handoffs in **Guidance → Routing**. Follow the [Hugo setup guide](https://help.crisp.chat/en/article/getting-started-with-hugo-ai-agent-w6gbux/) for activation and budget settings. For a bug report, [create a Workflow](https://help.crisp.chat/en/article/getting-started-with-workflows-hrmysb/) that collects what the customer expected, what happened, and the reproduction steps. Include the workspace ID and app version in the technical handoff so the next teammate can investigate. Test a documented setup question and a case requiring a person in **AI Agent → Evaluate → Playground**. After activation, repeat the handoff in a controlled live conversation and check that the receiving teammate sees the request and account context. Check the [current plan features](https://crisp.chat/en/pricing/) for the channels, Knowledge Base, and automation you want to use.