A supplier needs to know when an invoice will be paid. He rings the operations manager, because she answered helpfully about a delivery in March.
She does not deal with payments. She looks it up, or asks somebody, or promises to find out, and either way it costs her twenty minutes and produces an answer that finance could have given in one.
There are forty suppliers. Several of them have learned the same thing, and between them they produce a steady stream of enquiries to somebody whose job is something else entirely.
Who currently answers supplier enquiries
Whoever answered one previously. Suppliers are rational and they call the number that worked, which becomes the number for everything.
Who should answer them
Finance for payments, procurement for commercial matters, operations for delivery and scheduling, and a published route so suppliers know which is which.
What suppliers actually ask about
Payment status and timing, delivery scheduling, order amendments, who to contact about what, and chasing a decision somebody promised.
Why the payment questions dominate
Because they matter most to the supplier and because they are the hardest to get answered, so they generate the most repeat contact.
Why operations should not handle them
Not unhelpfulness, but because the answer sits in another system and another function, and the relay adds a person to every exchange.
Step 1: publish a supplier contact route
Which is missing from most businesses, so suppliers use whatever they have, which is a person rather than a function.
Step 2: expose payment status to suppliers
The single largest category, answerable from a system, currently answered by a person who has to look it up.
Step 3: define what operations genuinely owns
Delivery, scheduling and quality at the point of receipt, which is a narrow and legitimate set.
Step 4: route the rest automatically
By what the supplier is asking about rather than by who they happened to contact.
Step 5: tell suppliers when contacts change
Since a supplier whose named contact has left will call whoever they can reach, which is how this pattern starts.
Step 6: handle the new supplier onboarding properly
Which is where the contact routes should be established and almost never are.
Step 7: measure what arrives
Which is the analysis in mapping where repetitive enquiries actually come from.
Step 8: give suppliers a self service position
Invoice status, payment dates and order confirmations, available without contacting anybody, which removes the largest category before any routing is needed.
Step 9: review who is still calling and why
After a month, since the suppliers who continue to route everything through one person are telling you something about what the published routes do not cover.
Tell suppliers when something is disputed
An invoice on hold with no explanation produces weekly chasing from somebody who has no idea why they have not been paid, and the reason is almost always known internally.
Answer suppliers without routing them through a person
An assistant that gives payment status, answers delivery and scheduling questions, explains who handles what and routes the rest to the right function removes a supplier switchboard from an operations manager's week. The wider approach sits in reducing the questions that reach operations at all, a comparable coordination load in supplier coordination questions clients ask about planners, and the diligence questions in ai chatbot security questions to ask a vendor. Start at try, see features, and the sector view sits under small business.