Merging sales administration and customer service is neither always a good idea nor always a bad one. The decision depends on a few concrete criteria: how many customer requests relate to an order in progress, how big the team is, how complex your orders are, and whether everyone sees the same data. In many companies, the right answer is not merging the org charts but giving customers a single point of contact, with clear roles behind it.
Two jobs sharing the same inbox
On paper, the line is clear. Sales administration takes an order from the purchase order received to the invoice: entry, checking prices and terms, delivery follow-up, invoicing. Customer service steps in when something goes wrong or when the customer has a question: a delay, an incomplete delivery, a non-compliant product, a return.
In practice, both teams often receive the same messages. An electrician who writes “where is Tuesday’s order, I’m missing the circuit breakers?” is asking a tracking question (sales admin) and may be opening a dispute (customer service). A public-sector buyer asking for a credit note on a wrongly invoiced line touches both. The more your customers communicate by email, the wider this grey area becomes.
That grey area is what raises the question of merging. Not a management fad.
What keeping them separate protects
Keeping two distinct teams has real benefits.
- Focus. Entering orders with negotiated prices, discounts by product family and free-shipping thresholds takes attention. Being interrupted every ten minutes by a complaint call drives up the error rate.
- Expertise. A sales administrator who knows the price lists of three hundred customers by heart and an agent who knows how to calm down an unhappy customer are not quite doing the same job.
- Clear accountability. When everyone has their own scope, it is obvious who measures what: order entry time on one side, dispute resolution time on the other.
What keeping them separate costs
It also has a price, and the customer pays it first.
- Hand-offs. The customer writes to customer service, who has to ask sales admin for the order status, who has to ask the warehouse. Three internal exchanges for one answer.
- Orphan cases. On a dispute that combines an entry error and a delivery problem, each team assumes the other is handling it.
- Double reading. When both teams monitor the same shared inbox, each email is opened twice, and some are handled by no one.
- A partial view of the customer. Sales admin sees the orders, customer service sees the complaints, and nobody notices that this electrical distributor has been ordering less for three months and complaining more.
Six criteria to decide
Rather than deciding on principle, look at your situation through these criteria.
1. What incoming requests are about. Take a week of emails and sort them. If most messages sent to customer service concern a specific order (status, lead time, back order, price discrepancy), the two teams are already working on the same thing, and bringing them closer makes sense. If customer service mostly handles technical after-sales (warranty, commissioning, product returns), keeping them apart remains logical.
2. Team size. With four people, the merger often already exists in practice: everyone does a bit of everything. With thirty, a single team becomes hard to manage and specialisms reappear inside it.
3. Order complexity. A food wholesaler receiving repeat orders for well-known items can give entry and follow-up to the same person. An industrial supplier handling configured items, project pricing or tender responses needs specialists.
4. Account ownership. If each account already has a named contact, it is natural for that person to follow the order from start to finish, complaints included. If requests are handled by whoever is free, splitting by type of task works better.
5. Tools. If customer service has no access to the ERP and sales admin cannot see the ticketing tool, merging the teams will not fix anything: information will still have to be fetched from somewhere else. Start by sharing the data.
6. The order entry workload. This is the criterion people forget. If your sales administrators spend most of their day retyping purchase orders, merging them with customer service means asking an already overloaded team to take extra calls. Customer relations will come after data entry, just as they do today.
Three possible organisations
Between strict separation and a full merger, there are several options.
- Two teams, with bridges. The functions stay separate, but with a shared tool, written hand-off rules and a named owner for every mixed case. This is often the most realistic first step.
- Pods by customer portfolio. Each pod handles a group of accounts from order to dispute. The customer always deals with the same people, and knowledge of their terms stays within the pod.
- A single front desk, an expert back office. All requests arrive in one place, are sorted and, for simple cases, handled there; cases that need expertise (special pricing, complex disputes) go to specialists.
No model is better in absolute terms. The right one is the one that matches the criteria above in your company.
How automation changes the debate
Much of the discussion is really about volume: who has time to handle what. Automation changes that starting point.
An agent like Eledone reads the emails in sales and sales admin inboxes, categorises them (order, price request, stock or lead-time question, complaint), answers simple questions using ERP data and prepares a complete file for disputes that need a person. It also enters purchase orders into the ERP, checking prices, stock and credit limits according to the rules agreed with each customer, and flags anything out of the ordinary.
The sorting that justified two teams is then done upstream. Human work focuses on what requires judgement: exceptions, sensitive disputes, relationships with key accounts. Among our customers, automated order entry saves an average of 3 hours per day per sales administrator and cuts entry-related disputes by 30%.
The question becomes less “who does what” and more “who manages the agent’s rules and who takes over on difficult cases”. A single team, with fewer repetitive tasks and a stronger customer focus, becomes much easier to consider. We cover this in more detail in our article on what to do when AI takes over your daily tasks.
Before reorganising: a simple method
- Measure where each team’s time goes for two to three weeks, by type of task.
- Sort incoming requests by whether they concern an order, a product or an account.
- Reduce the repetitive workload before touching the org chart, otherwise the new organisation will inherit the same bottlenecks.
- Test the chosen model on a limited scope: one branch, one customer segment, one region.
- Name an owner for every case, from the first email to closure. Whatever the model, this is what makes the difference for the customer.
Frequently asked questions
Does merging sales admin and customer service save money?
Not automatically. A merger removes hand-offs and double reading, but it does not remove any tasks. The gains mostly come from reducing repetitive work and sharing data better.
Do job descriptions need to change?
Yes, as soon as scopes shift. A role that combines order follow-up and complaint handling requires people skills and a good knowledge of commercial terms. Plan a period of cross-training between the two teams.
Which indicators should you track after a reorganisation?
Time to first response, dispute resolution time, number of internal hand-offs per case and the order entry error rate. Compare them with the baseline measured before the change.
Does automation require merging the teams?
No. Eledone connects to your inboxes and your ERP whatever your organisation, and can route each request to the right team. Automation simply makes a merger easier to get right if you choose one.
Want to see how your customer emails and orders could be sorted and handled?
Book a demo