Request Information

Request Information

UA

US

RU

UA

US

RU

1. Introduction

In Telegram, there is an option to record subscribers' responses in bots for further use with the «Request Information» block in message blocks.

From this guide you will learn:

  • how to choose the type of requested information and the field to save it in;

  • how to configure the waiting time and message texts;

  • how to set actions for a successful response and for no response.

2. Key terms

Term

Definition

Term

Definition

«Request Information» block

A message constructor element that waits for a text response from the subscriber and saves it to the specified client card field.

Custom field

An additional field in the client card created manually to store specific data.

Waiting time

The period during which the bot waits for the subscriber's response. When the time expires, a no-response message is sent.

3. Block settings overview

Open the message constructor, click «+Message» and select the «Request Information» element. In the window that opens, configure the following settings in sequence.

3.1. Type of requested information

Select the data format you expect from the subscriber:

  • Number

  • Expression

  • Date

  • Phone

  • Email

3.2. Field to save the data

Specify the field where the received data should be saved. For the «Phone» and «Email» types, standard platform fields are available. For other types, you need to create custom fields of the required type in advance.

3.3. Waiting time

The time during which the bot will wait for the user's response. After the specified time expires, the user will receive a no-response message.

Important: while the response waiting block is active, all subsequent message blocks in the sales tunnel for the subscriber are paused and resume once the waiting time expires. However, the waiting does not stop other functional blocks such as «Action» or «Filter». It is therefore recommended to place an empty message block after the information request block and build further connections in the tunnel from it.

3.4. Auto-read response

You can automatically mark the received message with the subscriber's information as read in the chat. To do this, check the corresponding checkbox.

3.5. Information request message text

Set the text of the message the user will receive. The text should include a clear call to action — for example: «Enter your email» or «Type your name».

3.6. Successful response message

Set the text of the message the subscriber will receive when they respond successfully. The field is pre-filled by default, but you can change the message text as needed.

3.7. Action on successful response

In case of a successful response, you can choose an action: subscribe the subscriber 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 via an action, no separate connection to the block is needed.

3.8. Error message

The message text is set by default and informs the user that the response format is not acceptable. You can change it as needed.

3.9. No-response message and action

The user will receive this message once the specified waiting time has elapsed with no response received.

In case of no response, you can also choose an action: subscribe the subscriber to the required tunnel block — «Start», or stop them — «Stop».

Important: you can only configure one action at a time. When subscribing via an action, no connection to the block is required.

4. Related guides

Guide

Purpose

Guide

Purpose

Message constructor

Message constructor: element types, settings, restrictions.

Block placement rules. Conditions of dispatch.

Block placement rules and delivery conditions in sales tunnels.