Email response time in sales: why it is still the slowest channel
What to automate in the inbox and what to keep human.
· 5 min read · Editor: Max
Every few years someone announces that email is finished, replaced by chat, by messengers, by whatever interface arrived last quarter. Then you look at where business actually gets done. Quotes travel by email. Purchase orders travel by email. Procurement departments will not touch a WhatsApp thread when there is a contract at stake.
Email is not dead. It is slow. That is a different problem, and a fixable one.
The real failure is latency, not the channel
A message arriving in a shared inbox at 18:40 on a Thursday often sits until Monday morning. Nobody decided to ignore it. The person who handles pricing was travelling, the person who opened it assumed someone else had it, and by Monday the buyer has already had a conversation with two competitors.
Research on lead response has pointed in the same direction for years. The Lead Response Management study led by Prof. James Oldroyd found that the odds of qualifying a lead fall sharply once the first reply slips from minutes into hours. The Harvard Business Review article "The Short Life of Online Sales Leads" made the same point to a wider audience: most companies answer far more slowly than they believe they do, and the ones that answer fast are far more likely to reach a real conversation.
The mechanism is simple. When a buyer sends an enquiry, they are in a decision window: a problem in front of them, a tab open, attention to spend. Every hour closes that window a little.
A reply that arrives on Monday is not a slow reply. It is a reply to a different person, in a different mood, with different options.
What actually happens inside a shared inbox
Before deciding what to automate, it is worth being honest about how a small sales inbox fails. Four patterns cover most of it.
- Ownership is ambiguous. Three people can see the message, so nobody owns it. Work everyone can do is work nobody does.
- The first reply needs information nobody has to hand. Stock, lead time, the price at that quantity. The message waits for a two-minute lookup that only one person can do.
- Threads fragment. The buyer replies from a second address, someone forwards it internally, and the history splits into pieces.
- Follow-up depends on memory. A buyer says "send me something in two weeks." Two weeks later, everyone is busy.
None of these are intelligence problems. They are scheduling and routing problems, which is exactly the category machines handle well.
What to automate
Automate the parts of the inbox that are mechanical, verifiable and fast to reverse.
Acknowledgement with substance. Not an autoresponder saying your message is important. A real first reply that repeats what was asked, answers what can be answered from your own catalogue and pricing, and asks the one or two questions needed to go further. This is the single highest-value thing to automate, because it is the step where time is lost.
Classification and routing. Is this a new enquiry, an existing customer with an order question, a supplier invoice, or a recruiter? Route accordingly. Most inboxes lose time because everything arrives in one undifferentiated pile.
Data extraction. Pull the company name, the quantity, the delivery city, the deadline out of a free-text message and put them into structured fields before a human reads it. The human then starts from a filled form, not a paragraph.
Quote assembly for standard configurations. If your pricing is a function of product, quantity and destination, that function can be executed without a person: a price table and a template turn a standard enquiry into a quote in minutes. Axelion covers the step before the inbox: it answers price questions in your website chat from your own pages and hands each request to your team complete, with the whole conversation.
Follow-up scheduling. The buyer who said "in two weeks" hears from you in two weeks, without anyone remembering.
What to keep human
The line is not about difficulty. It is about consequence and ambiguity.
Keep a human on anything where the cost of being wrong is high and hard to undo: bespoke pricing, contract terms, discounts outside policy, credit arrangements, anything with a legal signature at the end.
Keep a human on complaints. A customer who is angry is telling you something about the relationship, not just about the order. Automated empathy reads as insult.
Keep a human wherever the enquiry does not fit a pattern. A message that mixes three questions, contradicts itself, or describes a use case you have never sold into is a signal, not a task.
Keep a human on your largest accounts, regardless of how routine the message looks.
Designing the handover
The point of automating the first reply is not to remove people from email. It is to make sure that when a person arrives, they arrive early and prepared.
Set explicit triggers for escalation: deal size above a threshold, language that signals frustration, a request you have no rule for, an explicit ask to speak to someone. Configure who receives the escalation and what they receive with it — the thread, the extracted fields, the draft that was about to go out. Handover works when your team has actually set it up and staffed it; it is a workflow you design, not something that happens by itself.
And write the automated messages so a human can take them over mid-thread without an awkward seam. No persona, no invented enthusiasm, no signature that implies a person who does not exist. Plain, factual replies age well and hand over cleanly.
The measurement that matters
Track median time to first substantive reply, not average. Averages hide the Friday evening enquiry that waited until Tuesday. Then track how many enquiries reach a second message from the buyer. That is the number that tells you whether your first reply was worth sending.
Email is the channel where the money moves. Treating it as a slow channel is a choice, and it is the easiest one to reverse. See how the pieces fit together on the product page, or read more on response speed.
Axelion answers in seconds, around the clock. It replies in your website chat, recommends the right product from your pages, saves every lead and hands complex cases to your team. WhatsApp and Telegram on Business. See it on your own website →
Related articles
AI chatbot for your website: how to choose one in 2026
Five kinds of website chat compared, seven questions to put to any vendor, and what to fix on your pages before an AI chatbot meets buyers.
Telegram for B2B sales in emerging markets
Why the channel outperforms email in some markets, and how to run it professionally.
WhatsApp as a sales channel, without the hype
Opt-in rules, templates, response windows and what actually drives replies.