Automatic Telegram follow-ups: rules you switch on

When a workspace is created, its list of follow-up rules is empty: the CRM flags no lead and sends no follow-up message. Rules are managed in the Automations screen, “Follow-up Rules” tab, by members who have the permission to manage settings.

• “Add a rule” creates a rule you complete: condition, delay, priority and message.
• “Restore default rules” creates the four rules shown below, active and without a message: they flag leads, they write to no one.
• Each rule turns on or off in one click, and can be edited at any time.

A rule pairs a condition with a delay. The “No reply” and “Unanswered support” conditions skip leads at the end of the pipeline: archived, VIP, commission unlocked or upsell done.

Every 10 minutes, the CRM recalculates the leads matched by your active rules. Each matching lead gets the “To follow up” flag, the rule’s priority (high, medium or low) and, as the reason, the rule’s name.

• In the pipeline, the lead card shows “To follow up” with a dot coloured by priority.
• On the dashboard, the “To follow up” tile counts overdue leads and opens their list, sorted by priority.
• The flag goes away on its own when the condition is no longer true, for example after a new message or a confirmed deposit.
• A lead you flag or unflag yourself keeps your choice: the recalculation does not overwrite it.

An active rule with a message sends it to each lead who matches its condition. The CRM checks every minute for leads that reached the delay, and the message goes out in the lead’s Telegram conversation, from the account they wrote to.

• Once per lead and per rule. A lead who falls back into the same condition later does not get the same message a second time.
• No send to your history. Only leads who reach the delay after the message is saved receive it; leads already overdue are not all messaged at once.
• Private chats only. The message only goes to a lead in a private conversation, never to a group, a channel or a bot.
• One send queue per account. Follow-ups share the automations queue: one message at a time per Telegram account, with at least 4 seconds between two sends.

The message accepts the variables {prenom}, {nom}, {username} and {statut}. Once sent, it appears in the conversation as a message from your team.

To follow up at day 1, day 2 and day 7

A rule sends one message. For a sequence, create one rule per step, with the same condition and three delays: 1, 2 and 7 days, each with its own message. A lead who replies leaves the “Has not replied” condition, and the later rules do not write to them.

A disconnected account or a wait imposed by Telegram can make a send fail. The CRM then retries up to five times, 1 minute, 5 minutes, 30 minutes, 2 hours and 12 hours later. Before each retry, it checks that the follow-up still makes sense:

• if the lead no longer matches the rule’s condition, the send is cancelled;
• if the lead has written since the first attempt, the send is cancelled;
• after the last attempt, the follow-up is dropped for that lead.

Turning a rule off or emptying its message stops the sends. When you turn them back on, the CRM starts from that moment: only leads who reach the delay afterwards receive the message. Rules without a message keep flagging leads while they are active.

Follow-ups act after a delay. For a message sent the moment a lead changes stage, use stage automations. For the reply the closer writes to a lead who was followed up, the AI offers three reply suggestions. The number of leads to follow up also appears in the team analytics.