Missed calls: who calls back, and when

What happens after a call is missed?

The full chain, step by step. Nobody has to remember it or switch it on by hand.

1. 01

   The phone system reports the call

   Omnia Lab listens for call-completion events. If your PBX does not send them, the platform polls the phone system every 2 minutes. A missed call is never lost to a silent integration.

2. 02

   A Call Back task appears

   The task is created in your CRM for the rep who owns the deal, due in 30 minutes. Reminders fire twice: 15 minutes before the deadline, and at the deadline itself.

3. 03

   Nights stay quiet

   A call missed overnight does not buzz anyone's phone — Telegram stays silent. The deadline is set to the start of the working day plus 30 minutes, so the task is simply waiting in the morning plan.

4. 04

   No duplicate pile-up

   If the deal already has an open task with a deadline within 45 minutes either way, no new one is created. Three missed calls in a row do not become three identical reminders.

5. 05

   A conversation closes the task, not a dial

   A connected call of 15 seconds or longer clears the task automatically. Five to eight seconds of ringing does not count, so "I tried calling" no longer closes anything.

6. 06

   Postponing is visible

   If someone keeps moving the deadline, it shows: two postponements or more on one task raise a separate signal in the Important notifications chat. Quietly pushing the task to the evening does not work.

7. 07

   A trail stays behind

   The Done button works straight from Telegram: it closes the task in the CRM and leaves a record. Only the task owner or a whitelisted admin can press it. The call and any change of owner land in the single communication history for that deal.

What deadlines and thresholds does Omnia Lab use out of the box?

This is how the loop works out of the box. Stages, trigger words and conversation rules are tuned per company, and any of the 33 modules can be switched off; a change in the admin panel applies in under 60 seconds, with no restart.

Call Back task deadline

30 minutes after the missed call

Call missed overnight

start of the working day + 30 minutes

Connected-call threshold

15 seconds of conversation

Duplicate guard window

45 minutes either side of an open task's deadline

Call Back reminders

15 minutes before, and at the deadline

Polling a PBX without events

every 2 minutes

Postpone button on a rep's own commitments

+1 hour; past the end of the day, 10:00 tomorrow

Postponement signal

2 postponements or more

Reminder lifetime

never longer than 48 hours

Evening digest for the head of sales

20:50

Why do missed calls get lost?

Most sales teams hit these before they build a real process.

• Control lives in the rep's head. Right after the call he remembers; by lunch he does not; by evening the call is buried under twenty other things.
• Dialing counts as done. The rep dials, hears eight seconds of ringing, closes the task — and the customer still has not spoken to anyone.
• The first nudge goes to the team chat. Public pressure before the deadline has even passed teaches people to hide problems instead of fixing them.
• Night calls either wake everyone up or quietly pile up. You end up with an irritated team, or a morning backlog nobody owns.
• One customer calls three times and generates three identical tasks. Reps stop reading reminders because reminders became noise.
• The PBX sends no events, so half the missed calls never reach the CRM. The team finds out from a customer who "called you yesterday".
• Calls and chats are tracked in separate systems. The customer fails to reach anyone, writes in a messenger, and sits there unanswered because that is "a different system".

What does the system deliberately not do?

These limits are the point. Without them the whole loop becomes noise people mute.

• It does not post to the team chat early. For a rep's own commitments the team chat only comes in once the task is an hour overdue; before the deadline the conversation stays private.
• A short call on its own is never treated as a failure. The task simply stays open, and the judgement stays with the head of sales.
• It does not nag forever. A reminder never lives longer than 48 hours, and overnight escalation stages are cancelled rather than stacked up for the morning.
• It does not go silent on failure. The rule is fail-open: anything that breaks is resolved in the customer's favour — the lead is assigned, the task is created, nothing is hidden.
• It does not credit the wrong person. If someone other than the deal owner picked up, the score and the follow-up task go to whoever actually spoke.

How does a missed call fit the rest of the lead's path?

Call-back control plugs one hole. Omnia Lab runs the whole path, so customers do not fall between channels.

• An unanswered message climbs an escalation ladder at 5, 10, 15, 17 and 20 minutes. Ten minutes is a private nudge to the rep; twenty minutes reaches the head of sales.
• Customer promises become tasks too. "I'll look at it in an hour" creates a Customer promised to return task due at their time plus 30 minutes, and the customer coming back closes it on its own.
• Follow-ups on silent leads run at 1, 3, 7 and 30 days as one private digest at 15:00, not a scatter of pings.
• A flow watchdog checks for silence: more than 3 hours with no inbound customer messages during working hours raises an alert, so a broken integration surfaces before the team notices.
• Leads are only routed to people actually on shift. The rota syncs from a Google Sheet every hour.
• The manager directory is the source of truth. A deal with an unknown owner generates no pings and never goes into paid analysis.
• Deals created by a call with no chat history are covered as well: every day at 10:00 deals of departed reps are reassigned, up to 25 at a time.

What do the numbers look like after rollout?

The first four rows are before-and-after measurements at live customers, one of them a premium car dealership. The last two come from outside research, with the source named in the row.

Median first response to a customer

from 32 minutes to 6.5 minutes

Share of deals with a prepayment

from 4—7% to 13%

Revenue

+33% in 4 months with no extra headcount

Rollout time

3—5 days

Speed and lead quality

responding within an hour yields 7x more qualified leads than an hour later, and 60x more than a day later (Harvard Business Review, "The Short Life of Online Sales Leads", 2011, 2,241 companies)

Persistence

93% of deals close by the sixth touch, yet half of all leads never get a second call (Velocify, about 3.5m leads)

We do not name customers. During the audit we show the measurement method so you can repeat it on your own data.