# Moving clients to another block When working with clients on the MaviBot platform, users may need to move certain groups of clients between different blocks. This can be done in two ways directly within the funnel builder: 1. By sending messages 2. Without sending messages {% hint style="success" %} Available on the "Business" and "Infobiz" plans (NOT during the Infobiz plan trial period). {% endhint %} Let’s take a closer look at each of these methods. ## Moving via message sending #### From one block to another Before getting started, go to the **“Funnel Builder”** section and locate the block in the flowchart **from which** you want to move a specific group of clients (or all clients) to another block.
Next, select the block **to which** the clients should be moved, as well as the block **from which** they’ll be moved. For example, we’ll select the clients who were verified by the bot for subscription status (marked in Fig. 1) and move them to the **“Join the meeting!”** block (marked in Fig. 2).

Рис. 1

Fig. 2

Open the block settings and look for the three-dot icon — this opens the additional commands menu.\ In this case, you need to select the action **“Create broadcast”**, which will then take you to a new window — the broadcast creation form. **Make sure to remember the number of the block from which you want to move the clients.** You’ll need it later.

Fig. 3

For this example, let’s choose a broadcast to messengers:

Fig. 4

Then, in the window that opens, you’ll see three tabs: **“Recipients”**, **“Message”**, and **“Send”**.

Fig. 5

In each tab, we’ll only use the settings needed to move clients from one block to another. In the **“Recipients”** tab, select the following settings:

Fig. 6

1. The **“Broadcast name”** field is for your convenience, helping you navigate existing broadcasts in the Salebot system later. It’s an optional field. 2. Now, locate the **“Broadcast to clients from blocks”** field:

Fig. 7

This is where you’ll need the number of the block **from which** you want to move the clients. You can copy the block number directly from the block itself and paste it into the broadcast field.

Рис. 8. Номер блока, из которого перемещаем клиентов

Fig. 9. Inserting the block number into the broadcast field

Check the box next to the number of the required block. This way, we’ve selected the clients located in the "Subscribed" block to be moved to another block. ### Other filters for moving clients to a block You can use other filters to move clients to a block. {% hint style="warning" %} Note! Use the filters you need depending on your project! \ If you haven’t applied any client criteria (for example, you don’t use lists or tags, haven’t built a site on MaviBot, etc.), then you don’t need to use these filters! {% endhint %} 1. By status in MaviBot CRM:

Fig. 10. Broadcast by status in MaviBot CRM

2. By connected messengers:

Fig. 11. Broadcast by messengers

Choose this type of broadcast based on the logic of the messengers connected to your chatbot flow; otherwise, the broadcast may not work correctly. 3. By lists/tags (you can also exclude any lists or tags that you don’t want to move):

Fig. 12. Broadcast by tag

3. By client variables (with the option to exclude certain client variables) / by deal variables (with the option to exclude certain deal variables):

Fig. 13

You can specify any necessary variables you have in your project. For example, in this case (Fig. 13), we have a variable called **age** that stores the client’s age. If the age is greater than or equal to 18 (≥), the client will be moved to the block with the meeting message; if it’s less than or equal to 17 (≤), they won’t be moved. 5. By registration date:

Fig. 14. Broadcast to clients by registration date

You can use this type of broadcast, for example, when you want to offer your clients promotions, discounts, or other bonuses in honor of their long-term relationship with you (for example, after six months). 6. Add or exclude a tag (from the site/landing page):

Fig.15 Broadcast by tag

In this case, you need to find your landing page tag in the **“Sites”** section:

Fig. 16. Mini landing page tag

If you need to move clients based on the filters described in this section, you should also create a broadcast through the funnel builder: **Step 1.** Select the block to which you want to move clients and send them a message.\ Open the additional settings menu and choose **Create broadcast → Messengers:**

Fig. 17. Creating a broadcast within the block

**Step 2.** In the window that opens, go to the **“Recipients”** tab and select the desired broadcast criteria. ### Using a .csv file If you need to import clients from a file into the funnel, use this method.
**Step 1.** Select the block where you want to move the clients:

Fig. 18

Open the additional settings menu and select “Broadcast to messengers,” which will take you to the broadcast creation window. **Step 2.** In the **“Recipients”** tab, under filter type, select **“Upload from file”**:

Fig. 19

To create a mailing list, you can download your client list and then filter it in Excel. Alternatively, you can upload a CSV file where the first column contains client identifiers — `client_id`. Please note: * The exported client file uses **UTF-8 encoding**. * The delimiter is a **semicolon (;)**. {% hint style="success" %} To send a broadcast via WhatsApp, simply upload a CSV file where the first column contains phone numbers. {% endhint %} **Step 3.** Select the CSV file with clients that you want to upload to the system. ## The "**Message"** and "**Send"** tabs **“Message” tab**\ After selecting the message recipients from the chatbot, move to the **“Message”** tab, where all the necessary settings are already applied according to the block’s setup in the flowchart, making your work much easier.

Fig.20 “Message” tab

You DO NOT NEED to edit this tab. As shown in Fig. 20, the message text already reflects the block’s settings, as do the other input fields on this tab. The messages and all actions planned in the broadcast will be executed according to the block’s configuration! In this same tab, you’ll see the number of the block to which clients will be moved after receiving messages from the chatbot (the client’s movement to the required block).

Fig. 21. Block number matching the number shown in the "Message" tab

{% hint style="danger" %} NOTE! Do not change or modify the advanced button settings unless absolutely necessary! \ If you need to edit the block’s buttons, make the changes directly in the block settings within the funnel builder! {% endhint %} #### "Send" tab In this tab, you can set the message to be sent on a specific date, choose a convenient time, or send it immediately.

Fig. 22

You can also split the broadcast into parts by staggering it over time for clients, or select a specific number of clients to receive it.

Fig. 23

If needed, turn off the **“Save broadcast in client chat history”** toggle (it’s enabled by default).
After completing all the necessary settings, you can launch the broadcast to your clients, which will move them to the desired block in the chatbot. ## Moving clients without sending a message If you don’t want to send a message to the client when moving them to the desired block, you can use one of the following two methods: 1. Temporarily replace the text with `#{none}`, then after moving, restore it back. In this case, all settings are done the same way as when moving to a block with a message sent, but instead of message text, use `#{none}`. This will trigger the bot without sending a message.

Fig. 24

2. Alternatively, create a full clone of the block with all connections and replace the text with `#{none}`; from there, the autoresponder funnel will continue as usual. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.mavibot.ai/how-to-do.../moving-clients-to-another-block.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.