A surprising amount of revenue in B2B companies is lost in the inbox. A customer asks for a price list and waits until the next afternoon. A prospect wants to know whether a product is in stock, but the salesperson is travelling. Someone asks for technical specifications, and the email is forwarded to two colleagues before anyone replies. An existing customer asks about an order, and the answer is split between email, the CRM, the ERP and a colleague who is in a meeting. None of these delays looks serious on its own, but across hundreds of enquiries a year they add up to a steady loss of orders that the company had already done the hard work to attract.
What the research says about response time
The best-known research on this subject was published in Harvard Business Review in 2011, in an article titled "The Short Life of Online Sales Leads". It drew on an analysis of 1.25 million sales leads and found that companies which tried to contact an inbound lead within an hour were nearly seven times more likely to qualify that lead than companies that waited even one hour longer. The same article reported an audit of 2,241 US companies. Only 37% responded to a web enquiry within an hour, 23% never responded at all, and the average response time among companies that did reply was 42 hours.
The research is now more than a decade old, and it should be read with care. Companies that reply quickly are often better organised in other ways too, so speed alone doesn't explain the whole difference in results. Even so, the pattern is easy to recognise in distribution and manufacturing, where trade buyers often send the same request to two or three suppliers and work with whoever comes back first with a clear price, lead time and the right documents. A slow reply doesn't always lose the order, but it gives competitors a head start on every enquiry it touches.
Why inbound enquiries are the most expensive ones to lose
An inbound enquiry is a customer showing intent. Before that email arrived, the company had already paid for its product range, its stock, its website, its trade show stand, its sales team and whatever marketing brought the buyer to it. Losing that customer because nobody sent the current price list or answered a routine question about minimum order quantities wastes all of that spending. It is also one of the easiest losses to prevent, because the information the customer needs usually exists somewhere in the company already.
Customers don't see the internal reasons for a slow reply, such as a salesperson on a site visit or a question waiting for the warehouse. They see a supplier that takes two days to answer a simple question, and they remember it the next time they need to place an order. For a small sales team that also handles quotes, order queries and customer service, keeping replies fast every day of the week is very hard. Response times end up depending on how busy the team is that week, when they should meet a standard the company has set.
How a Cadr coworker answers inbound enquiries
Cadr gives distributors, wholesalers and manufacturers with 10 to 200 staff AI coworkers that take on this work inside their existing systems. Each coworker has its own email address and its own logins to the company's email, CRM and ERP, and it works alongside a named salesperson within that person's permissions. It is connected to the Cadr Business Suite, which brings together the company's approved product information, current price lists, customer history, CRM records, ERP data and policies in one place. Every coworker starts in Review mode, which means nothing reaches a customer until someone on the team has approved it.
When an enquiry arrives, the coworker answers from that full company context and not only from what is written in the email thread. If a prospect asks for the latest price list, it finds the current approved version and sends it. If they ask about minimum order quantities, certifications, standard lead times or product specifications, it answers from information the company has already approved, and it never makes up prices or terms. If a returning customer asks about a previous order, it knows who they are, what they bought, who manages the account and what is already on record in the company's systems.
The coworker sends the first reply quickly, asks the customer for any missing details in a single message and keeps the conversation moving. The salesperson then picks it up with the basic information already collected and spends their time on negotiation, pricing decisions and the relationship. Once the team trusts the quality of the drafts, the company can move the coworker to Exceptions mode. In that mode routine questions are answered automatically, and anything unusual still waits for a person.
Passing complex requests to the right colleague
Some requests need more than a standard answer, and the coworker is set up to recognise where its authority ends. If a customer asks for a large discount, a custom production run, unusual payment terms or a technical change to a product, the coworker identifies the colleague responsible and assigns the request to them. It sends that person the original email, the customer's history and the details already gathered, so they can reply without starting from the beginning. If the colleague hasn't responded within the time the company has set, the coworker reminds them and, where the rules say so, tells their manager.
The customer only has to ask once, to one address. They don't have to work out which department handles credit terms or repeat the same request to sales, production and finance. The coworker lets them know that the right person is reviewing their request, so they aren't left waiting without a reply while the internal work happens. Every handover is recorded, which means managers can see how long each type of request takes to resolve and where it tends to stall.
Customer care after the sale
Customer care shouldn't slow down once an order has been placed. When a customer asks about delivery status, the coworker checks the order in the ERP and replies with the latest information on record. If production or a supplier delivery is running late, it alerts the responsible team and keeps the customer informed according to company policy, so they hear about the delay before the delivery date and not after it. This is often where small suppliers lose repeat business, because the team is busy with new orders and existing customers stop hearing from them.
When a customer reports a quality problem, the coworker collects the details the team will need, such as the order number, the affected lines, photos and a description of the fault. It records the issue against the customer's account, assigns the task to the responsible person and tracks it until it has been resolved and the customer has been told. Throughout, the coworker follows the same approval rules as the rest of the team. Anything that involves a credit, a replacement or a commitment on dates goes to a person to decide.
The admin is done during the conversation
Every customer conversation creates admin, and in most companies it gets done at the end of the day or not at all. A Cadr coworker handles it as the conversation happens: new enquiries are added to the CRM, customer requirements are recorded in a consistent format and opportunities are created with an expected value and close date. Follow-ups are scheduled according to company policy, relevant documents such as quotes and data sheets are attached to the record, and tasks are assigned to colleagues when their input is needed. The salesperson no longer has to answer the customer and then spend another ten minutes typing the same information into the CRM, the ERP and a spreadsheet.
Every action the coworker takes is logged, including what triggered it, which documents and data it used and who approved it. Each time a salesperson edits one of its drafts, the coworker applies that correction to similar replies in future, so fewer drafts need changes from one week to the next. Over time it learns the company's pricing tiers, approval steps and escalation paths as well as its data. Those rules stay with the company when staff change.
What management can see
Because every enquiry is now recorded in a consistent way, management can see far more than individual conversations. Cadr can show where enquiries drop out before they become quotes, how response times differ between teams and branches, and which products generate the most inbound demand. It can also show which quotes are still waiting for a reply, which customers need repeated follow-ups before they order and which regular accounts have started ordering less. Customer service becomes a reliable source of information for decisions about stock, pricing, staffing and product information, alongside its usual job of answering customers.
The case for improving this is straightforward. Companies spend a great deal to attract and develop customers, and inbound enquiries are the point where that spending either turns into orders or doesn't. Capturing, answering and following up every enquiry consistently is one of the most direct ways a distributor or manufacturer can improve sales without spending more on marketing. If enquiries at your company wait in inboxes while the team is busy, bring us one real example and we will show you how a Cadr coworker would handle it.
Frequently asked questions
What is a good lead response time for B2B companies? The 2011 Harvard Business Review research found that trying to contact a lead within one hour made it far more likely to be qualified than waiting longer. Many B2B companies still take more than a day to reply. For trade buyers comparing several suppliers, replying the same morning is a realistic goal that most competitors don't meet.
Will the coworker send replies without our approval? Not unless you allow it. Every coworker starts in Review mode, where a person approves each reply before it is sent. You can later let it answer routine questions automatically, while discounts, custom work and non-standard terms always go to the person with authority to approve them.
Does it send from our sales inbox? Each coworker has its own email address within your company's domain, with its own logins to your CRM and ERP. Customers can write to it directly, or your team can copy it in or forward enquiries. Your team sees every message it sends in the same threads they already use.