Broadcast consent in a chatbot: two consents, a tag and a stop word

Two consents, a tag, a stop word

The template asks for two consents separately. Since 1 September 2025, consent to the processing of personal data is drawn up separately from other documents (Part 1 of Art. 9 of 152-FZ), and advertising over telecommunication networks needs the recipient’s own prior consent (Part 1 of Art. 18 of the Advertising Law, 38-FZ), so they are not combined into one button. Informational messages — a changed timetable, a rescheduled meeting — are usually not advertising; promotions, discounts and paid services are. Ultimately it depends on the content of the message.

The first question names the operator, the data (name and messenger ID), the purpose, the term — until withdrawn — and how to withdraw, and ends with a link to the policy and “Do you agree?” with the buttons “Согласен” (I agree) and “Нет” (No). Fill in your organization’s name and the link: the policy does not replace the content of the consent itself. “Согласен” adds the согласие-пдн (data consent) tag, “Нет” replies “OK, without consent we don’t send mailings” and removes the рассылка (mailing) tag if it was there. Anyone who has already agreed won’t see the first question: a “Condition” on the согласие-пдн tag goes straight to the second. The button tap is saved in the conversation history together with the question text and the time.

The second question is consent to advertising from a named sender: “[Organization name] may send you advertising messages — promotions, discounts, new services. Do you agree? You can unsubscribe at any time — just write ‘stop’” with the buttons “Yes” and “No”. “Yes” → “Action → add tag” рассылка (mailing) → “Done, you’re on the list”. “No” doesn’t set the tag; it removes it if it was already there: a refusal after consent is still a refusal.

The words «отозвать согласие» (withdraw consent) or «удалите мои данные» (delete my data) remove both tags, reply “Your request to withdraw consent has been received. Mailings have stopped…” and hand the conversation to a staff member. Removing a tag does not stop processing: the contact card and the conversation remain until they are deleted. Deleting a contact in “Contacts” erases the card, conversations and messages; deals and payments stay in the logs without a link to the person. What to delete and what may be kept on other legal grounds is decided by the operator — your organization.

Unsubscribing is two “Keyword” triggers, both leading to “Action → remove tag” and the message “OK, we won’t send news”. «стоп» (and stop, /stop) — as the whole message, in “exact match” mode, so as not to unsubscribe someone who wrote «автостоп» (hitchhiking); «отписаться» and «отписка» (unsubscribe) — anywhere in the phrase. The word «подписаться» (subscribe) asks the questions again — data consent is not requested a second time. The stop word works from anywhere in the conversation, even in the middle of another flow. The exception is a flow with an “Any message” trigger created before this template: outside flows it takes the message first, and “stop” won’t unsubscribe. Make a copy of that flow, enable the copy and disable the original — flows are checked in creation order, and the copy will come after the consent flow. While the conversation is with an operator, the bot is silent and the operator reads “stop”: they remove the tag on the contact card.

From then on, the рассылка tag is the audience. In “Contacts” it’s visible on every contact, and a “Condition” in other flows can check it before sending anything. How to build a tag system for several broadcast topics — in the article on tags as segmentation.

How to send and what broadcasts lack

The sending itself happens in the “Broadcasts” section (Basic plan, 650 ₽/month per bot): text with variables like {{name}}, an audience by tags, a scheduled start for a date and time, stopping mid-way, sent/error statistics. Sending goes through a queue; messages go out one by one with a short pause — no faster than 20 per second. Broadcasts have no media or buttons — text only; the call to action is a trigger word (“write PRICE”) that starts a flow.

Trigger chains like “a day after the material” are built not in “Broadcasts” but in a flow with “Pause” and “Condition” blocks: see the article on trigger chains. Channel specifics — broadcasts in Telegram and broadcasts by a MAX bot. Open the template in your account.