Skip to content
ChatterfyHelp Center
HomeGeneralCRMAI ManagerTrackerPlatformsFAQUpdate log
Main
Bot Settings
Automation & AI
CRM defaults
Flow Settings
AI Settings
Steps
Communication
Changes
Terms
Tracking
Additional
Messenger
Client card
Chat data
Chat data — main card tab
Manual — Manually Changing Lead Parameters
Custom Data — manually filling in custom fields
User Information — basic lead data
Tracker Data — traffic source data
Show Chat Events — displaying service events
Actions — exporting and clearing a conversation
Events
Users
Mailings
Analytics
  1. CRM
  2. Chat data
  3. User Information — basic lead data

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

Updated August 30, 20264 min
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 the lead’s “ID card” in the system.
When to open this
If you need a Chat ID for an outgoing webhook, copy it from here. If a lead wrote to support (“nothing works”) and you need to find them on your side, copy the Telegram ID and find them using the filter in Users. When debugging a flow, you need to know which step the lead is on — Step ID. If you want to check how long the lead has been with us, use the dialog start date.
User Information block
User Information in Chat data




What is displayed

Field
What it shows
When needed
Username
@name in Telegram (or empty if the lead did not specify one)
Find the lead in Telegram, mention them in support
Telegram ID
Unique user ID in Telegram
Unique lead binding, search using a filter
Chat ID
Unique dialog ID
Webhook, manual sending via API, support
Step ID
ID of the current flow step
Flow debugging, manual routing
Dialog start date
When the lead first wrote to the bot
Understand the lead’s “freshness,” filter by Created At



Username vs Telegram ID vs Chat ID — the difference

These three concepts are often confused. Here is what each one means:
Username — the user’s public @name in Telegram. It can change (the user changed their handle) or be absent (the user has not set a username).
Telegram ID — the user’s unique, permanent ID. It does not change. If the username is empty or changes, the Telegram ID remains the same.
Chat ID — the unique ID of the conversation between this user and your bot. The same user will have different Chat IDs for different bots of yours. Used in the API.
Which ID to use
To find a user in your data, use Telegram ID (stable). To send a message via the Telegram Bot API or webhook, use Chat ID. Username is for mentions in regular text, but NOT for technical identification (it can change).




Step ID

Step ID is the internal identifier of the current step in a flow. It is usually needed only for debugging or integrations. In Manual, you see the step name in human-readable language. Here, you see the technical name (UUID or slug).



Conversation start date

When the first Contact occurred — the lead sent the bot their first message. Used in filters User filtering — 11 parameters(the Created At parameter), for segmentation such as “new leads in the last 7 days.”
Do not confuse with Subscribe
The conversation start date is the first Contact (the user wrote to the bot). Subscribe is the first subscription to the channel / bot launch — it may happen earlier, and is counted separately in Tracker.



Usage examples

Scenario 1 — webhook integration:
You want to send a Chatterfy chat to an external CRM when a certain event occurs.
Webhook step → pass Chat ID + custom data.
The external CRM finds / creates a record by Chat ID — Chat ID becomes the primary key.
Scenario 2 — support is looking for a specific lead:
The lead wrote to support: “Something isn’t working for me.”
Support asks: “Send us your Telegram username or ID.”
Lead: “@vasya123”.
The operator opens Users→ Search → @vasya123 → finds the chat → sees User Information.
Scenario 3 — debugging a flow with support:
AI is not responding for a specific lead.
The operator copies the Step ID + Chat ID and sends them to the support chat with a description of the issue.
Support uses the ID to reproduce and diagnose the issue.



What to keep in mind

Username can change
A Telegram user can change or delete their @username at any time. After that, the old username will no longer work — searching by it will not find the lead. If you need stable identification, store and search by Telegram ID, not by username.



Frequently asked questions

The Telegram ID field is the Telegram User ID. It is a unique lifetime identifier for the user. If the field is empty, this is unusual (a bug or connection-specific behavior); contact support.

Telegram ID identifies the user (one per Telegram account). Chat ID identifies the conversation between a specific user and a specific bot (different for each of your bots). To send messages via the Bot API, you need the Chat ID, not the Telegram ID.

No. Telegram ID is stable and never changes. Username can change. If you want to always be able to find the lead, search by Telegram ID or Chat ID.

The avatar is displayed at the top of the customer card and in the chat list in Messenger. In User Information, it is not duplicated as a separate field. If you need the avatar URL for an integration, there is currently no such endpoint; contact support.

Automatically when the lead sends the next message. Telegram sends the current username with each message, and the bot updates it. You cannot force an update from the UI.

In the Webhook — Sending Data Out step, add the {chatId} placeholder to the URL or body. The webhook will send a request with the current Chat ID of the lead for whom the step was triggered.



Related

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
Webhooks & API — receiving data from external sources
With a webhook, an external service can update user data, change the chat status, switch Flow steps, write values to Custom Fields, add or remove tags, and manage the conversation from an external sys
Webhook — Sending Data Out
The Webhook step sends an HTTP request to an external URL with lead data. This is an outgoing webhook, unlike , which describes receiving data from external systems. It is used for integrations with t
User filtering — 11 parameters
The Filters section in the table is used to work with a large customer database. With it, you can do the following in just a few seconds: find the leads you need build an audience for a broadcast see

Was this article helpful?

BackCustom Data — ручное заполнение кастомных полейNextTracker Data — traffic source data

On this page

  • What is displayed
  • Username vs Telegram ID vs Chat ID — the difference
  • Step ID
  • Conversation start date
  • Usage examples
  • What to keep in mind
  • Frequently asked questions
  • Related