Inbound Lead Response

/ Why this matters

Speed is not a nice-to-have. It is most of the outcome.

Almost every enquiry you lose was won by somebody who answered first, not somebody who answered better. This is one of the most consistently replicated findings in sales research, and the size of the effect is larger than most owners expect.

What the research says

Contacting a lead within 5 minutes makes you 21× more likely to qualify it than waiting 30 minutes. Odds of making contact at all are 100× greater in the first 5 minutes than at 30.
Across 2.24 million leads, firms responding within an hour were 7× more likely to qualify the lead than those waiting just 60 minutes longer.
Wait 24 hours or more and you are roughly 60× less likely to qualify than a firm that answered within the hour.
The average business takes about 42 hours to respond — roughly 500× slower than the research says it should.

Sources: MIT / InsideSales lead response study; Harvard Business Review analysis of 2.24M leads. These are third-party industry findings about response time in general — not Launch7 client results. We have not published our own figures yet.

Interest has a shelf life. The window is minutes, and almost nobody is staffed to hit it.

What it costs you now

A DM arrives at 9 PM. You see it at noon the next day. They already booked someone else.
Six people got that same enquiry. The one who replied first got the call.
The form on your site sends an email nobody opens on a Sunday.
Four inboxes — Instagram, WhatsApp, the form, the phone — and only two get checked daily.

What changes

Every DM and form answered in under sixty seconds, any hour.
Qualified against your own criteria before it reaches you.
Booked straight into your calendar, with the context attached.
One thread per person, wherever they first wrote in.

/ Watch it work

The DM that arrives at midnight, handled by midnight.

Two enquiries, played at the speed they actually happen — including the one the agent refuses to answer.

Illustration, running

—Reply time

Illustration, not a live feed. Scene one: an 11:48 PM Instagram DM about a bridal lehenga is answered in nine seconds, qualified on date and budget, and booked into a Saturday fitting slot — with the owner notified and the qualification attached. Scene two: a 12:31 AM request for a price below the stated range, which the agent declines to negotiate and hands to a person with an 8 AM callback queued.

/ How it works

What actually happens in that first minute.

Trigger: A message lands on any connected channel, or a form is submitted.
Read: The agent identifies what they are asking about and matches it against your catalogue and availability.
Answer: It replies with the specific thing they asked for — not a holding message. If the answer is not in your data, it says so rather than inventing one.
Qualify: It asks the one or two questions you would have asked. Budget, timeline, location, whatever actually separates a real enquiry from a browser.
Book or hand over: A slot goes into your calendar, or the thread is escalated to you with everything already gathered.
Escalate: One rule it cannot override: when it is not sure, it stops and says "let me get the team on this."

/ What it's worth

Your numbers, not ours.

Move the sliders. Every figure below is arithmetic on what you enter — we have not measured your business, and we do not assume a rate on your behalf.

Enquiries a week 60

Average deal or booking ₹3,000

Share you answer late 30%

Turn on JavaScript to use the calculator.

Value in enquiries answered too late, six months—

M1M2M3M4M5M6

This is arithmetic on the numbers you just entered — not a result we're claiming. It assumes one in five late enquiries would have bought; change the sliders to match what you actually see. When we publish a measured figure it will carry the business, the category and the sample size.

/ Read deeper

Field note What a four-second reply actually changes about a DM 4 min read

/ Before you ask

Questions people actually ask.

Does it answer in the customer's language?

In whatever language they wrote in, Hinglish included — which is most of the real traffic.

What if it doesn't know the answer?

It stops. There is one rule it cannot override: "Let me get the team on this." A slow right answer beats a fast wrong one, and it can only speak from your catalogue, so it has nowhere to invent a price from.

Can it book straight into my calendar?

Yes, if your calendar is one it can reach. We wire that during the sprint. If you do not have one, the agent keeps the schedule itself.

Will customers know it's not me?

We do not pretend otherwise. It answers as your business, and the moment anything needs a person it hands over. Pretending to be human is how you lose trust the first time it slips.

/ The other agents

They hand off to each other.

Six specialists, one system, and none of them named after the model they run on — because that part gets replaced, repeatedly, and what they do for your business does not change when it does. Moving you onto the better one is the monthly Run’s job, not yours.

02Conversational Service Automation 03Revenue Recovery Operations 04Voice Deflection & Callback 05Scheduling & Retention Automation 06Outbound Campaign Automation

The enquiry that went cold while you were busy.