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

# How to start Workflows automatically for all incoming conversations

****Workflows are most commonly used within Hugo, who is able to start scenarios at will in predetermined situations. However, this isn't the only way to start workflows. If you do not wish to implement AI Agents, or if you simply first want your users to go through a workflows you've prepared, you have the ability to configure them to be automatically triggered when your users contact you.****

Workflows are no-code procedural automations, they are designed to help you automate processes and be versatile enough to accommodate any type of usages.

By simply selecting and connecting specialized blocks together, you can create a series of events, conditions and actions which allow you to build automations and trigger them automatically in your conversations

Whether you wish to automatically qualify users starting a conversation, filter or categorize their requests, collect information or offer them choice-based paths, workflows can do this before they've even had breakfast.

[Just discovering Workflows? Learn more from this guide](https://help.crisp.chat/en/article/hrmysb/)

---

# Starting Workflows automatically for all incoming conversations

If you wish to trigger your workflows globally and automatically on all new conversations, rather than routing them trough Hugo first, this is possible.

__It may be the case if you wish to:__

* ****collect information**** from your users first
* ****triggered choice-based**** flows, by offering them different options
* ****sort and categorize requests**** ( for instance by checking segments, data, locale...) to handle them differently
* or simply have ****non-AI flows****

__There are two ways to trigger your scenarios automatically anytime a user send a message:__

* ****A. By disabling the AI Agent**** → (Recommended) When the AI Agent is disabled, Crisp automatically falls back to workflows, and evaluate them anytime users contact you
* ****B. By enabling the AI Agent and selecting the "route to workflow"**** target → Instead of answering conversations, Hugo will simply immediately trigger the selected workflow

To get started, head over to [Crisp](https://app.crisp.chat) and navigate to ****AI Agent**** from the left menu.

#### A. Starting workflows for incoming conversations by disabling the AI Agent

You can trigger workflows on all new conversations in 2 steps:

1. Go to ****AI Agent > Agent > Activation**** and disable the option ****Enable agent activation for new conversations****.
2. Create scenarios starting with either [New User Message](https://help.crisp.chat/en/article/understanding-and-mastering-the-crisp-ai-chatbot-1boypme/#6-new-user-message) or [User Message Matches](https://help.crisp.chat/en/article/understanding-and-mastering-the-crisp-ai-chatbot-1boypme/#6-user-message-matches) event blocks, and deploy them.

Your scenarios will now trigger anytime your users send a new messages (based of course on the configuration of your scenarios).

![](https://storage.crisp.chat/users/helpdesk/website/-/d/d/1/f/dd1fded880f82800/5c12edfa-bd10-4181-9d8b-d016c0_8vgn5b.png)

#### B. Starting workflows by selecting the "route to workflow" target

To force all incoming conversations to go through a specific workflow:

1. Go to ****AI Agent > Agent > Activation**** and enable the option ****Enable agent activation for new conversations****.
2. Select the default target ****Directly route to a Workflow**** and select your workflow.

||| When using this method, make sure that your workflow starts with either an Action or Condition block. Otherwise your flow will await for a new event to occur before triggering.

![](https://storage.crisp.chat/users/helpdesk/website/-/9/d/9/9/9d99b21044fae000/2077cb83-70e1-46f1-90aa-ae0757_xrbkyt.png)

---

# Frequently Asked Questions

__Still have some questions which were not covered above? Perhaps you'll find our answer in this FAQ. Also checkout__ [_this article_](/en/article/understanding-and-mastering-the-crisp-chatbot-1boypme/) __and master your workflows craftsmanship!__

__If your question does not figure here, share it with us directly by chat, we'll be available to assist you__

###### My workflows are not starting when users start a conversation

The first step would be to make sure that your scenarios are enabled and deployed. Disabled workflows will never be evaluated when users contact you.

If your workflows are enabled, also make sure their starting block (after the entry block) matches the method you used:

* ****Method A**** → Only workflows starting with an event block ****New User Message**** or ****User Message Matches**** will be evaluated
* ****Method B**** → The workflow you've selected must start an ****Action**** or ****Condition**** block

If you use ****Directly route to a Workflow****, avoid starting that workflow with ****New User Message****. In that setup, the conversation is first routed into the workflow, then the ****New User Message**** block waits for the next user message before continuing. In practice, this often makes the workflow appear not to trigger on the first message.

If you are using Condition blocks early in your flow, ensure that their conditions are indeed met for the conversations you've been monitoring. Also make sure that your blocks are properly connected logically.

If another workflow seems to start instead, verify your workflow priority and make sure the intended workflow is placed before others with overlapping start conditions.

If your tests work in the ****Playground**** but not on your live website, generate a debug link from ****AI Agent > Settings > Get help from support**** so the setup can be reviewed in context.

Finally, attempt disabling/re-enabling your scenarios and testing again.

If despite your efforts the issue still persists, shoot us a message, we'll likely be able to help