> ## 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 the Essentials plan __This guide helps you roll out the Essentials plan in a structured way, so you can unlock the main value of Crisp without getting lost in all the new possibilities.__ Essentials is where Crisp becomes a full-featured support platform. It adds ****10 seats****, more included ****Hugo credits****, ****customer data management****, ****omnichannel inbox channels****, the ****workflow automation builder****, the ****AI chatbot builder****, ****knowledge base****, ****analytics****, and ****routing rules****. If Mini helps you professionalize support, Essentials is where you start designing a real operating model around it. | The ****Essentials**** plan includes everything from the ****Free**** and ****Mini**** plans, plus the additional features listed below. --- # Essentials plan features | Essentials includes ****$25 of Hugo credits****, which Crisp estimates at around ****450 automated conversations per month****. __Main features unlocked:__ * ****10 seats included**** → scale your team without changing plan immediately * ****Customer data management**** → centralize and use customer information in Crisp * ****Omnichannel inbox**** → connect channels like ****WhatsApp Business****, ****Instagram****, ****SMS****, ****Line****, ****Viber****, and more * ****Workflow automation builder**** → build no-code workflows and automation paths * ****Omnichannel AI chatbot**** → create AI-powered automated flows * ****Knowledge base**** → publish self-service help content * ****Analytics**** → track activity, customer satisfaction, and team performance * ****Routing rules and assignment**** → automatically assign or route conversations * ****More Hugo credits**** → move from experimentation to a more operational AI setup --- # Recommended setup #### Teammates and workspace structure Essentials includes ****10 seats****, so this is usually the right time to onboard your whole support team and clarify who owns what. Invite operators from [**Crisp**](https://app.crisp.chat) via ****Settings → Workspace Settings → Operators and Teams****, then decide how your team will split channel ownership, shifts, and escalation rules. | You can use [this invite guide](/en/article/how-do-i-invite-other-agents-to-my-inbox-1rsgzkh/) and share [this onboarding article](/en/article/getting-started-with-crisp-for-support-1ts8txn/) with operators. #### Channels Essentials is designed for teams that want one real omnichannel inbox. This is the moment to bring your main support channels into Crisp instead of managing them in separate tools. __Good channels to connect first:__ * ****Shared email inbox**** → keep email conversations in the same workspace * ****WhatsApp Business**** → centralize one of the highest-volume support channels * ****Instagram DMs**** → reply to social messages from Crisp * ****Phone integrations**** → connect supported calling partners if phone support is part of your workflow | Useful guides: [shared inbox overview](https://crisp.chat/en/shared-inbox/), [connect WhatsApp Business Platform](/en/article/connect-whatsapp-business-platform-with-crisp-11rcwkw/), [link Instagram DMs](/en/article/how-to-link-crisp-with-instagram-dm-14xg8xl/), [connect Aircall](/en/article/how-to-connect-aircall-with-crisp-5qq4k6/), [connect Ringover](/en/article/how-to-connect-ringover-with-crisp-r8u84t/). #### Knowledge base Once your team starts handling more volume, self-service becomes one of the best leverage points. Your knowledge base will help customers find answers on their own and will also improve what Hugo can use as a source of truth. __Start small with a few articles that cover:__ * ****Account and billing basics**** * ****Setup or installation questions**** * ****Shipping, delivery, or return policies**** * ****Most common product troubleshooting steps**** | Create your first articles with the [Knowledge Base](https://crisp.chat/en/knowledge/), and if you are migrating from another provider, see [how to import a previous helpdesk](/en/article/how-can-i-import-my-helpdesk-from-a-previous-provider-rpa7tv/). #### Workflows Essentials is the first plan where the workflow builder becomes a core part of your setup. Start with a few practical flows instead of trying to map every edge case on day one. __Good first workflow ideas:__ * ****Out-of-office responder**** → acknowledge requests when nobody is available * ****Routing workflow**** → direct visitors to the right team or topic * ****Lead qualification flow**** → collect a few details before handing off * ****Knowledge-based assistance**** → help users find answers before escalation | Use [Getting started with Workflows](/en/article/getting-started-with-workflows-hrmysb/) for the overview, then build specific flows such as a [weekend responder](/en/article/how-to-create-a-weekend-response-bot-1ubwvsu/) or a [department routing bot](/en/article/how-to-create-a-department-routing-bot-11f6pij/). #### Routing and customer data The real power of Essentials comes from combining routing with customer data. Once you know what should happen to conversations based on source, language, topic, or customer segment, Crisp becomes much easier to operate at scale. __What to define early:__ * ****Assignment logic**** → who should receive what * ****Conversation tags or segments**** → how you classify requests * ****Custom data**** → what customer attributes matter in your workflow * ****Escalation rules**** → when a conversation should move to a human | Helpful reads: [set custom user data](/en/article/how-can-i-automatically-set-custom-user-data-1xh7pqk/) and [push user events](/en/article/how-can-i-push-user-events-pxu9vm/). #### Hugo At this stage, Hugo becomes much more useful because Essentials gives you both more included credits and more structured knowledge sources to train on. __A solid setup usually combines:__ * ****Q&A snippets**** → for concise answers to frequent questions * ****Website content**** → for public-facing information * ****Knowledge base articles**** → for more stable support content * ****Conversation history**** → when you already have meaningful support volume | Start with [Getting started with Hugo AI Agent](/en/article/getting-started-with-hugo-ai-agent-w6gbux/) and improve quality with [training Hugo on your own resources](/en/article/training-hugo-on-your-own-resources-ijkdrl/). #### Daily usage Essentials gives teams more ways to answer quickly and consistently. Make sure the available tools actually become part of the day-to-day workflow, otherwise the extra features will stay underused. That usually means relying on ****Shortcuts**** for repeated answers, ****Private Notes**** for internal collaboration, and the available ****AI tools**** for drafting or accelerating replies. --- # Next steps Essentials works best when you combine channels, knowledge, workflows, and routing into one support setup. You do not need to launch everything at once, but you should make sure each part supports the others. __Helpful articles to continue:__ * ****Workflows overview**** → [Getting started with Workflows](/en/article/getting-started-with-workflows-hrmysb/) * ****Hugo setup**** → [Getting started with Hugo AI Agent](/en/article/getting-started-with-hugo-ai-agent-w6gbux/) * ****Knowledge base**** → [Knowledge Base](https://crisp.chat/en/knowledge/) * ****Plans overview**** → [Pricing and plans](https://crisp.chat/en/pricing/)