Most distributors don't lose inbound customers because nobody wants to serve them. They lose them because the reply takes too long. A contractor asks for a price list and hears nothing until the next afternoon. A buyer asks whether an item is in stock, and the email goes to the warehouse and then to a branch supervisor before anyone answers. A prospect asks for a product data sheet while the responsible salesperson is out visiting customers. An existing customer asks about a backorder, and nobody is sure who should reply. Every one of these delays gives the buyer time to contact another supplier, and many of them do.
Cadr gives distributors, wholesalers and manufacturers with 10 to 200 staff an AI coworker that handles this inbound work. The coworker has its own email address and its own logins to your ERP and CRM, so it reads enquiries, checks prices and stock and records its work in the same systems your team uses every day. Every Cadr coworker starts in Review mode, which means nothing reaches a customer until someone on your team has approved it. The rest of this article explains what the coworker does with an inbound enquiry, where it hands work to a person and how the company stays in control of what it sends.
Why response time decides inbound orders
Response time matters more in inbound sales than at any other point in the sales process. A customer who writes to you has already decided to consider your company, often after building a shortlist of suppliers. Trade buyers commonly send the same RFQ to two or three distributors and order from whoever comes back first with a clear price, a confirmed lead time and the right documents, as long as the price is in range. A fast reply can't win an order at the wrong price, but a slow reply regularly loses orders the company was in a good position to win.
For a small sales team, keeping replies fast every day is hard. The same three or four people usually handle RFQs, quotes, order queries, backorder updates and customer service, often while working on site visits and key accounts. On a quiet day they answer within the hour, and on a busy day the inbox waits until the evening or the next morning. Inbound response time ends up depending on how busy the team is that week, when it should depend on a standard the company sets.
What a fast reply looks like in practice
Here is how a single enquiry moves through a Cadr coworker at a building-products distributor. At 09:12 a contractor emails the sales inbox asking for prices on 400 lengths of 110mm drainage pipe, availability for delivery on Friday and a current product data sheet. At 09:13 the coworker matches the item to the catalogue in the ERP, applies the contractor's account pricing and checks stock at the nearest branch. By 09:16 it has drafted a reply with the price, the confirmed stock and the approved data sheet attached, along with a note that Friday delivery depends on the transport schedule. Because a delivery promise needs a person's sign-off, it flags that line to the branch manager and logs the enquiry in the CRM with its value and expected close date. The salesperson approves the reply at 09:21, nine minutes after the email arrived, and the coworker schedules a follow-up for two working days later.
Answering routine questions from approved information
A large share of what inbound customers ask has a standard answer. Product specifications, minimum order quantities, certifications, standard lead times, payment terms and delivery options are already written down in your price lists, product data sheets and policy documents. A salesperson who types the same details out by hand ten times a week is doing work that doesn't need their judgement. A Cadr coworker answers these questions using only the documents and data the company has approved, and it doesn't make up prices, lead times or terms that aren't in them.
The coworker also completes the request instead of describing it to a colleague. If a customer asks for the latest price list, it finds the current approved version and sends it. If a prospect asks whether you can supply a particular product, it answers the parts covered by your catalogue and lists the points that still need confirmation from purchasing or a supplier. Where the enquiry is missing details, such as quantity, specification or delivery address, it asks the customer for all of them in one reply instead of three. The salesperson then picks up a conversation where the basic information has already been collected.
Passing the right requests to the right colleague
Fast answers are only useful when they're correct, so the coworker has to know where its authority stops. Each coworker works within the permissions of the role it supports, and the company decides which topics it handles alone and which go to a person. Requests for a large discount, a special order, unusual payment terms or a technical question that needs a product specialist are passed to the right colleague. The coworker sends that person the original email, the customer's order history and the details already gathered, so they can reply without starting from the beginning.
The customer doesn't need to know how your company is organised to get an answer. They send their question once, to one address, and the coworker routes it internally to sales, purchasing, finance or the warehouse. It lets the customer know that the right person is reviewing the request, so they aren't left waiting in silence while the internal work happens. If the colleague hasn't replied within the time the company has set, the coworker reminds them and, where the rules say so, raises the delay with their manager.
Order status, backorders and problems after the sale
The same approach carries on 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 information on record, including expected dispatch dates for anything on backorder. If a supplier delivery has slipped or a shipment has been held, it brings the responsible person into the conversation instead of giving the customer a vague update. It also watches for orders whose dates have moved and tells the customer early, so they don't find out about a delay on the morning the goods were due.
When a customer reports a problem, such as a short delivery, damaged goods or the wrong item, the coworker collects what the team will need to resolve it. That usually means the order number, the affected lines, photos and a short description of the fault. It records the issue against the customer's account, alerts the responsible team and checks that someone has followed up with the customer by an agreed date. Between orders, it notices when a regular customer who normally orders every month has gone quiet and lets the account manager know before the account drifts to a competitor.
The CRM and admin work done during the conversation
Every inbound conversation creates admin, and the coworker handles it as the conversation happens. New enquiries are added to the CRM with the customer's requirements, the expected order value and a likely close date. Follow-ups are scheduled according to company policy, quotes and data sheets are attached to the opportunity, and tasks are assigned to colleagues when their input is needed. Nobody on the sales team has to remember to update the record at the end of a long day, and the pipeline reflects what customers have asked for.
How the company stays in control
Managers decide how much the coworker does on its own, and they can change that at any time. In Review mode the coworker drafts every reply and a person approves it before it is sent. Once the team is satisfied with the quality, the company can move it to Exceptions mode, where routine questions such as stock checks, data sheet requests and order status are answered automatically and anything unusual still waits for a person. Every message and action is logged with what triggered it, which documents and data the coworker used and who approved it. Each time a salesperson edits a draft, the coworker applies that correction to similar replies later, so the share of drafts that need changes goes down week by week.
What changes for the sales team
Most AI writing tools draft a reply and leave everything else to the employee, who still has to check the facts, send the email, update the CRM and remember the follow-up. A Cadr coworker handles that whole sequence within the limits the company sets, working from its own inbox and its own system logins. Salespeople stay responsible for pricing, commitments and customer relationships, and they spend far less of their week on repeated replies and data entry. Customers get clear answers quickly and stop chasing the company for basic information.
Management gains a clearer view as well. Every enquiry is in the CRM, along with how long it took to answer and what the customer asked for, which shows which products and questions come up most often and where replies tend to stall. That information helps with decisions about stock, product information and staffing. If enquiries and RFQs at your company sit unanswered while the team is busy, bring us one real example and we'll show you how a Cadr coworker would handle it.
Frequently asked questions
What can the coworker answer without a person? Only what the company has approved it to answer, using the documents and data it has been given. This usually covers specifications, minimum order quantities, certifications, standard lead times, payment terms, stock availability and order status. Anything outside those limits goes to the right colleague with the full context attached.
Will it send customers wrong prices or terms? No. It uses only the price lists, account pricing, terms and policies the company has approved, and it doesn't invent figures. Discounts, special orders and non-standard terms always go to the person who has authority to approve them.
Does it send emails from our sales inbox? Each coworker has its own email address within your company's domain, along with its own logins to your ERP and CRM. Customers can write to it directly, or your team can copy it in or forward enquiries to it. Your team can see every message it sends in the same threads they already use.
How does it know who to pass a request to? The company sets the escalation paths during setup, for example sending technical questions to a product specialist and credit questions to finance. The coworker follows those paths and reminds the colleague when a reply is overdue. The rules can be changed at any time as the team or the process changes.