Everyone who ever writes to your bot becomes a contact. That is how your own client base gradually accumulates: with their details, conversation history and where they came from. The base can be used for broadcasts and reminders.
What you see for a contact
A contact holds a profile and a history: the name, phone, what they ordered and other data the bot collected along the way. You can see which channel the person came from (Telegram, the website or the widget), when they last wrote, and their tags. Here too are all their conversations and messages. The longer the bot works, the more valuable this base becomes.
Segments
A segment is a rule for selecting clients. For example: “everyone with a phone number filled in”, “whoever ordered this month”, “who has not replied in a long time”. A segment can be checked before use to see how many people fell into it — so the broadcast reaches exactly the people it is meant for.
Broadcasts
A broadcast is a message sent to a chosen segment. Sending goes through a queue that respects Telegram’s message-rate limits, so nothing gets blocked. Progress is visible in real time, and every recipient has their own delivery mark — it is clear who received it and who did not.
Pause and resume
Sending can be paused: the broadcast stops immediately. Later it can be resumed from where it stopped — nobody receives the message twice and nobody is skipped.
The scheduler
The scheduler holds the application’s jobs: delayed messages, reminders and automatic scenario runs by days of the week and time. Jobs survive a server restart. And while a bot is stopped, they are not lost — they wait for the bot to work again.
Next: numbers on broadcasts and the operators’ work — in the Analytics & Logs section, working with people — in Inbox, and running a scenario on a schedule — in Flow Nodes.