Speed to lead on WhatsApp, Instagram and live chat: answer every inbound message in five minutes

Speed to lead means the time between a person writing to you and getting a useful reply. A five minute target is realistic for WhatsApp, Instagram, Messenger and live chat if an agent answers first and a person owns the handoff. One hotel measured a median first reply of 41 seconds against 159 minutes when staff replied first, though that comparison is not like for like. We publish no conversion lift for faster replies, only what was measured.

Most speed to lead advice is written for form fills and phone calls. In messaging the clock is harsher and the habit is different: a person who wrote on WhatsApp expects a reply the way they expect one from a friend, and a person who commented on an Instagram post may have moved on before you see it. This post is a practical way to hold a five minute promise on those channels.

Where do inbound messages come from?

Four routes feed the same inbox, and each has a different delay built in.

• Direct messages on WhatsApp, Instagram and Messenger. The person wrote to you on purpose.
• Comments and story mentions on Instagram and Facebook. The person reacted in public, and a reply by direct message turns it into a conversation.
• The live chat widget on your site. The person is on the page now.
• Ad leads. A form on Facebook or Google. Sellinger polls Facebook lead form leads from a sheet every 60 seconds and Google Ads leads every 300 seconds, creates them as leads and contacts them by the campaign. Google Ads leads default to WhatsApp as the first channel.

The polling intervals are the first part of your speed budget: a Google Ads lead may wait up to five minutes before anything happens, so the polling alone can use the whole target. Know your own numbers before you promise one.

What slows the first reply?

Almost never the writing. It is the waiting.

1. Nobody is watching the inbox. Evenings, weekends and meetings. This is the biggest cause.
2. The message sits in the wrong place. A comment, a story mention, a message request folder.
3. The answer needs a lookup. Availability, a price, a stock level.
4. The sender needs permission. Someone has to approve a quote.
5. The first reply asks nothing useful. "Thanks, we'll get back to you" starts the clock again.

An agent removes the first, second and fifth. The third depends on what you connect it to. The fourth is a policy you control.

What did the hotel measure?

The Hotel Pirin case study is the only set of response times we publish for inbound messages, and it states what each number counts.

Read that table with the caveat the case study gives. Staff answered first only where the agent had not, which tends to be the harder threads, so the 0.7 against 159 is not a fair race. What it does show is the size of the gap a night or a weekend can open when only people answer.

It also shows where speed stops helping. Of 63 leisure guests, 8 booked, and the agent created no reservation. Staff, the owner or the reply desk closed most. After a guest was handed over to staff the wait ran from 3 hours to 14 days. A fast first reply just moves the slow part later in the conversation.

What does our own outbound data say?

On our own LinkedIn outbound, the agents' reply time fell from about 19 minutes to about 2 minutes over a year, yet meetings per conversation did not rise with it (case study). The list and the message were the bigger levers. That is outbound, where the person did not ask to hear from us, so it is not a rebuttal of speed to lead for inbound. It does support the same practical lesson as the post on speed as table stakes: answering fast keeps you in the game, and what you say and who takes over decides whether you win.

How do you hold five minutes?

1. Route every channel into one inbox, so nothing waits in a folder.
2. Let the agent answer first, from a knowledge base with your prices, hours, terms and rules. The Sellinger goal library has a goal for exactly this: respond to every inbound inquiry within 5 minutes, classify intent, and route it to the right sequence or team member.
3. Make the first reply useful. Answer the question and ask for the one thing you need next, such as dates, quantity or a phone number.
4. Set a quoting rule. In the hotel case, telling the agent to quote as soon as it had dates and party size raised the share of replies carrying a price from 50% to 92%.
5. Name an owner for the handoff, with an alert that reaches a phone and a clock: if a handed over conversation is unanswered for 30 minutes, escalate.
6. Measure from the person's first message, not from when you saw it, and report the median and the 90th percentile.

How do you audit your current speed in one afternoon?

Do not guess. Measure it with your own channels.

1. Send yourself test messages on each channel from a personal account, at six different times: a weekday morning, lunchtime, early evening, late night, Saturday and Sunday.
2. Record the time to the first useful reply, not the first automatic one. An auto reply that says "we will be in touch" does not count.
3. Read the last 30 real inbound threads and note the gap between the person's first message and your first reply. Take the median and the slowest three.
4. Mark where the time went. Was it waiting for someone to see it, waiting for a lookup, or waiting for approval?
5. Fix the biggest wait first. If most of the delay is nights and weekends, an agent that answers first fixes it. If most of it is approval, change the policy before you add software.

A small illustration, not a result. Suppose you receive 10 inbound messages a week and 4 arrive outside office hours. With only people answering, those 4 wait until the next working morning. With an agent answering first, all 10 get a first reply in minutes, and the person decides what to do next. What the 4 are worth is your number, not ours.

What should you not promise?

• Not "instant". Say five minutes and mean it. A promise you can only keep in the daytime is a bad promise.
• Not a conversion lift. We have no measured number for faster replies converting better and neither should your page.
• Not that nobody is a bot. If someone asks whether they are talking to an AI, answer honestly.

A checklist

• [ ] All inbound channels land in one inbox.
• [ ] I know the polling delay for each ad source.
• [ ] The agent answers first, from a knowledge base I tested.
• [ ] The first reply answers and asks one useful question.
• [ ] Handoffs have an owner, an alert and a time limit.
• [ ] I measure the median and the slowest tenth, from the first message.