Every reply, click and sale in your Telegram pipeline comes with a few small chores: take the conversation, raise the priority, set a reminder, cancel the follow-ups. TeleBoost automations do them for you the moment the event happens. Write a rule once — when this happens, if these hold, then do that — test it on a real contact, and switch it on. Rules organize the work; they never write to your leads.
One readable sentence per rule: the event, the conditions that must hold, the actions to take.
Test a rule on any contact. See each condition, expected vs actual, and what would happen. Nothing is written.
Every attempt recorded — acted, skipped with the reason, failed or previewed.
Rules organize the work around a lead. What a lead reads is written by you or sent by a campaign you launched.
A lead replies. Now someone has to take the conversation, decide it's a hot one, bump its priority, set a reminder to follow up and move the contact to the right stage. A buyer pays — and the three follow-ups still scheduled for them have to be cancelled before one of them goes out and asks if they're still interested.
None of this is hard. It's just constant, and it's done from memory — which means it's done late, or by two people at once, or not at all. The chores that slip are never the dramatic ones; they're the quiet ones that leave a warm lead unassigned over the weekend.
The leads you lose aren't the ones you said no to. They're the ones nobody got around to.
Every automation is one sentence with three parts. When picks the event that starts it — a reply, a link opened, a stage change, a recorded sale. If narrows it down with conditions that must all hold: an engagement score above a threshold, a stage, a segment, a list, the account it came through. Then lists what the rule does, in order, up to eight actions.
There's no code, no expression language and nothing to escape: triggers, conditions and actions come from a fixed list, and a rule only stores choices from that list. It's deliberately bounded — closer to a well-labeled switchboard than to a programming tool — so a rule you read is exactly what will run.
Actions cover the housekeeping around a lead: assign the conversation to a team member, set the contact's owner or priority, move them to a pipeline stage, add or remove them from a list, create a reminder, open a ticket, cancel their scheduled follow-ups, send an in-app notification, or emit a webhook to your own endpoints.
What no rule can do is send a message. That's a choice, not a gap: a message to a lead needs sending quotas, quiet hours and a preview, and an automation fires without anyone looking. Follow-up sequences live in your campaigns, where every send respects your accounts' limits — and automations keep those sequences clean, stopping them the moment a lead buys or opts out.
A new rule starts switched off. Before you turn it on, pick a contact and run a test: each condition shows what the rule expects next to what this contact actually has, and the verdict lists exactly what the rule would do. Nothing is written — no priority changes, no ticket, no reminder.
Try it on a contact who should match and one who shouldn't. When both answers read right, flip the switch to Live. Changed your mind? Switch it off again; the rule and its history stay where they are.
An automation nobody can audit is one nobody trusts. Every attempt is recorded in the activity log: Acted, with what the rule changed; Skipped, with the condition that stopped it; Failed, with the error; or Preview, for a test. When a lead ends up with a priority you didn't expect, the answer is one line away.
Each event runs a rule once. If the same reply or click is delivered twice, the rule doesn't assign the conversation twice or open a second ticket. And a rule that breaks never takes its event down with it: the reply is still saved, the sale still recorded — the failure is simply logged for you to fix.
The fastest way to your first automation is a recipe: a ready-made rule you can install as it is or adjust before switching it on. Each one solves a chore most Telegram teams handle by hand today.
Rules belong to the workspace they're created in. In a team workspace, they run for everyone's conversations: assign replies to a specific member, give each new qualified lead an owner, get an in-app notification when a sale lands. In solo mode they stay on your own data.
Need the event somewhere else? The webhook action sends a signed automation.triggered event to the endpoints you've already registered under Settings → Developers (Pro and Business) — so a rule in TeleBoost can wake up your own tools without ever pointing at an arbitrary URL.
Questions
Something else on your mind? Write to us and a person will answer.
Starter, Pro and Business. In a team workspace, access follows the owner's plan, so every member can build and manage rules. A workspace can hold up to 60 rules, each with up to 10 conditions and 8 actions. The webhook action needs webhook endpoints, which are part of Pro and Business.
No. There is no send action, by design: a message to a lead needs sending quotas, quiet hours and a preview, and an automation runs without anyone watching. Use campaigns for follow-up sequences — they respect your accounts' limits — and let automations stop those sequences when a lead replies, buys or opts out.
No. A rule you create starts switched off. Test it on a contact first: the dry run shows each condition next to the contact's real value and lists what would happen, without changing anything. Switch it to Live when you're happy with the answer.
The event that triggered it is never affected — the reply is still saved, the sale still recorded. The failed attempt appears in the activity log with its error, next to the runs that acted or were skipped.
No. Each event runs a given rule once, so a reply or click delivered twice can't assign a conversation twice or open two tickets. Different rules listening to the same event each run once.
Automations are rules that run on their own, the moment an event happens, always the same way. The AI copilot and the MCP server act when you ask them to, in your words. They work well together: rules take care of the chores that repeat, the copilot of the requests that don't.
Automations are included on Starter, Pro and Business. Start from a ready-made recipe, test it on a contact you know, and switch it on when it reads right.