11 ready-made scenarios for your chat

11 practical rules for everyday chat tasks

These are teaching examples from everyday chat life, not accounts of specific customers. Use your own topic names, links, and replies. Create each custom command in the editor before trying it.

Start in a test group or with a narrow condition. This is especially important for warnings, deletion, and automatic admission.

1. Support gets another payment question

Situation: a service administrator explains the same steps several times a day. You want people to get the standard instructions immediately.

Set up:

• Type: trigger. Event: chat message, with edits off.
• Topic: Support. Message type: text.
• Text condition: contains the phrase “how to pay.”
• Action: send the instructions to the current topic. Add a button leading to your payment or help page.

Expected result: “Can you tell me how to pay for my subscription?” in Support gets the instructions.

Should not match: the same phrase in Off-topic, or “How do I change my password?”

Add an OR alternative for “payment won't go through.” The bot does not automatically guess every way of asking the question.

2. Someone writes at night and expects a tutor's reply

Situation: support works weekdays, but members write around the clock. You need to explain when the team will return.

Set up:

• Trigger on a message in Support, with edits off.
• Text contains “how to pay.”
• Schedule: weekdays, 07:00–14:59 UTC. The final minute is included, so the after-hours reply starts at exactly 18:00 Moscow time.
• Enable Run outside this time.
• Action: send a reply to the current topic.

Expected result: a matching question at night gets this explanation.

Should not match: the same question during working hours. Reaching the evening start time does not itself trigger a message.

If you enable both this example and the previous one, limit the regular instructions to working hours. Otherwise, both replies may arrive at night.

If the period is already set in your chat's closing hours, use Closing hours without Run outside this time instead of a separate schedule, and adjust the reply to your hours. The bot still needs an event: this filter does not let people write in a closed chat. Empty closing hours or identical start and end times should not match.

3. A PDF submission needs an assignment reminder

Situation: tutors receive homework files but cannot always tell which lesson they belong to.

Set up:

• Trigger on a message in Homework.
• Message type: document. File type: .pdf or application/pdf.
• Action: send a reminder to the same topic.

Expected result: a PDF in the selected topic gets a reminder.

Should not match: a photo, or a PDF in another topic.

This simple version replies to any matching PDF, even one that already has an explanation. The bot does not read the assignment or confirm that a tutor has reviewed it.

4. A long voice message arrives in Support

Situation: someone records a detailed account, but the team first needs to understand what happened and how urgent it is.

Set up:

• Trigger on a message in Support.
• Message type: voice message. Duration: at least two minutes.
• Action: ask for a short written summary.

Expected result: a seven-minute voice message gets the reminder.

Should not match: a voice message under two minutes, plain text, or a video message.

Start by helping, not deleting. This example does not transcribe the recording or judge what was said.

5. A moderator wants to issue a warning

Situation: Anna sees a personal attack in Ilya's message. She makes the decision; Combot helps carry it out with a familiar command.

Set up:

• Command: /team_warn; Command target: Reply target.
• Triggered by: Telegram admins. If needed, exclude administrators from the people who can receive a warning.
• Actions: Warn user; Apply to: Replied-to user.

Anna chooses Reply on Ilya's message and sends /team_warn.

Expected result: Ilya receives the warning.

Should not match: a call from a regular member. Also try sending the command without a reply: it should not warn Anna herself.

If you add deletion of the command message, /team_warn disappears. Ilya's message does not. Before enabling the rule, check what your chat does when warnings accumulate.

6. A member helps a newcomer

Situation: Ilya explains an assignment to a new student. A tutor wants to recognize the helpful answer.

Set up:

• Command: /reward_member; Command target: Reply target.
• Only Telegram admins can call it.
• Action: change XP by 25, applied to the user in the replied-to message.
• Optionally add a REP change of 1. Enable the required features in the chat.

The tutor replies to the helpful message with the command.

Expected result: Ilya receives 25 XP, not the tutor.

Should not match: a command from a regular member.

A repeated command can give another reward. Agree with the moderators who recognizes answers if you do not want duplicate rewards.

7. Organizers admit guests through an invitation

Situation: an open class has its own invitation link. Requests through it can be approved while other requests remain for manual review.

Set up:

• Trigger on a join request.
• Source: this class's specific invitation link.
• Action: approve the request.

Expected result: a request through the selected invitation is approved.

Should not match: a request through another link or one with missing source information.

People can forward the link. This example does not verify payment, identity, job title, or membership in an organization.

8. A member invites a friend to the community

Situation: Ilya invited a friend. A moderator has checked that they joined and wants to thank Ilya with a small XP reward.

Set up:

• Enable XP in the chat.
• Command: /invite_thanks; Command target: Reply target.
• Only Telegram admins can call it.
• Action: add 10 XP to the user in the replied-to message.

After checking the referral, the moderator replies /invite_thanks to Ilya's message, not the newcomer's.

Expected result: Ilya receives 10 XP.

Should not match: a call from a regular member, or the friend's join without a moderator's command.

A person checks the invitation here; Combot awards the points on their command. Keep track of who has already received the bonus: repeating the command can add another 10 XP.

9. The team checks off tasks before a webinar

Situation: organizers share one checklist and want to notice progress without constantly watching the list.

Set up:

• Connect a log channel and copy the direct link to the checklist.
• When: Checklist tasks done.
• Condition: the link to this exact list, without ?comment=….
• Action: send a log-channel message. An Open plan button links to the same checklist.

Expected result: a change to the selected checklist produces a notification. Select the checklist itself, not the separate service message about the change.

Should not match: a completed task in a neighboring list, even in the same topic.

Don't say “Everything is ready”: it might be just one completed task. If you do not need a notification history, enable deletion of this send action's previous reply.

10. Editors follow reactions to posts

Situation: the team wants a signal about linked-channel posts that currently have 20–30 👍 and ❤️ reactions combined.

Set up:

• When: Reaction count. The log channel is connected and accessible to the bot.
• Count only 👍 and ❤️. Minimum: 20. Maximum: 30.
• Action: send a notification to logs and delete this send action's previous reply.

Expected result: 12 👍 and 10 ❤️ match because their total is 22.

Should not match: a total of 19 or 31. Other reaction types do not contribute to this sum.

The next matching update can send another notification. Cleanup replaces this action's previous message but does not prevent repeat runs or keep a separate reply per post. This is not a one-time notification for first reaching 20, nor a reward for the “twentieth member.”

11. A club wants varied welcomes

Situation: new people join a small club, and the team wants to greet them with a few different short messages.

Set up:

• Trigger on a new member.
• Three send actions, each with its own welcome.
• Mode: Random one. None of these three sends has the Always star.

For example: “Welcome! Tell us a little about yourself,” “Great to meet you! Start with the welcome note,” and “Hi! Explore the topics and join the conversation.”

Expected result: one of these welcomes is sent after a join.

Should not match: an ordinary message from someone already in the chat.

The next newcomer may get the same text. If Combot's standard welcome is already enabled, decide whether you need both so that newcomers are not greeted by several similar messages.