בסיס הידע של GetMyBot

People (CRM)

Subscriber database: labels, parameters, dialogs, and attachments.

בעמוד זה

The People section is your bot's CRM: everyone who has messaged the bot is added to the subscriber database. Here you can see a user's profile, their labels and parameters, the full conversation history, and attachments. User records are created and updated automatically on every event.

User list

The table shows name, Telegram ID, labels, and activity (last seen or "blocked" status). Search by name/ID is available, as well as a label filter with quick chips: All, VIP, Paid, New, Unsubscribed: each with a counter. Clicking a row opens the dialog.

What is stored about a user

A user card contains: avatar, name, @username, an "Open in Telegram" link, counters (messages, first and last dialog), labels, and global parameters. It also shows whether the user has blocked the bot or is waiting for an operator's response.

Subscriber source. When someone arrives through a link like t.me/<bot>?start=utm_source-vk__utm_medium-cpc__utm_campaign-spring (a Telegram payload allows only letters, digits, _ and -, so pairs are separated by __ and the key is split from the value at the first -) or vk.me/<group>?ref=utm_source=vk&utm_medium=post (VK), the UTM tags are stored on the first start together with the channel it came from and never change afterwards (first touch). They are available in substitutions {{utm_source}}, {{utm_medium}}, {{utm_campaign}}, {{utm_content}}, {{utm_term}} and in segments (fields attribution.utm_source … utm_term). In segments the tags from the link take precedence over the same-named UTM of that person's web visits, while keys the link did not carry keep their web values; a link without UTM (an opaque campaign tag) adds no values and never erases web data. The source is bound to the start channel: it reaches segments only for the subscriber with the same identifier on that channel, and shows up there after the next recompute.

Labels

Labels are subscriber tags (VIP, paid, new, unsubscribed, and custom ones). They can be set manually or by the "Edit labels" action and are used in conditions ("With labels") and for broadcast segmentation. Label colors and sets are configurable per bot.

Parameters

Parameters are arbitrary values tied to a user (name, email, amount, order status, points). They are populated by the "Edit parameters", "Save message", and dialog step actions, and used in substitutions ({{param.key}}) and conditions ("With parameters"). This gives the bot a mini-profile for each customer without an external database.

Dialogs

The dialog window shows the full conversation: text, photos/videos, voice messages with a waveform, documents, inline button previews, delivery marks, and reaction "pills". At the bottom is an input field: you can attach files, write a message, or send a reaction to the user by picking a reaction.

Attachments

The Attachments button opens a gallery of all files in the dialog with filters Photos, Files, Voice, Links, and a Download all button.

Dialog history and import

The dialog stores the full conversation with the user. Older messages are loaded in batches as you scroll up (cursor pagination), so even long histories open quickly. New messages appear in the open dialog in real time: just like in the operator inbox.

If you are migrating a bot from SamBot, the dialog history is imported together with users: after import, the card immediately shows past conversations and attachments. See Import from SamBot.

Customer card and bulk actions

The customer card brings together profile data, a paginated timeline, segment membership, the conversation and operator notes. Timeline entries can be filtered by kind, source and date range. Property and label changes require an explicit save, are audited, and queue a segment recompute.

Select customers in the list to apply a property in bulk. The operation saves its audience snapshot, is limited to 5,000 customers and is safe to retry. A CSV export is a separate saved operation and can be cancelled before download. A committed bulk profile change is atomic and is never partially rolled back.

What's next