Free audit ↗
Response SLA

When reps stop answering customers: a response SLA that enforces itself

Omnia Lab is a sales-team control system that runs on top of your CRM — Bitrix24, amoCRM or any other. First-response time is enforced by an escalation ladder from minute 5 to minute 20 and an hourly digest of everyone still waiting; each new reminder erases the previous one.

· · Author: Dmitry Marenich

A customer writes at 10:14. The rep sees it at 13:40. By then the customer is talking to someone else. Omnia Lab runs a lead from the first message to the payment on top of the CRM you already use, and the first thing it refuses to leave to chance is the reply: a reminder hits the team chat at 5 minutes, the rep's private chat at 10, the head of sales at 20. One reply closes the timer and clears the whole chain, and at night escalation is cancelled instead of piling up for the morning. Nothing about the way your team works has to change.

How fast does the escalation ladder fire?

The clock starts on a customer message nobody has answered. Every step is addressed to a specific person, not to the room.

  1. 01

    5 minutes

    A reminder lands in the shared sales chat, tagged with the rep who owns the deal. Nobody gets to assume it is someone else's problem.

  2. 02

    10 minutes

    A private Telegram message to that rep, addressed by name. The nudge is now one-to-one — a chance to close it themselves before the head of sales is pulled in.

  3. 03

    15 and 17 minutes

    Back to the shared chat. Colleagues can see the thread is still hanging and pick the customer up.

  4. 04

    20 minutes

    The head of sales, privately and in the sales leadership chat. Up to that minute nothing has reached their desk.

  5. 05

    The reply

    Closes the timer and clears every reminder in the chain. A message, a call, the "No reply needed" button, or closing the deal all count as a touch.

How do you keep reps from drowning in alerts?

Notification chats die when they get noisy. This one stays short on purpose.

  • A new reminder physically deletes the previous one. Each thread has exactly one live message in the chat, not ten.
  • The old message is removed only after the new one is confirmed sent. Nothing disappears if Telegram is slow.
  • At night, escalation steps are cancelled, not postponed. The morning does not open with thirty overdue pings.
  • No reminder lives longer than 48 hours. Stale signals do not sit in the chat for weeks.
  • At 20:05 the shared chat and the alerts channel are wiped clean. Messages people typed themselves are never touched.
  • Leads that arrive overnight come back as a single digest at 10:05, not as a burst of separate pings.

What counts as a reply to the customer?

Counting "a message exists, so they replied" ruins the numbers. Every message is checked first.

  • A message that is nothing but "ok" or "thanks" closes the thread — the customer said goodbye.
  • The same word inside a real sentence does not. "Ok, I'll do it a bit later" is a live customer, and the SLA keeps running. So is "Ok?"
  • A sticker does not lift the SLA. A file or photo from the customer is a full message; a file from the rep counts as a reply.
  • Marketplace boilerplate — "the user viewed your number", "we reminded your contact" — never opens an SLA and never distorts response time. It still stays visible in the history.
  • A lead with no live customer text at all is held in quarantine instead of being pushed to the team. Any real text from a human wins, and any failed check is resolved in the customer's favour.
  • Pipelines and stages that should not be measured go on an ignore list — no reminders, no digests.

What are the default timings and thresholds?

This is how it works out of the box. Any block below can be switched off entirely — every module has its own toggle.

Escalation ladder
5 / 10 / 15 / 17 / 20 minutes
Who each step reaches
5, 15, 17 min — shared sales chat; 10 min — the rep privately; 20 min — head of sales and the sales leadership chat
Hourly unanswered digest
10:00 to 21:00, up to 15 customer buttons in one message
"No next step" block
11:00 and 16:00
Flow watchdog
more than 3 hours with no customer messages during working hours triggers an alert
New lead
a ping with a "Take it" button in the priority chat; on timeout it is assigned from the shift schedule
Pickup time measurement
starts when the deal is created, stops at the first real contact; working seconds only, capped at 3 days
Reminder lifetime
never longer than 48 hours
Evening chat cleanup
20:05

What does the head of sales actually see?

Every hour from 10:00 to 21:00 one digest of unanswered threads arrives, with a button per customer. The rule behind it is strict: the digest never hides a waiting human because of the deal stage — if the customer wrote, they are on the list. Twice a day, at 11:00 and 16:00, a "No next step" block goes out: deals where the customer got a reply but no open task remains. That is the quietest leak of all — on paper everything is fine, and nobody is planning to come back to that customer.

A separate flow watchdog runs alongside. If more than three hours pass during working hours with no customer messages at all, it raises an alert — which is how a broken messenger integration gets caught before the sales floor notices it.

What changes in the numbers after rollout?

The first three rows are before-and-after measurements at existing customers, one of them a premium car dealership. The last row is our standard rollout timeline.

Median first response time
from 32 minutes to 6.5
Deals with a prepayment
from 4–7% to 13%
Revenue
+33% in 4 months, with no extra headcount
Rollout
3–5 days; the free audit before it takes 3–5 days as well

Outside research points the same way. Answering within an hour produces 7 times more qualified leads than answering an hour later, and 60 times more than answering a day later (Harvard Business Review, "The Short Life of Online Sales Leads", 2011, 2,241 companies). Cutting the wait from 30 minutes to 5 raises lead qualification roughly 21-fold (James Oldroyd, MIT Sloan).

Why do response-time rules usually fail?

Almost every sales team has a "reply within 15 minutes" rule. It rarely holds, usually for one of these reasons.

  • The SLA lives in the manager's head. Nobody measures response time, so breaches only surface as customer complaints.
  • Every reminder goes to the shared chat. A week later people skim it; two weeks later they stop opening it.
  • The first miss gets called out in front of the whole team. Reps start hiding conversations instead of answering faster.
  • Nights and weekends pile up and land on Monday. The team drowns and stops reacting to any signal at all.
  • Time is counted from the first message in the thread instead of the last unanswered one. "Ok" at 12:00, a question at 14:00, a reply at 14:05 — that is 5 minutes, not two hours.
  • Marketplace auto-replies are counted as rep replies. The report looks clean and the customer is still waiting.
  • The digest is filtered by deal stage. A waiting customer vanishes from the report simply because the deal is formally "in progress".

Частые вопросы

Our reps already drown in notifications. Won't this make it worse?
Each thread carries exactly one live reminder — a new one deletes the old, so no feed builds up. The first step goes to the shared chat, the private message only comes at minute ten, and the head of sales is pulled in at twenty. At night escalation is cancelled, at 20:05 the chats are wiped, and overnight leads arrive as one digest at 10:05.
What exactly counts as answering the customer?
A message from the rep, a call, the "No reply needed" button, or closing the deal. A file or photo from the rep counts too. A customer message that is only "thanks" closes the thread, while the same word inside a real sentence does not — the SLA keeps running.
Do we have to replace our CRM?
No. Omnia Lab runs on top of the CRM you already use. Bitrix24 is the primary integration: it reads deal and message events, creates tasks, writes timeline comments and fills custom fields, without taking over your pipeline. amoCRM is on the list of CRMs we implement and configure — we scope that setup separately.
What happens at night?
Escalation steps are cancelled rather than postponed, so nothing queues up for the morning. A call missed overnight becomes a "Call back" task due 30 minutes after the working day starts, and Telegram stays silent until then. Leads that came in overnight are delivered as one digest at 10:05.
What stops a rep from just tapping buttons to make it stop?
Every reminder carries the rep's name, and permission to press a button is limited to the people it belongs to. Each press leaves a trace in the CRM. Real response time is measured separately and visible in the dashboard, where a single measurement can be excluded with a "Don't count" button — with an audit record of who excluded it.
How long does it take to go live?
Rollout takes 3–5 days. Technically a new client is deployed in 3–4 hours, and every module stays asleep until you switch to live mode. Stages, trigger words and conversation rules are tuned to your team: 33 modules with individual toggles and 85 settings that apply in under 60 seconds, with no restart.

Read next

Start with a free audit

We look at your conversations and calls from the past few weeks and calculate your real median first response time: where the time goes, how many leads never get an answer, which threads went quiet. The audit takes 3–5 days and costs nothing. You end up with the numbers — what to do with them is your call.

Получить бесплатный аудит ↗