Getting started with the Plus plan

Learn how to set up Crisp Plus around scale, automation, and deeper AI usage.

Plus is built for larger or more advanced teams that want the full Crisp experience. It includes 20+ seats, more Hugo credits, the broader AI-first support suite, unlimited task automations, ticketing, advanced analytics, white labelling, enhanced rate limits, and access to a wider integration strategy. It is the right plan when Crisp becomes a central support platform rather than just a shared Inbox.

Plus plan features

The Plus plan includes everything from the Free, Mini, and Essentials plans, plus the additional features needed for scale, advanced support operations, and deeper automation.

Plus includes $75 of Hugo credits, which Crisp estimates at around 1350 automated conversations per month.

Main features unlocked:

20+ seats included → scale a larger support organization
AI-first support suite → unlock deeper AI capabilities across the workspace
Unlimited task automations → connect your AI Agent to third-party tools for repetitive actions
Ticketing system → offer a dedicated customer portal for support requests
100+ integrations → connect Crisp with the rest of your stack
White labelling → remove Crisp branding from the widget, emails, and knowledge base
Enhanced rate limits → adapt the platform to heavier usage
Advanced analytics → build more tailored reporting around your KPIs
More sub-inboxes → structure larger teams, brands, regions, or support tiers more clearly

Recommended setup

Plus is usually about making an existing support operation more scalable. Before adding advanced automation, make sure your workspace structure reflects how the team actually works.

Review team structure

With 20+ seats, Plus is often used by multiple teams, regions, or support tiers at once. Start by inviting the right operators and reviewing ownership at the workspace level.

Open Crisp, then go to Settings → Workspace Settings → Operators and Teams. Review roles, access, and team responsibilities before building more automation around them.

Read How do I invite other agents to my Inbox? if you need the invite steps.

Design sub-inboxes intentionally

Sub-inboxes are one of the most valuable Plus features operationally. They let you separate ownership, visibility, and escalation paths more cleanly as volume grows.

Open Settings → Message Settings → Sub-inboxes to create or adjust them.

Common sub-inbox patterns include:

Team → support, sales, success, partnerships, billing, technical escalation
Priority → VIP, escalations, incidents, enterprise, urgent conversations
Channel → WhatsApp, Instagram, email, phone, website chat
Region or language → useful when support is distributed
Brand or product line → useful when one workspace supports several business units

Read How to create and use sub-inboxes for the full setup.

Standardize routing and escalation

Plus workspaces can quickly become complex if routing is not documented. Create routing rules that match real ownership, not theoretical categories.

Good routing design should define:

Which conversations enter each sub-inbox
Which conversations should stay unassigned until picked up
Which cases should be assigned automatically
Which escalations should notify a specific team or operator
Which automations are allowed to resolve, hand off, or update conversations

Helpful resources:

Use Hugo and task automation for repeated work

Plus is where Hugo can become more operational. Instead of only answering FAQs, Hugo can combine training resources, routing rules, workflows, and integrations to handle more of the repetitive support workload.

Open AI Agent to configure Hugo. Use Agent → Settings for behavior, Train for resources, Guidance → Instructions for behavioral rules, Guidance → Routing for situations and actions, and Evaluate → Playground to test before going live.

Strong Plus-level AI use cases include:

Order or account lookup → retrieve live details through native integrations or MCP tools
Workflow triggering → start a structured process when Hugo detects a specific situation
Support triage → classify intent, gather context, and route conversations to the right place
Repetitive policy questions → answer with reliable content and escalate when needed
After-hours coverage → resolve documented questions while routing complex ones to humans

Helpful Hugo resources:

Set up ticketing when conversations need longer follow-up

The ticketing system is useful when customer requests do not fit a normal live conversation: bug reports, feature requests, account reviews, investigations, or support cases that require several updates.

Use ticketing when customers need a clear portal to open, track, or follow requests over time instead of relying only on real-time chat.

Read Crisp Ticketing System for an overview.

Clean up branding and customer-facing surfaces

Plus includes white labelling, which lets you remove Crisp branding from customer-facing surfaces such as the widget, emails, and knowledge base. This is especially useful when your support experience needs to fully match your brand.

Review customer-facing surfaces together: chatbox appearance, email domain, signatures, knowledge base domain, colors, and wording.

Helpful branding resources:

Build advanced analytics around your KPIs

Plus is often used by teams that need more than default reporting. Start with Crisp Analytics, then build dashboards around the metrics your team actually reviews.

Common reporting questions include:

How many conversations are handled by AI or automation?
Which channels generate the highest volume?
Which teams or sub-inboxes are overloaded?
Which topics create escalations?
How do response times change during office hours?
Which knowledge base articles reduce support volume?

Read Getting started with the Crisp Analytics to understand default reports and custom dashboards.

Operational habits for Plus teams

Plus gives you more power, but power only helps when the team keeps the setup maintained. Review the workspace regularly so routing, automations, and AI do not drift away from reality.

Useful operating habits:

Audit routing rules monthly → remove outdated rules and simplify overlapping logic
Review Hugo conversations → identify missing knowledge, weak instructions, or escalation gaps
Update knowledge articles continuously → keep the source of truth accurate for agents and AI
Watch automation ratings → understand where automated experiences need improvement
Document ownership → make sure teams understand who handles each channel, topic, and escalation
Monitor usage and limits → review AI credits, API usage, channels, and sub-inbox structure as volume grows

Next steps

Once Plus is active, the best improvements usually come from deeper integration, cleaner reporting, and more reliable AI operations rather than adding complexity everywhere.

Helpful resources to continue:

Updated on: 04/05/2026

Was this article helpful?

Thank you!