People (CRM)
Find a customer, read their conversation, add a label and save a phone number or other details. Profiles, filters and export.
이 페이지에서
People contains customers who have messaged the bot. Open a profile to see the conversation, files and saved details such as a phone number, a course of interest or payment status. Profiles are created and updated automatically from events.
This customer list is a CRM. Labels identify groups such as “Paid”, while parameters store specific values such as phone or order_id.
User list
The table shows each person's name, Telegram ID, labels and activity (when they were last seen or whether they blocked the bot). Search by name or ID, or use the All, VIP, Paid, New and Unsubscribed label filters. Each button shows a count. Click a row to open the conversation.
Blocked shows only people who blocked the bot; their profile shows the block date. Export CSV downloads the current search and filter result, up to 10,000 rows. You can open CSV in a spreadsheet. The file has columns tg_user_id, name, username, platform, is_blocked, blocked_at, first_seen, last_seen, labels; labels are separated by ;, and dates use RFC3339. Text cells are protected from being executed as spreadsheet formulas. If the limit cuts off rows, the API returns X-Export-Truncated: true. For API access, use GET /api/bots/{botID}/users?is_blocked=true&format=csv. The is_blocked=true|false parameter also works with the ordinary JSON list, where blocked users have a blocked_at field.
What is stored about a user
A profile contains an avatar, name, @username, an Open in Telegram link, message and conversation counts, first and last conversation times, labels and global parameters. It also shows whether the person blocked the bot or is waiting for an operator.
Subscriber source shows the first link through which the person came to the bot. For example, a separate spring-campaign link helps distinguish those visitors. Values identifying the campaign are UTM tags. In Telegram, the extra part after start= is the payload, or start parameter.
Examples:
- Telegram:
t.me/<bot>?start=utm_source-vk__utm_medium-cpc__utm_campaign-spring. Telegram payloads allow only letters, digits,_and-. Pairs are separated by__, and the first-separates each key from its value. - VK:
vk.me/<group>?ref=utm_source=vk&utm_medium=post. - Referral link:
t.me/<bot>?start=ref_<their ID>. The profile and{{referrals.count}}substitution show how many people this subscriber invited. Theref=<ID>andref_<ID>formats are parsed separately from UTM.
Five fields are saved: utm_source, utm_medium, utm_campaign, utm_content and utm_term. The first non-empty value is used for each. They are available in substitutions and segments as attribution.utm_source … utm_term.
The source is fixed by the first non-empty start payload. This is called first touch. A later /start does not change it or add UTM from a new link. If the first payload was an arbitrary or referral tag, UTM fields remain empty. An empty payload does not claim the source.
In segments, UTM from the start link takes precedence over the same-named website-visit tags. Missing link fields use web data; a link without UTM does not erase it. The source belongs to the channel of the first start and appears in segments after recomputation only for a subscriber with the same ID in that channel.
Labels
A label identifies a subscriber group, such as VIP, Paid, New or Unsubscribed. You can create your own labels and choose their colors. Add one manually or with Edit labels, then use it in conditions (“With labels”) or to select broadcast recipients.
A label can be permanent or last a set number of days. When it expires, it is removed automatically and the bot receives a Label expired event. Through the API, use POST /api/bots/{botID}/users/{tgUserID}/labels with a canonical UUID label_id and optional ttl_days from 0 to 106751. ttl_days: 0 makes the label permanent; temporary-label expiry is returned as label_expires_at in the user list.
Parameters
Parameters store values tied to a user, such as name, email, amount, order status or points. Edit parameters, Save message and dialog steps can populate them. Use them in substitutions ({{param.key}}) and conditions (“With parameters”). This gives the bot a small customer profile without an external database.
Conversations
A conversation shows messages, photos, video, voice messages, documents, buttons and delivery marks. Sent reactions appear as separate cards. At the bottom, you can reply, attach a file or send a reaction selected from the list.
Attachments
Attachments opens a gallery of all files in the conversation with Photos, Files, Voice and Links filters and a Download all button.
Conversation history and import
The conversation stores the full history with the user. Older messages load when you scroll up, so a long history opens without waiting for every message. New messages appear immediately in an open conversation, as in the operator queue.
If you migrate a bot from SamBot, conversation history is imported with the users. The profile then shows earlier messages and attachments. See Import from SamBot.
Customer profile and bulk actions
The profile combines customer details, an event history (timeline), segments, the conversation and operator notes. History loads in batches and can be filtered by type, source and date. Save property and label changes to record them in the audit log and start a segment recomputation.
Select customers to apply a property in bulk. The operation keeps a snapshot of the selected audience, is limited to 5,000 people and is safe to retry. CSV export is a separate saved operation that you can cancel before download. A bulk change already applied cannot be partly rolled back.
Merge profiles
The project owner can select two people on the same list page and choose Merge profiles. Check their contact details and channels, select the profile to keep, and confirm. Their history and data are combined; the selected profile takes priority for conflicting properties. A merge cannot be undone.
Unfinished CRM synchronization or an unresolved Ozma operation blocks the merge until it is finished or reviewed. Conflicting contact details and links to different CRM records must be reconciled first.
Matching email addresses alone do not merge GetMyBot profiles. Use signed identify to link a website visitor to an authenticated user. A confirmed Telegram link is available only when the feature is enabled in your region; connecting the channel alone is not enough.
What's next
- Chats and operators: the operator queue and handoff.
- Conditions and chats: filters using labels and parameters.
- Broadcasts: broadcasts to customer segments.
- Import from SamBot: conversation-history migration.
Dynamic segments
In Segments, define an audience by combining conditions with AND or OR. Preview the definition before saving. After changes, recompute membership and check that the segment is ready before choosing it for a broadcast. Saving the definition alone does not confirm that the member count is current.