Free audit ↗
Follow-through

Your reps forget to call back, and forget what they promised

Omnia Lab is a sales control system that runs on top of your CRM — Bitrix24, amoCRM or any other. Missed follow-ups are a bookkeeping problem, not a discipline one: every promise gets an owner and a deadline, and whatever slips past it reaches the sales manager by name.

· · Author: Dmitry Marenich

A dropped promise never looks dropped. The deal is open, the rep remembers the conversation, and the quote still hasn't gone out. The customer who said "call me after three" is still waiting. The fix isn't more discipline, it's bookkeeping: every commitment, yours and theirs, becomes a task with a real deadline. Omnia Lab creates that task, reminds the rep before the clock runs out, and closes it once the work actually happens.

Why do sales reps forget to follow up?

This is a systems problem wearing a people problem's clothes.

  • The promise is spoken out loud. It lives in a chat thread and a conversation, and in no CRM field — so as far as your system knows, it never happened.
  • A rep carries dozens of open deals. Three are top of mind. The rest run on memory and sticky notes.
  • Deadlines come out fuzzy: "in an hour," "tomorrow," "sometime this week." That doesn't go in a calendar, so it doesn't go anywhere.
  • Nobody logs what the customer promised. "I'll decide by Friday" — and Friday passes, because that task belonged to no one.
  • Manually created tasks survive until the first busy day. They get pushed, pushed again, then sink into a pile of overdue items nobody reads.
  • Managers find out about the missing quote when the customer has already bought somewhere else.

What counts as a commitment?

A commitment is anything said out loud with a time attached, no matter who said it. Your side: send the quote, prepare options, call back after approval, email the contract. Their side: "call me tomorrow afternoon," "I'll review the numbers by Friday," "I need to talk to my wife and I'll get back to you." Most teams track the first list and ignore the second. The second is where deals quietly die. When a customer picks the time themselves, calling at that time isn't pushy. It's keeping your end of something you both agreed to.

How does a spoken promise become a closed task?

Same sequence for a web form, a WhatsApp thread, an email, or a phone call.

  1. 01

    Capture the commitment

    The system watches messages, emails, and conversations on the deal and pulls out promises from either side. Reading conversations is one input signal here, not the point of the product. What matters is that a promise was made, not how smoothly it was delivered.

  2. 02

    Turn plain speech into a deadline

    "In an hour" becomes a timestamp. "Tomorrow morning" becomes a specific hour tomorrow. Promises made at night or over the weekend land on the next working morning instead of firing at 2 a.m.

  3. 03

    Assign an owner

    The commitment becomes a CRM task with a person and a due time. Customer promises get assigned to the rep too, because calling at the agreed hour is the rep's job.

  4. 04

    Remind before, not after

    The rep gets a Telegram nudge ahead of the deadline. One message per commitment, replacing the previous one rather than stacking on top of it.

  5. 05

    Close on evidence

    The quote email goes out, a call of real length connects, the customer replies in chat — and the task closes itself. Nobody files a status update to prove work the data already shows.

  6. 06

    Escalate in steps

    Deadline passed with no action, and the rep gets a second nudge. Still nothing, and the manager gets a message naming the customer and quoting the promise.

  7. 07

    Roll it into the numbers

    Every commitment lands in reporting: how many were made, how many were kept on time, where things slipped. Broken out per rep, not averaged into mush.

How much do slow replies and missed follow-ups cost?

A forgotten promise is silence with extra steps. The cost of silence has been measured by people other than us.

  • Responding within an hour produces 7x more qualified leads than responding an hour later, and 60x more than waiting a day. Harvard Business Review, "The Short Life of Online Sales Leads," 2011, based on 2,241 companies.
  • Cutting wait time from 30 minutes to 5 raises the odds of qualifying a lead roughly 21x. James Oldroyd, MIT Sloan.
  • 93% of deals close by the sixth touch, yet half of all leads never get a second call. Velocify, roughly 3.5 million leads.
  • Read together, those numbers say most losses aren't lost to a competitor. They're lost to a conversation that never happened.

What results do clients see after rollout?

Measured before and after rollout. We don't name clients.

Median first response time
32 minutes, down to 6.5 minutes
Deals with a deposit
4—7%, up to 13%
Revenue over four months
+33%, no new headcount
The client
a premium car dealership — same team, different operating rhythm
Time to roll out
3—5 days, on top of the existing CRM

Before-and-after measurements at active clients.

Why don't policies and reminders fix this?

Almost everyone tries these before they try bookkeeping.

  • Write a policy that says "log every commitment in the CRM." It holds for three weeks while someone watches, then survives only with your most organized reps.
  • Create tasks called "follow up" with no due date. A task without a time can never be late, so it never means anything.
  • Alert on everything. When every ping matters, none of them do, and the important one drowns with the rest.
  • Close tasks based on what reps report. Self-reported status is always sunnier than reality, and the manager burns an evening cross-checking it.
  • Buy speech analytics and expect it to solve this. Call analysis tells you how a rep sounded. It won't tell you the lead sat unassigned overnight, or that the promised quote never went out.
  • Track only your own promises. Half the stalled pipeline is customers who said "call me Thursday" and never got a call.
  • Replace the CRM. The CRM isn't lying — it faithfully stores whatever was entered, and the promise was never entered.

What else does the system track besides promises?

Commitments are one loop of several, and they work better together. Omnia Lab assigns incoming leads by shift schedule, so a request that arrives at midnight has an owner before morning. It measures first response time across every channel and escalates to the rep first, the manager second. It converts missed calls into dated tasks. It reminds reps about the next touch as a deal goes cold. It filters spam and off-target inquiries so they stop eating time and skewing your numbers. It reviews how deals get closed — a "lost" or "spam" with no real reason goes back into the pipeline. All of it runs on top of your CRM, whether that's Bitrix24, amoCRM, or something else, connected to your phone system and messaging apps. You don't replace the CRM, and you don't hire anyone.

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

A rep says "I'll send it tonight" on a call. Will the system actually catch that?
Yes. The system reads the thread and the conversation for commitments, including who made them and when they're due. "Tonight" becomes a specific time today, and the task lands on that rep. If the wording is genuinely vague, the system picks a sensible deadline and the rep can adjust it in one tap.
If the customer asks for a callback in an hour, whose task is it?
The rep who took the call. A customer's promise is your team's obligation: they named the time, so a call at that time is expected rather than pushy. Requests made late at night move to the next working morning.
How does a task close? Do reps have to report back?
No. Tasks close on evidence — the email went out, a call of real duration connected, the customer replied in the thread. Manual closing exists as a fallback, but the normal path is that reps do the work and the system notices.
Won't this bury the team in notifications?
One live commitment gets one message. A new reminder replaces the old one instead of piling on, and completed items disappear on their own. If the volume ever feels heavy, that's a real backlog showing itself, not an alerting problem.
We use Bitrix24 and we're not switching. Is that a problem?
No. The system runs on top of your CRM rather than replacing it. Tasks, fields, and deal history stay where they are, and commitments get written into the same place. The same applies to amoCRM and other systems, plus connections to your phone system and messengers.
How long does setup take and what do you need from us?
Rollout takes 3—5 days. Before that we run a free audit over 3—5 days: we look at where leads and commitments are actually falling through, and show you the numbers before you commit to anything. We need access to your CRM and phone system, and half an hour with whoever runs the sales floor.

Read next

Start with a free audit

Give us 3—5 days with your deals, messages, and calls, and we'll show you how many commitments were dropped last month. It's free and there's no obligation — if you're happy with what you see, you're free to change nothing. If you'd rather fix it, rollout takes another 3—5 days on top of your existing CRM.

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