Request Information
UA | US | RU |
|---|
- 1 1. Introduction
- 2 2. Block setup overview
- 2.1 2.1. Type of requested information
- 2.2 2.2. Field to save the data
- 2.3 2.3. Waiting time
- 2.4 2.4. Auto-read response
- 2.5 2.5. Information request message text
- 2.6 2.6. Successful response message
- 2.7 2.7. Action on successful response
- 2.8 2.8. Format error message
- 2.9 2.9. No-response message and action
- 3 Related instructions
- 4 Key terms
1. Introduction
Definition
«Request Information» block is a message constructor element in Leeloo.AI sales tunnels that turns a passive broadcast into a two-way dialogue: the bot asks the subscriber a question, waits for a text response, validates the format, and saves the data to the client's card. It is used at the Engage and Manage stages — wherever you need to collect structured data from a subscriber without handing them off to a manager. Available only for the Telegram communication channel.
The block supports five data types — Number, Expression, Date, Phone and Email. For «Phone» and «Email» the platform's standard fields are used; for the other types the operator creates custom fields of the required format in advance. The block waits for the response for the configured time, after which the fallback scenario triggers — a no-response message and an optional action.
The B2B operator (business owner, marketer, or content manager) configures the block once via the message constructor: picks the data type, specifies the field to save the answer, sets the waiting time, writes the message texts (request, success, error, no response), and chooses an action — subscribe to a tunnel block or stop the subscriber's movement.
The B2C client (a Telegram subscriber) receives the question in the chat with the bot — for example, «Enter your email» or «Type your name» — replies with a text message, and immediately sees either a success confirmation or a format-error message. The validation and saving mechanism is hidden from them.
The subscriber's answer is written to the Client's Card in the specified field. While the block is waiting for a response, all subsequent «Message» blocks in this subscriber's tunnel are paused and resume only after the answer is received or the waiting time elapses. Important: the «Action» and «Filter» functional blocks are not paused — therefore it is recommended to place an empty «Message» block right after «Request Information» and build subsequent connections from it.
After reading this article, you will understand:
what the «Request Information» block is and what role it plays in a sales tunnel;
which functions it performs at the Engage and Manage stages;
which data types can be collected and which client card fields they are saved to;
how the block interacts with other tunnel blocks and why you should «cover» it with an empty message block;
how to configure all nine block parameters — from the data type to the no-response message.
Purpose
The «Request Information» block is a tool for collecting structured data from a subscriber without handing them off to a manager. It automates short «bot asks — client answers — data lands in the card» dialogues and frees the operator from routine questions on the early funnel stages. The specific function of the block depends on the customer lifecycle stage it is used on.
Engage — the block collects basic contact data right after subscription: email for follow-up broadcasts, first name for message personalization, date of birth for future greetings. The job is to enrich the client's card without a manager's involvement, so the data can later be used for message personalization and audience segmentation.
Manage — the block collects structured deal information before the lead is handed off to a manager: contact phone, budget, timing, key request parameters. The job is to save the manager's time on routine clarifying questions and hand off a client card that already has the key fields filled in.
2. Block setup overview
The «Request Information» block has nine parameters that are configured top-to-bottom in the constructor window: data type, save-to field, waiting time, auto-read checkbox, four message texts (request, success, error, no response), and actions for the successful response and for its absence. Each parameter is described below.
2.1. Type of requested information
Select the data format you expect from the subscriber:
Number — an integer or decimal number (e.g., age, quantity, budget).
Expression — an arbitrary text string with no format validation (name, comment, free-form answer).
Date — a date in a format the platform understands.
Phone — a phone number with automatic format validation.
Email — an email address with syntax validation.
2.2. Field to save the data
Specify the client card field where the subscriber's answer will be saved. For the «Phone» and «Email» types, the platform's standard fields are available. For «Number», «Expression» and «Date» you must first create custom fields of the required type in the client card settings — otherwise there will be no place to save the answer.
2.3. Waiting time
Set the interval during which the bot waits for the subscriber's response. After the configured time elapses, the subscriber receives a no-response message (see 2.9), and the block finishes its work — the tunnel continues along the chosen fallback action.
Important: while the response-waiting block is active, all subsequent «Message» blocks in this subscriber's sales tunnel are paused and resume once the waiting time elapses. However, the waiting does not stop the other functional blocks — «Action» and «Filter». It is therefore recommended to place an empty «Message» block right after «Request Information» and build further connections in the tunnel from it.
2.4. Auto-read response
You can automatically mark the message containing the subscriber's answer as read in the chat. To do so, tick the corresponding checkbox — the manager will not have to manually close the conversation in «Dialogues» once the tunnel has processed the answer.
2.5. Information request message text
Set the text of the message the user will receive. It should contain a clear call to action — for example: «Enter your email», «Type your name», or «Pick a convenient date for the call». How clear this message is directly determines whether the subscriber understands what is expected of them, and in what format.
2.6. Successful response message
Set the text of the message the subscriber will receive after their answer is successfully validated. The field is pre-filled by default, but you can change the wording as needed — for example, add a thank-you or hint at what happens next («Thanks! I'll send the schedule for that date now»).
2.7. Action on successful response
On a successful response, pick an action for the subscriber: subscribe them to the required tunnel block by clicking «Start», or stop their movement through the tunnel — «Stop».
Important: you can only configure one action at a time — «Start» or «Stop». When subscribing the user to a tunnel block via an action, no separate connection to that block is needed — it duplicates the action and may cause a double send.
2.8. Format error message
The text is set by default and informs the subscriber that the response format is not acceptable — for example, when they try to enter letters in a «Number» field or an invalid address in an «Email» field. You can edit the text as needed and add an example of the correct response format.
2.9. No-response message and action
The subscriber will receive this message once the configured waiting time (see 2.3) has elapsed with no response. You can adapt the text to the scenario — for example, gently remind them about the question or invite them to come back to the dialogue later.
If there is no response, also pick an action: subscribe the subscriber to another tunnel block — «Start», or stop their movement — «Stop». This lets you build a fallback branch for subscribers who did not answer in time.
Important: you can only configure one action at a time. When subscribing via an action, no separate connection to the block is required.
Related instructions
Instruction title | Purpose |
|---|---|
Message Constructor — element types, settings, limitations. | |
Запитати інформацію — UA version of this instruction. | |
Запросить информацию — RU version of this instruction. |
Key terms
Term | Explanation |
|---|---|
«Request Information» block | A message constructor element used to collect text responses from a subscriber and save them to the client's card. Available only for the Telegram channel. |
Sales Tunnel | A sequence of blocks that a subscriber moves through; blocks are joined by connections and automate the communication. |
Message Constructor | The editor inside the tunnel where a block's content is assembled and its elements are picked — messages, buttons, information requests. |
Client's Card | The centralized subscriber profile in Leeloo.AI where answers to information requests and all tunnel events are recorded. |
Standard fields | Pre-defined client card fields — «Phone» and «Email» — to which the block saves data with no extra setup. |
Custom fields | Client card fields the operator creates for the required data type (Number, Expression, Date) before using the block. |
Data type | The expected response format — Number, Expression, Date, Phone, or Email. Defines the validation rules. |
Waiting time | The interval during which the bot waits for the subscriber's answer; once it elapses, the no-response scenario fires. |
«Start» / «Stop» action | The block's choice: subscribe the subscriber to the next tunnel block or stop their movement through the tunnel. |
«Action» block | A functional tunnel block that is not paused during the response wait and fires immediately. |
«Filter» block | A functional tunnel block that routes subscribers into branches by conditions and is not paused during the wait. |
Auto-read checkbox | An option that marks the subscriber's answer as read in the chat automatically — without manager involvement. |