> ## 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).

# How does the Automated inbox work

*This article explains how the Automated inbox works when Hugo handles conversations for your team.*

When Hugo is active, Crisp groups conversations handled by the AI Agent in a dedicated **Automated** inbox. This keeps human inboxes focused on conversations that need agent attention, while still letting your team review Hugo's work and step in whenever needed.

---

# ${color}[#0080dd](What the Automated inbox is)

The **Automated** inbox is a dedicated inbox where conversations handled by **Hugo** are routed. It separates AI-handled conversations from your human team’s regular inboxes.

When a new conversation starts and Hugo is enabled:
* The conversation is **routed to the Automated inbox**
* Your support team is **not notified by default**
* Hugo attempts to resolve the conversation autonomously

This allows your team to stay focused on complex or high-value requests without being interrupted by routine questions Hugo can handle.

![Automated inbox for conversations handled by Hugo](https://storage.crisp.chat/users/helpdesk/website/-/8/7/a/e/87ae2703583ac800/cleanshot-2026-05-04-at-122040_b2sw7n.png =400xauto)

---

# ${color}[#0080dd](How escalation works)

If Hugo cannot confidently answer, detects that human help is needed, or reaches an escalation rule you configured, the conversation is escalated back to humans.

When escalation happens:
* The conversation leaves the **Automated** inbox
* It is moved to the **Main Inbox** by default
* Your usual inbox routing rules can then move it to the right sub-inbox
* Human agents can take over the conversation normally

If you want new conversations to go directly to humans instead of staying in the Automated inbox, open [**Crisp**](https://app.crisp.chat), go to **AI Agent → Agent → Activation**, and change the default target to **Route to Inbox**.

---

# ${color}[#0080dd](How Workflows interact with the Automated inbox)

If a conversation is routed through a workflow, it can still remain in the **Automated** inbox by default. This is expected when the automation is part of Hugo’s handling flow.

If a workflow should hand the conversation to humans, add a **Move to Inbox** block and select the destination inbox, such as the **Main Inbox** or a specific sub-inbox.

|| Without a **Move to Inbox** block or a Hugo escalation, the conversation can remain in the Automated inbox even if a workflow was involved.

---

# ${color}[#0080dd](Conversation reactivation and auto-resolve)

A resolved conversation can re-trigger Hugo when the user sends a new message during the configured reactivation window. This helps preserve continuity when the customer comes back shortly after the conversation was closed.

You can also control how long Hugo keeps inactive conversations open. To change this, open **AI Agent → Agent → Settings**, then adjust the **Auto-resolve after user inactivity** setting.

| Auto-resolving inactive conversations helps keep the Automated inbox clean while preserving enough time for users to follow up.