> For the complete documentation index, see [llms.txt](https://help.novatalks.com.ua/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novatalks.com.ua/en/get-started/a-i-and-bots/flow-bots/flow-bots-list-and-creation.md).

# Flow Bots list and creation

## List of Flow Bots

The Flow Bots page displays all created Flows, grouped by launch trigger.

<figure><img src="https://2498134934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5yF7NRiGknx3Bqj4OgYA%2Fuploads%2Fx32A9YZXJ55vHmTFaonV%2Fimage.png?alt=media&amp;token=8d4bf794-1582-48e8-84a9-f01776bcef3d" alt=""><figcaption></figcaption></figure>

1. Type – the kind of Flow: Interactive (message icon) or Background (lightning icon). The kind is determined by the system automatically; for details, see the section "Flow types: interactive and background".
2. Name – the name of the Flow.
3. Status – an Active / Draft toggle. Clicking the toggle immediately activates or deactivates the Flow without opening the editor.
4. Channel type – the channel types for which the Flow works.
5. Actions – the Edit (pencil), Duplicate (copy), and Delete (red cross) buttons.

***

### Flow Groups and Order

Flows are grouped by launch trigger. The group header contains the trigger name and the number of Flows in the group. A group can be collapsed or expanded by clicking "∨".&#x20;

By default, groups are displayed in the following order:

1. Customer initiate a new dialog
2. Customer sends any message
3. Dialog status is changed
4. Customer is not responsive
5. Agent is not responsive
6. Reusable workflow&#x20;

The order of Flows within a group, as well as the order of the groups themselves, can be changed by dragging – using the dotted icon (::) that appears when you hover over a Flow row or a group header.

<figure><img src="https://2498134934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5yF7NRiGknx3Bqj4OgYA%2Fuploads%2Fkbg115IkXZoNTUbs7S8X%2Fimage.png?alt=media&amp;token=8cacebef-7de0-4588-bfe1-5b27b91ef343" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The order of Flows within a group matters: if several interactive Flows match the launch conditions, the first one in the list will run. For details, see the section "How Flows Are Launched".
{% endhint %}

***

### Deleting a Flow

To delete a Flow, click the red cross in the Actions column. In the Delete Confirmation window, click Yes, Delete to confirm or No, Keep to cancel.

<figure><img src="https://2498134934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5yF7NRiGknx3Bqj4OgYA%2Fuploads%2FODj6BA5dPWXuMxpzR6wa%2Fimage.png?alt=media&amp;token=06e537f9-457b-4750-8c1d-b7a84477229c" alt=""><figcaption></figcaption></figure>

{% hint style="danger" %}
A deleted Flow cannot be restored.
{% endhint %}

***

### Creating a Flow Bot

To create a new Flow, click the + Add button in the upper-right corner of the page and select one of the options:

<figure><img src="https://2498134934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5yF7NRiGknx3Bqj4OgYA%2Fuploads%2F0Fh6vBe8VdKvY66bCird%2Fimage.png?alt=media&amp;token=4cce45d7-690d-476c-a26d-e0c8ab00c518" alt=""><figcaption></figcaption></figure>

• Create from scratch – the Flow editor opens immediately, with the launch settings panel on the right.

• Add from template – the library of ready-made Flow templates opens.

***

### Templates

<figure><img src="https://2498134934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5yF7NRiGknx3Bqj4OgYA%2Fuploads%2FSOYH88iNR7q10MBhoE5z%2Fimage.png?alt=media&amp;token=8a438c0e-f1be-457a-982c-4f6b3e200030" alt=""><figcaption></figcaption></figure>

The following templates are available in the library:

| Template                                                                                                  | Purpose                                                                                                  |
| --------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| When a customer starts a conversation                                                                     | Launch a flow scenario based on the customer's language and working hour                                 |
| When a customer sends a message                                                                           | Ask the customer questions and collect the necessary data                                                |
| When a customer is not responding (on agent)                                                              | Send a reminder message to the customer                                                                  |
| When a customer is not responding (on bot)                                                                | Close the conversation                                                                                   |
| When a conversation is resolved — send CSAT (basic)                                                       | Send a customer satisfaction survey after the conversation is closed                                     |
| <p><em>! planned for upcoming releases</em><br>When a conversation is resolved — send CSAT (advanced)</p> | Send an advanced customer satisfaction survey with additional questions after the conversation is closed |

***

### Flow Launch Settings&#xD;

When you create a Flow, the launch settings panel opens to the right of the canvas. The trigger is selected first – the set of other fields depends on it.

<figure><img src="https://2498134934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5yF7NRiGknx3Bqj4OgYA%2Fuploads%2FLj44PJ5t2lTclU8xP2UI%2Fimage.png?alt=media&amp;token=d5241ff3-6cf5-4b33-8814-46279a372349" alt=""><figcaption></figcaption></figure>

1. How workflow starts – the trigger that launches the Flow when it fires. For details, see the subsection "Triggers". "Customer initiate a new dialog" is selected by default.
2. Workflow name – the name of the Flow. The name must be unique.
3. Inbox types – one or more channel types for which the Flow will work. The list shows only the channel types connected in the account.
4. Conditions – optional filters that a dialog must match for the Flow to start. For details, see the subsection "Conditions".

<figure><img src="https://2498134934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5yF7NRiGknx3Bqj4OgYA%2Fuploads%2FImNAXFFyvlTiWCrXsPjM%2Fimage.png?alt=media&amp;token=9ff9b0e3-ce18-4fda-8959-86f89d71ed9c" alt=""><figcaption></figcaption></figure>

The Create button becomes active (green) only after all required fields are filled in.

{% hint style="danger" %}
The trigger cannot be changed after the Flow is created. If you need a different trigger, create a new Flow.
{% endhint %}

***

### Triggers

<figure><img src="https://2498134934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5yF7NRiGknx3Bqj4OgYA%2Fuploads%2F1NkR4JJcN5zr1NFTPAEi%2Fimage.png?alt=media&amp;token=c539cc15-14ce-49bf-901a-0b3176dffeeb" alt=""><figcaption></figcaption></figure>

Triggers are grouped by the moment they start: at the start of a dialog, during a dialog, and triggered by another workflow.

| Trigger                        | When the Flow starts                                      | Additional fields                                                                                                                                                              |
| ------------------------------ | --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Customer initiate a new dialog | The customer starts a new dialog                          | –                                                                                                                                                                              |
| Customer sends any message     | The customer sends a message during a dialog              | –                                                                                                                                                                              |
| Dialog status is changed       | The dialog status changes to one of the selected ones     | Triggers when the status changes to – one or more statuses: Open, Pending, Snoozed, Resolved                                                                                   |
| Customer is not responsive     | The customer does not respond within the specified time   | <p>No response from the customer for – a number and a unit of time (seconds, minutes, hours, days); 5 minutes by default.<br>While the dialog is being handled – see below</p> |
| Agent is not responsive        | The agent does not respond within the specified time      | No response from the agent for – a number and a unit of time; 5 minutes by default                                                                                             |
| Reusable workflow              | Only from another Flow – via the "Run Another Flow" block | Conditions are not configurable                                                                                                                                                |

The "While the dialog is handled by" field (only for the "Customer is not responsive" trigger) determines whose last message is taken into account:\\

\
**•** Bot or agent – the Flow starts regardless of who sent the last message to the customer (default value);\\

\
• Bot – the Flow starts only if the last message to the customer was sent by a bot (a Flow or a chatbot);\\

\
• Agent – the Flow starts only if the last message to the customer was sent by an agent.

{% hint style="success" %}
The Reusable workflow trigger is used for parts of a scenario that repeat across different Flows, for example, requesting contact details or a CSAT survey. Such a Flow is configured once and called from other Flows with the "Run Another Flow" block.
{% endhint %}

***

### Conditions

Conditions let you start a Flow only for certain dialogs – for example, only for dialogs where the customer's language is Ukrainian. To add a condition, click Add Filter and fill in:

1. Condition – the dialog parameter that is checked;
2. Operator – for example, Equal to or Not equal to;
3. Values – one or more values of the parameter.

The set of conditions is standard.

Calendar condition is available – it lets you start different Flows during working and non-working hours, according to the calendar settings.

There is also the Message condition – it lets you analyze the customer's messages.

{% hint style="danger" %}
If a condition is added, it must be filled in completely – otherwise, the settings cannot be saved. An incomplete condition can be deleted.
{% endhint %}
