Telegram notifications for a sales team
Omnia Lab is a sales operations system that runs on top of your CRM — Bitrix24, amoCRM or any other, and it talks to reps in Telegram. Alerts are split across six addresses, escalation steps at 5, 10, 15, 17 and 20 minutes, overnight leads as a single 10:05 digest.
· · Author: Dmitry Marenich
Omnia Lab is an operating system for a sales team: it runs a request from the moment it appears to the moment it turns into money, on top of the CRM you already have — and Telegram is where the rep works with it. Alerts only work if there are few of them and each one is addressed to a named person, so the system messages you only when a deal is actually waiting: a customer left unanswered for five minutes, a promised callback coming due, a missed call. A new reminder deletes the previous one, so a thread never turns into a feed. Chats are split by purpose, buttons carry permissions, and at 20:05 the service chats are wiped so tomorrow starts clean. Bitrix24 stays exactly where it is.
Which chats does a sales team need in Telegram?
The usual reason a team mutes alerts is that everything lands in one place. Different signals belong in different rooms.
- Sales team group chat
- Unanswered-customer pings at 5, 15 and 17 minutes, plus the hourly list of waiting customers from 10:00 to 21:00.
- Rep's direct messages
- The 10-minute ping on their own customer, promise reminders, the morning plan, the end-of-day review. Everything that does not need an audience.
- Head of sales, DM and chat
- The 20-minute step — the last one. Plus the 20:50 evening summary of promises and the daily deal report.
- "Important" chat
- For things nobody should scroll past. A promise deadline pushed twice or more raises a flag here, for example.
- New-lead priority chat
- Each new request arrives with a Take button. If nobody taps it, the lead is handed out by the shift schedule with its own response clock.
- Tech chat
- Integration failures and errors. The flow watchdog raises an alert when three working hours pass without a single customer message — usually a broken channel.
Pipelines and stages you want left alone go on an ignore list: no response clock, no digests, no pings there at all.
What arrives in the chats, hour by hour?
The schedule is fixed and visible from day one. Here is what arrives and when.
- 01
10:05 — overnight leads
Requests that came in at night arrive as a single digest, not ten separate messages. Escalation steps are canceled overnight rather than queued, so no avalanche lands in the morning.
- 02
10:00–21:00 — hourly waiting list
Every hour, the customers still waiting, with a customer button next to each — up to 15 of them. The list never hides a real waiting person because of a deal stage.
- 03
11:00 and 16:00 — "No next step"
Deals where the customer got an answer but no open task is left. These are the ones that die quietly.
- 04
15:00 — follow-up digest
One personal message with buttons: customers who have gone silent for 1, 3, 7 and 30 days.
- 05
18:00 — daily deal review
The head of sales gets a report that opens with "Needs attention today": priority from 70 up, ten deals maximum. Each rep gets a DM with one thing done well and one thing to work on.
- 06
20:00 — last waiting list
The final list of waiting customers for the day. Cleanup comes next.
- 07
20:05 — cleanup
The group chat and the Important chat are wiped. Only service messages go; anything a human wrote stays.
- 08
20:50 — evening summary for the head of sales
Who promised what and what is still undone. Nothing goes public before a deadline is missed.
- 09
20:59 — quarantine report
Confirmed spam moves to the cold pipeline and the head of sales sees the list. If the customer writes or calls later, the card comes back on its own.
How does a rep close a task without opening the CRM?
A rep closes the loop from the same place they read the reminder. Opening the CRM is a choice, not a requirement.
- Take — claim a new lead from the priority chat before the schedule hands it to someone else.
- Answered and No reply needed — clear the reminder and stop the response clock. Deciding not to reply counts as handling the lead.
- Done — closes the CRM task straight from Telegram and leaves a trace on the card. Only the task owner or a whitelisted admin can tap it.
- Snooze — moves the deadline by an hour, or to 10:00 tomorrow if the working day is over. Two pushes or more raises a separate flag in the Important chat.
- Did it and Not relevant — a one-tap answer to a recommendation so it stops hanging around.
- The customer button in the waiting list jumps straight into that conversation, no searching by name.
- Taps confirm instantly even when the CRM is slow to respond. Permissions are enforced: you cannot close someone else's task.
How do you keep a chat from turning into a feed?
The rule is simple: exactly one current message per deal lives in the chat. Everything else clears itself.
- A new reminder deletes the old one. The old message is removed only after the new one has been delivered, so a signal is never lost.
- A reply from the rep clears every reminder at once. A call, the No reply needed button and closing the deal all count as a touch, same as text.
- At night escalation steps are canceled, not postponed to morning. No reminder lives longer than 48 hours.
- Acknowledgement filter: a message that is only "ok" or "thanks" closes the loop. The same word inside a real sentence — "ok, I'll do it a bit later" — is a live customer, and the clock keeps running. "Ok?" is live too.
- A sticker does not restart the response clock. A file or photo from the customer is a full message; a file from the rep counts as a reply.
- Marketplace service notices like "the user viewed the phone number" never start a clock or enter the waiting list. They still stay in the history.
How do you know whose customer this is?
Each text carries the rep's name, so nobody in the group chat has to guess whose customer it is. The manager directory is the source of truth — a deal with an unknown owner produces no pings at all. New requests are handed out only to people on shift: the schedule is pulled from a Google Sheet and synced every hour, and anyone switched off from distribution is skipped. And escalation always runs bottom-up: the team first — 5, 10, 15 and 17 minutes — and the head of sales joins only at 20, never first.
What will the system deliberately not do?
Half the value of alerts is in what they never send.
- It does not take a rep's promise public early. A private ping 30 minutes before the deadline, another DM 15 minutes after it slips, and only past an hour late does the group chat hear about it.
- It does not ping about a promise already kept: before every reminder the AI rereads the conversation and closes the task on its own.
- It does not create duplicates. If an open task already has a deadline within 45 minutes either way, no second one appears.
- It does not wake anyone at night over a missed call. The callback task lands at the start of the working day plus 30 minutes; during the day it is simply the call plus 30 minutes.
- It does not count ringing as a call. A conversation of 15 seconds or more closes the callback task by itself.
- It does not scold the customer. A reminder about their own promise suggests a reason to reach out, not a "you said you'd get back to us".
- It does not fail quietly in its own favor. Any error is resolved in the customer's favor: the lead still gets assigned, the conversation still shows up, filters switch off rather than hide data.
What changed after rollout, in numbers?
Measured before and after rollout at existing clients, among them a premium car dealership.
- Median first response
- from 32 minutes to 6.5
- Deals with a prepayment
- from 4—7% to 13%
- Revenue
- +33% in four months, with no extra headcount
- Rollout time
- 3—5 days; setting up a new client takes 3—4 hours, and every module sleeps until you switch to live mode
- Tuning
- 85 settings in the panel, applied in under 60 seconds with no restart; 33 modules with individual toggles
Any alert loop can be switched off entirely — from the hourly waiting list to the evening cleanup.
Частые вопросы
- How do I set up sales alerts my team will not mute in a week?
- Three things matter: few messages, a named recipient, and a way to act without leaving the chat. One live alert per thread, the rep's name on every text, and a button for the action. The 20:05 cleanup wipes the day's service messages so the chat never becomes the pile people mute.
- How many messages will one rep get per day?
- It depends on lead volume, but the rhythm is fixed: a morning plan, the 15:00 follow-up digest, an end-of-day review, and pings only about their own customers who are genuinely waiting. Group chats add the hourly waiting list from 10:00 to 21:00 and the "No next step" block at 11:00 and 16:00. Overnight leads come as one digest at 10:05.
- Why is the first ping at 5 minutes?
- Speed decides more than the script. Harvard Business Review's "The Short Life of Online Sales Leads" (2011, 2,241 companies) found that responding within an hour yields 7 times more qualified leads than an hour later, and 60 times more than a day later. James Oldroyd at MIT Sloan measured roughly a 21-fold lift in qualification when the wait drops from 30 minutes to 5. Hence 5 minutes first, with the head of sales joining at 20.
- Can one rep tap a button on behalf of another?
- No. Done is limited to the task owner and whitelisted admins. Every tap leaves a trace in the CRM showing who acted and when, and it confirms immediately even if the CRM lags.
- What happens if twenty leads arrive overnight?
- Escalation steps are canceled at night instead of stacking up. At 10:05 one digest carries all the overnight leads, and the normal clock starts from there. The morning opens with a single message, not a hundred unread ones.
- Do we have to replace our CRM?
- No. The platform runs on top of the CRM you already use. Everything described on this page — tasks, timeline comments, custom fields, deal events — runs on Bitrix24, our main integration. amoCRM is on the list of CRMs we implement and configure; we scope that setup separately. Telegram alerts, tasks and comments all land on your existing deal cards, so reps keep working where they already work.
Read next
- Sales response SLA: a 5–20 minute ladderReps not answering customers? A response SLA that runs itself: escalation at 5, 10, 15, 17 and 20 minutes plus an hourly unanswered digest.
- Missed calls in sales: control and callbackReps forget to call back. Omnia Lab opens a Call Back task due in 30 minutes, moves overnight calls to the morning, and closes it on a real 15-second call.
- How to Train Sales Reps on Their Own DealsHow to train sales reps on their own deals: a private daily debrief, a four-block morning plan, and a Monday review where every claim carries a quote.
- Lead Routing by Shift for Sales RepsRoute leads by shift: hourly sync from your sheet, a Take button, routing only to reps on shift, and reassigning a departed rep's deals.
Free sales audit
We look at your conversations and calls from the past few weeks: where first-response time leaks, which promises never reach the customer, what gets closed as lost without a second look. The audit takes 3—5 days and costs nothing. You end up with a plain list of what to fix, whether or not we work together.