Free audit ↗
Classifieds

Marketplace auto-replies wreck your response time

Omnia Lab is a control system for the sales team, running on top of your CRM — Bitrix24, amoCRM or any other. Your response clock starts on the customer's first real message: platform notices stay in the deal history but never reach the routing queue or the reports.

· · Author: Dmitry Marenich

A lead from a classifieds site often arrives with no words from a human in it. All it holds is a system notice: "the user viewed your number", "we reminded the other party". Your CRM reads that as an inbound message, so the first-response clock starts before anyone has asked anything. Omnia Lab tells a platform's boilerplate apart from a real person's message: a notice never opens an SLA, never enters the pending-replies digest and never distorts response time. A card with nothing but service text waits in deferred quarantine, and any real text from the customer puts it straight back into play.

Why do empty classifieds leads cost you money?

The volume of notices is not the problem. Treating them as a customer is.

  • The first-response clock starts on a system notice. A rep shows up as overdue before anyone has asked a question.
  • An empty card gets handed out like a real lead. Someone picks it up and writes into the void.
  • The pending-replies digest fills with cards nobody can answer. The person actually waiting gets buried.
  • Your average response time stops meaning anything. It is dragged down by leads that contain no question.
  • When the marketplace integration breaks, nobody notices. The stream of "messages" keeps flowing, it just has no people in it.

What happens to a marketplace lead inside the system?

The timings are the same for every source. The content check is what kicks in on marketplaces.

  1. 01

    The deal is created

    This starts the lead-pickup measurement: from deal creation to the first real contact with the customer. Only working seconds count, and the measurement caps at 3 days. Response time to a message is counted separately, starting from the customer's first live text.

  2. 02

    Content check

    The system looks for text written by a person. Platform notices — "the user viewed your number", "we reminded the other party" — do not count as a customer message. They stay in the deal history all the same.

  3. 03

    Empty card goes to quarantine

    If the entire content is a service card from the platform, the lead is not handed to the team. It waits in deferred quarantine for the customer's first real word.

  4. 04

    Real text goes to the priority chat

    A lead with a human question lands in the new-leads priority chat with a Take button. If nobody takes it, it is routed by the shift schedule — only to reps who are actually on shift.

  5. 05

    Escalation ladder: 5 / 10 / 15 / 17 / 20 minutes

    With the customer still unanswered: 5, 15 and 17 minutes go to the team chat, 10 minutes to the rep's DM, 20 minutes to the manager's DM and the managers' chat. One reply from the rep closes the measurement and clears the whole chain.

  6. 06

    Hourly digest from 10:00 to 21:00

    Who is waiting right now, with buttons per customer, up to 15 of them. The digest never hides a waiting human because of the deal stage.

  7. 07

    Night and morning

    At night escalation steps are cancelled rather than postponed, so nobody walks into an avalanche. Overnight leads arrive as one digest at 10:05, not as ten separate pings.

What counts as a real message and what doesn't?

The call is made on the content of the message, not on the source it came from.

"I looked up your number and couldn't get through"
A live message. A person typed it, so the SLA runs and the lead is handed out.
"The user viewed your number…", "we reminded the other party"
A platform notice. No SLA, no digest entry, no effect on response time. It stays visible in the history.
A photo or file from the customer
A full message. Someone sending a car photo or a document is waiting for an answer.
A sticker
Does not start the response clock.
A message that is only "ok" or "thanks"
Closes the thread and starts no clock.
"Ok, I'll do it a bit later"
The same word inside a real sentence means a live customer, so the SLA runs. "Ok?" counts as live too.
An unclear case
Doubt always goes the customer's way: the lead is treated as live and handed out.

What does the system deliberately not do?

  • It does not strip platform notices from the thread. The trace stays, it simply is not counted as something the customer said.
  • It does not hide a lead for good. Quarantine is deferred: any real text from the customer wins and returns the card to the team.
  • It does not resolve doubt against the customer. Fail-open is the rule: on any failure the lead is routed and the filter switches off rather than hiding data.
  • It does not stay quiet when the stream dies. More than 3 hours with no customer messages during working hours triggers an alert. That usually catches a broken integration before the sales floor does.
  • It does not take the final call away from the manager. Every response-time measurement has a Do not count button with an audit trail of who excluded what.

What makes sales reports show the wrong numbers?

  • Timing the reply from a system notice. Your team median then depends on how many people viewed your phone number, not on how the team works.
  • Measuring from the first message instead of the first question. "Ok" at 12:00, a question at 14:00, an answer at 14:05 is 5 minutes, not 2 hours. The false-start filter counts it that way.
  • Silencing the noise by muting the whole channel. The live questions disappear along with the notices, and the deals go with them.
  • Cleaning empty leads by hand at the end of the day. By then they have already skewed the digest and the response-time report.
  • Counting conversion with the junk included. Spam stages and deals with "spam" in the name are excluded, otherwise the funnel shows fiction.

What changes in the numbers after rollout?

Measured before and after rollout at an active client, a premium car dealership.

Median first response to a customer
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, running on top of the CRM you already use

Why speed matters at all: Harvard Business Review ("The Short Life of Online Sales Leads", 2011, 2,241 companies) found that answering within an hour brings 7 times more qualified leads than answering an hour later, and 60 times more than answering a day later.

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

Marketplace auto-replies are ruining our response-time stats. Can that be fixed?
Yes. Platform notices never open an SLA, never appear in the hourly digest and never enter the response-time measurement. Pickup time runs from deal creation to the rep's first real contact, while response time runs from the customer's first live message — the false-start filter keeps a notice or an "ok" from moving the starting point. The notices themselves stay in the deal history, so nothing is lost.
What happens to a lead where the customer only wrote "I viewed your number and couldn't reach you"?
That is a live message and the system reads it as one. The lead goes to the priority chat with a Take button and runs the normal 5 / 10 / 15 / 17 / 20 minute escalation ladder. A missed call also creates a Call back task due in 30 minutes, and a real conversation of 15 seconds or more closes it automatically.
A card went to quarantine but the customer turns out to be real. Do we lose them?
No. Quarantine is deferred, so the moment any real text arrives the lead returns to the team and follows the normal path. Doubt always goes the customer's way: if the check fails, the lead is handed out rather than hidden.
Do we have to replace our CRM?
No. Omnia Lab runs on top of the CRM you already have. The main integration is Bitrix24: deal events, tasks, timeline comments, custom fields, pipeline and stage changes. amoCRM is on the integration list as well. Messengers and open channels, telephony, Telegram, Google Sheets and the classifieds feed into the same loop.
How long does setup take, and can we switch on only the marketplace filter?
Rollout takes 3—5 days. The admin panel holds 33 modules with individual toggles, so you can start with what you need now and add the rest later. All 85 settings apply in under 60 seconds without restarting anything.
How do we know the marketplace integration has gone down?
A stream watchdog handles that. If no customer message arrives for more than 3 hours during working hours, an alert goes out. It usually catches a broken integration before the sales team notices anything.

Read next

Let's look at your classifieds leads

The free audit takes 3—5 days. We go through your real leads from Avito and other platforms: how many are empty cards, what your response clock actually starts on, and what your true first-response median looks like. You get the findings with numbers. The rollout decision comes later, at your own pace.

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