Why Does Answering One Customer Question Require Three People?

A customer sends an email at 9:12 in the morning.

Can you confirm when our order will arrive?

It should be an easy question. Customer service opens the ERP and finds a delivery date, but they are not sure it is still current. They message operations. Operations remembers that the supplier mentioned a delay last week, but cannot remember whether the date changed by five days or ten. They search through email. Procurement gets involved because they spoke to the supplier more recently. Someone checks the purchase order. Another person checks the shipment information.

Twenty minutes later, customer service finally has an answer.

From the customer's point of view, they asked one company one simple question. Inside the business, three or four people had to stop what they were doing to answer it.

When this happens occasionally, nobody worries about it. When it happens 30 times a day, it becomes part of the way the company operates. That is when customer service starts consuming much more capacity than the number of customer emails suggests.

The problem is not necessarily that you need more people answering customers. The problem may be that the person answering the customer cannot see what the business already knows.

The Information Usually Exists Somewhere

This is what makes the situation frustrating. Most of the time, the company already has the answer. The sales order exists. The purchase order exists. The stock information exists. The supplier sent the revised delivery date. The forwarder sent the shipment update. Someone knows which goods were allocated to another customer. The warehouse knows what physically arrived.

The information is there. It simply sits in different places. Our own buying-moment research captures this very well:

The information exists somewhere, but I can't see it.

Another recurring phrase is even more direct:

I need to ask three people before I can answer the customer.

In businesses where order, delivery and stock information depend on several systems and individual knowledge, a simple customer question creates internal checking, slower responses and interruptions across several departments.

For a business owner, that is worth paying attention to. The customer enquiry is visible. The internal work required to answer it often is not.

One Customer Question Can Create Work Across the Company

Imagine customer service receives this message:

Can you confirm whether the 600 units will ship on Friday?

The customer service employee cannot see a reliable answer, so they contact operations. Operations checks the sales order and sees the goods are still open. They contact procurement. Procurement checks the purchase order and finds the supplier's original commitment. Then they remember the supplier sent another email yesterday. The new date is Monday. Now operations checks whether the three-day delay affects another part of the order. Customer service receives the updated information. They reply to the customer.

That might have taken customer service five minutes. But the business used 20 or 30 minutes of combined employee time. More importantly, several people were interrupted. Procurement stopped doing procurement. Operations stopped managing orders. Customer service waited for an answer. If managers become involved, they stop managing as well.

This is why customer-service workload is often underestimated. The real cost is not only the person speaking to the customer. It is the number of people behind that person who need to help find the answer.

Searching for Information Has Become Work

This problem extends far beyond customer service.

Those studies cover many types of work, not only customer service. Still, the behaviour is very familiar in an SME. Someone opens the ERP. Then email. Then Excel. Then WhatsApp or Teams. Then asks a colleague. The employee may be working hard all day without actually moving many orders forward. A large part of the day is spent reconstructing what is already happening inside the business.

Customer Service Has the Same Problem

Salesforce's customer-service research found that 26% of service representatives say they often lack context about a customer's situation.

That makes sense. A customer-service employee does not need to become a procurement expert. They do not need to manage the warehouse. They do not need to negotiate with suppliers. They simply need reliable access to the information required to answer the customer.

Again, the practical lesson is simple. If someone has to search five places before answering a customer, the business has created unnecessary work before the conversation even begins.

The Customer Does Not Care Where the Answer Lives

From inside the company, departments matter. Sales. Procurement. Operations. Warehouse. Finance. Customer service. Each team has its own responsibilities and often its own systems.

The customer sees none of that. They placed an order with your company. If they ask when it will arrive, they expect your company to know. They do not care that the latest supplier date is inside an email that only procurement received. They do not care that the ERP has not been updated yet. They do not care that the warehouse maintains another spreadsheet. They definitely do not care that customer service does not have access to the purchasing screen.

Those are internal problems. The customer experiences the result as:

I asked a simple question and they couldn't answer me.

That gap between the internal complexity and the external experience is important. Your company can feel reasonably organized internally while appearing surprisingly disorganized to the customer.

A Slow Answer Is Annoying. A Wrong Answer Is Worse.

Speed matters. But accuracy matters more. Suppose the ERP says the order will arrive on the 18th. Customer service replies immediately:

Yes, delivery remains confirmed for the 18th.

The answer is fast. Unfortunately, the supplier emailed procurement yesterday saying production is running ten days late. The customer now has a confident answer that is wrong. A few days later, the company has to call back and correct the commitment.

Our own operational research contains exactly this buying moment:

We told the customer yes, then discovered we could not deliver.

That type of mistake is classified as Very High commercial severity because unreliable promises can lead to cancellations, discounts, lost trust and customer churn. This is why simply giving customer service access to more data is not enough. They need access to information the business itself can trust.

The Question Is Not "Can They Access the ERP?"

A common response is:

Customer service already has access to Odoo.

Good. But what happens after that? Does Odoo contain the latest supplier commitment? Does the stock figure reflect what has already been allocated? Does it show the revised shipment date? Was the partial delivery recorded? Did yesterday's supplier email change the expected arrival date? Is the backorder visible? Can the employee see which part of the customer order depends on incoming stock?

Access to a system only helps when the relevant operational information has reached the system. This is why the issue often survives ERP implementation. The ERP may be doing exactly what it was designed to do. It contains the transactions. Some of the day-to-day operational information still arrives outside it. That is what creates the gap.

Odoo Already Gives Businesses Useful Customer Visibility

Odoo 19 includes customer portals by default. Businesses can give customers access to information and documents including orders and invoices. Portal users can follow and view orders, while delivery integrations can provide tracking links through the customer portal.

That is valuable. If customers can check straightforward information themselves, they do not need to contact your team every time. Salesforce research also shows there is real appetite for that.

But self-service only helps if the information is reliable. If your portal says the order arrives Friday while procurement already knows it will arrive next Tuesday, you have not solved the problem. You have simply allowed the customer to see the outdated information without speaking to you.

Before Customer Self-Service Comes Internal Visibility

For many SMEs, the first objective should be modest. Do not begin with an elaborate customer portal. Begin by making sure the employee speaking to the customer can answer confidently. Can they see:

• The customer order
• Current stock
• Outstanding quantity
• Supplier status
• Expected delivery
• Shipment status
• Backorders
• Known exceptions

If the answer requires calling three departments, customer self-service is probably not the first problem to solve. The internal information flow comes first. Once that is reliable, customer-facing visibility becomes much easier.

There Are Three Very Different Ways to Handle the Same Customer Question

Consider the question: "Where is my order?"

The first way: someone investigates

Customer service checks several places. They ask operations. Operations asks procurement. Procurement checks with the supplier. An answer eventually returns to the customer. This is common, but expensive.

The second way: customer service already has the answer

The employee can see the current order status, supplier commitment, shipment information and any exception affecting the customer. They answer immediately. Other departments are not interrupted.

The third way: the customer never needs to ask

The business knows the shipment has changed. The customer is informed before they contact you, or the current status is already available through a reliable portal.

That is a very different customer experience. Most growing SMEs do not need to jump directly from the first situation to the third. Moving from investigation to reliable internal visibility already recovers a significant amount of capacity.

B2B Customers Are Expecting More Visibility

This is becoming especially relevant for distributors. McKinsey's 2025 distribution research, based on surveys of 300 distributors and 299 suppliers, found real-time inventory tracking among the most important digital capabilities for both groups.

McKinsey also describes real-time visibility, transparent information and self-service as increasingly basic expectations in distribution rather than optional digital extras.

There is an interesting contrast here. A customer can buy a HK$300 consumer product online and see order received, prepared, shipped, out for delivery, delivered. Then the same person goes to work and places a HK$300,000 B2B order. To find out where it is, they send an email. Someone replies:

Let me check.

That experience is becoming harder to justify. B2B operations are more complex than consumer parcel delivery, of course. But the customer's expectation has changed anyway.

An Interesting Example: Riddell

Riddell, the American sports-equipment company, recently faced a very similar problem. Its sales organization had almost 200 people. When representatives needed pricing, delivery dates or order status while speaking with customers, they often had to contact back-office support or run reports. The information existed inside the business, but it was difficult for the people facing the customer to access quickly.

Management considered adding more sales-support employees. Riddell's CIO rejected that solution because adding people would not solve the underlying information problem. Instead, Riddell built an internal assistant that allowed sales representatives to retrieve information from its SAP system more easily.

Microsoft reports that after rollout, more than 21,000 hours were saved annually, 59% of sales representatives said they responded to customer questions faster, more than a third used the assistant instead of contacting sales support, and roughly 20% of representatives were making between one and five additional customer calls per day because they had recovered time.

Riddell is much larger than the typical STREVIO client, so those absolute numbers should not be projected onto an SME. The decision itself is what matters. Management could have added more people to answer the same internal questions. Instead, it asked why those questions required another person in the first place.

Hiring Another Customer-Service Person May Not Fix the Problem

Imagine your five-person customer-service team is overloaded. The obvious conclusion is:

We need a sixth person.

Sometimes you do. If customer volume genuinely requires more human conversations, another employee may be the right decision.

But first look at what the existing five people actually do. How much time is spent answering customers, versus waiting for information? How often do they contact operations? How often do they ask procurement for order status? How often do they check spreadsheets? How often do they manually rebuild shipment information? How often do they answer a question that another employee already answered yesterday for another customer?

If a large part of the workload is searching and chasing, employee number six will probably do the same thing. You have increased capacity at the front of the process while leaving the bottleneck behind it unchanged. The customer-service team may even generate more interruptions because six people can now ask operations for information instead of five. Before adding the headcount, understand the workload.

This Is Exactly What Operational Capacity Means

Imagine the business currently handles 1,000 customer orders per month. As sales grow, orders rise to 1,300. If every additional order produces more status enquiries, more supplier checks, more stock questions, more internal messages, and more reporting, then customer-service workload rises almost directly with order volume.

Eventually, more people are required. Then another layer of coordination is added. This is the pattern behind one of our most important buying moments:

Every time we grow, we need another person.

More customers and more orders produce proportionally more follow-up and coordination, so payroll and complexity rise with revenue. The better goal is to allow order volume to increase faster than the administrative work surrounding each order. That is Operational Capacity.

Our Hong Kong Wholesale Case Had Exactly This Problem

Another Case Shows What Happens When the Answer Is Wrong

Customer Service Should Not Depend on Who Happens to Be in the Office

There is another warning sign owners often overlook. Ask yourself: if your best operations employee takes a week off, does customer service become noticeably slower?

If the answer is yes, the business may rely too heavily on individual knowledge. Perhaps Susan knows every supplier. Maybe David remembers which container contains which orders. Perhaps someone in procurement keeps a private Excel tracker that everybody trusts more than the ERP.

Those employees are valuable. The problem is not their expertise. The problem is that routine operational information depends on their availability. People should be valuable because of the decisions they make and the relationships they manage. They should not become indispensable simply because they are the only person who knows where the answer is.

More Meetings Usually Do Not Solve It

A common workaround is the morning operational meeting. Everybody gathers. Procurement gives updates. Operations discusses late orders. Customer service asks about important customers. Management reviews exceptions.

This can be useful. Some issues genuinely deserve a conversation. But if the meeting exists mainly so one department can tell another department what the systems do not show, you have created a human information-integration process. And tomorrow, you have to run it again.

Another common workaround is WhatsApp or Teams. Customer service posts: "Anyone knows status of ABC order?" Somebody answers. Great. The customer gets the information. But the answer may still disappear into a conversation thread. Next week, someone asks again.

Communication tools are excellent for communication. They are poor substitutes for reliable operational visibility.

A Dashboard Does Not Automatically Fix This Either

Another common reaction is:

We need a dashboard.

Perhaps. But ask what the dashboard will display. If it pulls an outdated supplier date from the ERP, it shows outdated information beautifully. If the business still maintains the real backorder list in Excel, the dashboard may not know about it. If supplier updates remain buried in email, a colourful chart does not capture them.

Visibility improves when the relevant information is connected and current. The screen itself is the last part. A simple table that people trust is more useful than an impressive dashboard nobody believes.

What Information Should Customer Service Actually See?

They do not need access to everything. Giving everybody every system often makes the problem worse. For a typical trading or distribution company, the customer-facing employee may need a straightforward view showing:

• Customer order
• Quantity ordered
• Quantity already shipped
• Quantity outstanding
• Stock available
• Relevant incoming stock
• Supplier status
• Expected shipment date
• Delivery tracking
• Known delay
• Backorder status
• Any issue requiring a special customer conversation

That may be enough. They do not need the supplier's complete commercial history. They may not need purchasing prices. They do not need access to every operational screen. The objective is not maximum information. It is the right information to answer the customer correctly.

The System Should Also Know When the Normal Answer Is No Longer Good Enough

Most orders are normal. Those should not consume much management attention. The more useful question is: which customers need somebody to intervene? For example:

• An expected date changed
• Stock is no longer sufficient
• A supplier failed to confirm
• Part of the shipment is missing
• The order became a backorder
• A delivery milestone was missed
• A key customer's commitment is now at risk

Those situations deserve human attention. The system should help surface them. This changes customer service from repeatedly asking "Is everything okay?" to knowing "These seven orders are not okay." That is a much more scalable way of working.

Good Customer Service Can Be Proactive

There is a major difference between these two conversations. The first:

Customer: Where is my order? Company: Let me check.

And the second:

Your supplier shipment has moved from Friday to Monday. Your customer delivery is still safe, so no action is required.

Or:

Your delivery will now be two days late. We identified the issue this morning and wanted to let you know before it affects your planning.

The operational event is the same. The customer experience is completely different. Salesforce's State of Service research points to proactive service as an important benefit of bringing customer and operational data together.

For a business owner, proactive service does not need to mean a sophisticated AI project. It starts with one basic capability: the business has to know about the problem before the customer does.

Self-Service Is the Final Step, Not the First One

There is a temptation to put everything into a customer portal. Let customers log in. Let them track orders. Let them see stock. Let them see delivery status. That can be excellent.

But imagine publishing unreliable information directly to customers. Now the company has lost the human buffer that previously caught some of the mistakes. A portal works well when the underlying operational information is already dependable.

The sequence should usually be: first, make sure your own team can see the answer. Then make sure the answer is trustworthy. Then decide which information customers should access themselves.

Eight Signs Your Customer Service Problem Is Actually an Information Problem

1. "Let me check" is one of the most common phrases in customer service

Some questions genuinely require investigation. Routine order-status questions should not.

2. Customer service regularly asks operations for updates

If it happens all day, operations has effectively become second-line customer support.

3. Employees check several systems before answering

ERP, Excel, email and WhatsApp should not all be necessary for every basic question.

4. Different employees give different delivery dates

This usually means there is no trusted current answer.

5. Customers sometimes tell you about problems before your system does

That is a serious visibility issue.

6. Customer enquiries interrupt procurement constantly

Procurement should speak to customers when their expertise is required, not because order status is invisible.

7. Your best employee knows the answer without checking

Useful expertise can hide a weak information process.

8. As orders grow, customer-service headcount has to grow almost at the same rate

Look at how much of the new workload is genuine customer interaction and how much is searching, checking and chasing.

Five Questions an Owner Can Ask Tomorrow

You do not need a consultant to start understanding this. Ask your customer-service team:

When a customer asks where an order is, where do you look first?

Then ask what happens if the answer there is not trusted.

How often do you need operations or procurement to help answer a basic customer question?

You do not need perfect measurement. A rough answer will tell you a lot.

Which customer questions take the longest to answer?

Order status? Stock availability? Delivery dates? Backorders? Invoices?

How often do we have to call customers back and change an answer we already gave them?

That question is particularly important.

If customer orders grew 50% next year, would we need 50% more people answering these questions?

If yes, you have identified a capacity issue worth examining.

What Should Be Automated?

The repetitive information work. For example:

• Collecting current order status
• Bringing together stock and outstanding quantities
• Monitoring supplier commitments
• Capturing shipment updates
• Identifying backorders
• Matching incoming supply to customer demand
• Flagging late deliveries
• Notifying the relevant person when a customer commitment becomes at risk

The goal is not to automate every customer conversation. Customers sometimes need judgment, reassurance, negotiation or a genuinely human response. But the employee having that conversation should not need to spend 20 minutes finding the basic facts first.

What Should Stay Human?

• A customer is angry because an important delivery failed — that should probably be handled by a person
• A key account wants to change an order at the last minute — human judgment
• A customer needs a commercial concession — human decision
• An important relationship is at risk — human ownership
• A complex technical question comes in — send it to the right expert

There is plenty of valuable human work in customer service. Checking three screens to discover whether a box shipped yesterday is not where human judgment creates value.

The Goal Is Not Fewer Customer Conversations

This distinction matters. A good relationship with customers includes communication. The objective is not to stop customers calling. If a customer wants advice, wants to discuss future orders, wants help choosing a product or wants to solve a real business problem, that conversation is valuable.

What you want to reduce are the conversations created because your own information is difficult to access.

• Did it ship?
• How many are available?
• Did the supplier confirm?
• What is the new date?
• Where is the balance?

Those questions will always exist. The business should simply be able to answer them without starting an investigation.

Before Hiring Another Customer-Service Person, Follow One Question Through the Business

Pick a normal customer enquiry tomorrow. Something simple. "Where is my order?" Then follow it. Who receives it? What do they open? Who do they ask? What does that person open? Does procurement get involved? Does someone search email? Does a spreadsheet need checking? Does somebody call the warehouse? How long before the answer comes back?

Then ask one more question: how many times does this happen every week? That is where the business case begins.

You may discover that customer service genuinely needs another employee. Fine. But you may also discover that a large amount of the workload comes from people searching for information the business already owns. Before adding permanent payroll, it is worth knowing the difference.

The Customer Asked One Question. Your Business Should Know the Answer.

Customers do not expect perfection. Suppliers will still be late. Shipments will still change. Stock problems will still happen. Business is messy. The opportunity is not to remove every exception. It is to make sure the company can see what is happening when the exception occurs.

Then customer service can answer accurately. Operations can focus on the orders requiring attention. Procurement can manage suppliers instead of answering internal status requests. Managers can deal with meaningful problems instead of chasing information. And as order volume grows, the existing team can absorb more of that growth without every additional customer creating another chain of internal follow-up.

That is what Operational Capacity looks like in everyday business.