Chat data — main card tab

Chat data — the main tab , opened by default when you click a chat. 6 blocks with different functionality in one long right-hand panel. Here the operator sees and changes the lead’s main parameters: s

Updated September 11, 20264 min

Chat data — the main tab Customer Card, opened by default when you click a chat. 6 blocks with different functionality in one long right-hand panel. Here the operator sees and changes the lead’s main parameters: status, sale stage, tags, custom fields. views tracking data and basic information from Telegram. controls the display of system events. exports or clears the conversation.

This is the most “operational” part of the card. If Events and Media are more about reading the history, then Chat data is about action. Every day, the operator changes sale_stage here dozens of times, adds a tag, and fills in Custom Fields after a call.

When to open this

Opened a chat — this is the first thing you see. Want to manually change the sale stage / status / assign it to an operator — Manual. Record a comment, fill in trader_id from a call — Custom data. Find out the ChatID for a webhook or support — User information. Understand where the lead came from — Tracker Data. Enable system events for flow debugging — Show events. Download the conversation or clear the chat — Actions.

What changes automatically and what changes manually

The card collects data from different sources. Some fields are filled in by the bot automatically, while others are the operator’s responsibility:

—Changes automatically: Sale stage (via the Change Sale Status step in the flow), conversation Status (Auto / Waiting / Manual — switches based on operator and AI actions), Tags (via the Change Tag step), Tracker Data (received on the first touch), User information (updated with every lead message), Events (postbacks and flow events).

—Changed manually via Manual: the same sale_stage / status / tags can be overridden by the operator (for example, after a call, manually mark the lead as a “hot lead”). Closed reason and Manager assign are usually set manually.

—Only manually via Custom data: custom fields that are not filled in automatically — operator notes, trader_id from an external source, geo, any arbitrary bot fields.

What’s inside

Six blocks, each with its own reference article.

Manual — Manually Changing Lead Parameters

Manual is a block in → the Chat data tab, where the operator manually manages key lead parameters. Here you will find 6 main fields used in daily work: Sale stage, Status, Flow, Step, Manager, and Tag

Custom Data — manually filling in custom fields

The Custom Data block in → Chat data tab — manually filling in the bot's custom fields. These are all fields from , available to operators for editing. A field can be: empty — a new lead, no data yet

User Information — basic lead data

The User Information block in Chat data is read-only lead data received from Telegram. You cannot change it (Telegram manages it itself), but it is needed for integrations, support, and search. It is

Tracker Data — traffic source data

The Tracker Data block in → the Chat data tab — read-only data about how the lead entered the system: which ad campaign, which source (Facebook / Google / Telegram / Custom), which domain, landing pag

Show Chat Events — displaying service events

The Show Chat Events block in → the Chat data tab — a toggle for displaying system events inside the conversation. When enabled, technical entries appear in the chat feed alongside regular messages: s

Actions — exporting and clearing a conversation

The Actions block in → the Chat data tab is the final block of the card. It contains two buttons: Download messages — exports the conversation history to a file. Clear chat — irreversibly clears the c

—Manual— manual editing of Sale stage, Status, Flow, Step, Manager, and Tags. The operator’s most frequent actions.

—Custom data— filling in the bot’s custom fields (trader_id, geo, note, any fields from Custom Fields).

—User information— read-only basic data from Telegram: Username, Chat ID, Step ID, conversation start date.

—Tracker Data— read-only data from “Tracker — overview” Tracker — Overview— Campaign, source, domain, landing.

—Show chat events— toggle for displaying system events (Change Status / Change Step / Error / AI requests) inside the conversation feed.

—Actions— Download messages (export the conversation) and Clear chat (irreversibly clear the conversation).

Use cases by segment

What different teams do here:

—Affiliate marketer: after a call with a lead, sets Sale stage = Reg/FD via Manual, fills in trader_id in Custom data, and adds a country tag.

—Sales manager: after communication, records the lead’s needs (budget, timeline, objections) via Custom data, assigns the lead to themselves via Manual, and switches the sale_stage.

—Support: opens Custom data to find the order number / product version. copies the Chat ID from User information for a request to the tech department. sets Status = Waiting via Manual while waiting for a reply from the engineers.