Ask a reseller MD why their provisioning process can't be automated and the answer tends to come quickly. Confidently, even.
Every carrier does it differently. Gamma has its own portal, its own submission flow, its own way of handling exceptions. BT Wholesale works differently again. Virgin Media Business differently again. And layered on top of that, every customer order has its own configuration — number of lines, porting requirements, site specifics, service type. There is no single process. There are dozens of variations of a process, and the person running it has spent years learning how to navigate all of them.
That knowledge is real. The complexity is real. And the conclusion — that this makes the process impossible to automate — feels logical.
It is also wrong. But not for the reason most people expect.
The objection assumes that automation means replacing the human entirely. That for a process to be automated, it has to be uniform, predictable, and exception-free. And since provisioning across multiple carriers is none of those things, automation must not apply.
This is the right concern aimed at the wrong layer.
The provisioning process is not one thing. It is two things that happen to live in the same workflow, handled by the same person, and never clearly separated from each other. Until you separate them, the whole thing looks un-automatable. Once you do, it becomes obvious which part needs a human and which part has been quietly consuming their time for years without requiring them at all.
Here is the distinction that changes everything: most of what happens in a provisioning workflow is not judgment. It is scaffolding.
Scaffolding is the work that follows a known pattern every single time. Logging the order. Submitting to the carrier portal. Monitoring for acknowledgement. Updating the CRM when a status changes. Notifying the customer when a milestone is reached. Chasing a carrier when an update is overdue. None of these require the coordinator to think. They require the coordinator to be present — to remember to do them, to find the right system, to copy the right information into the right place.
Judgment is different. Judgment is what the coordinator reaches for when the order doesn't follow the pattern. The carrier comes back with a query about the line configuration. A porting conflict surfaces that needs to be investigated. A customer has a non-standard requirement that needs someone to make a decision. These moments are real, they matter, and they are exactly where the coordinator's years of experience earn their value.
The problem is not that provisioning requires judgment. The problem is that the coordinator is spending most of their time on the scaffolding, which means when the moments that require genuine judgment arrive, they are already stretched.
What the Scaffolding Actually Looks Like
Take a single provisioning order through its lifecycle and map every step against this distinction.
Order received — log in CRM. Scaffolding. Same every time.
Identify carrier from order type, submit to the correct portal. Scaffolding. Rule-based, repeatable.
Monitor carrier portal for acknowledgement. Scaffolding. The same status field, checked on the same schedule, for every order.
Update CRM with acknowledgement, trigger next stage. Scaffolding.
Carrier raises a query about site configuration. Judgment. Someone needs to look at this order specifically and make a call.
Monitor for provisioning progress, chase if milestone is missed. Scaffolding.
Carrier flags a porting conflict. Judgment. Investigation required.
Receive completion notification, update CRM, notify customer. Scaffolding.
In a standard provisioning order, the ratio of scaffolding to genuine judgment is roughly eight to two. Eight steps that follow a known pattern. Two that require the coordinator's expertise.
The coordinator is spending eighty percent of their time on work that does not require them. Automation handles the eight. The coordinator handles the two — and handles them better, because they are no longer context-switching between a portal check and an exception that actually needs their attention.
Why Specific Processes Make Better Automation Projects
Here is what the objection gets backwards.
The specificity of a provisioning process — the fact that Gamma works one way, BT Wholesale works another, Virgin Media Business works a third — is not a reason automation won't work. It is a reason a generic tool won't work.
There is a difference between the two.
A generic automation platform built for any business in any sector cannot account for the fact that a Gamma port-out acknowledgement looks different from a BT one, or that a leased line order has a different monitoring cadence than a hosted voice install. It does not know your carriers, your order types, or your exception patterns.
A bespoke automation built specifically for your provisioning workflow does. It is designed around your carriers. It knows which status updates to expect from each one, which email addresses they come from, which milestones to monitor and at what intervals. The specificity that disqualifies a generic tool is exactly what makes a custom build valuable.
The more specific your process, the more the automation is worth — because nobody else can replicate it. A competitor running the same carriers cannot buy your automation off a shelf. It was built for you.
What the Coordinator Does When the Scaffolding Is Handled
This is the part that tends to land hardest in the conversation.
When the scaffolding is handled automatically — when CRM updates happen without manual input, when carrier portals are monitored without someone opening a browser tab, when customer notifications go out on time without someone remembering to send them — the coordinator's day changes shape.
They stop being the person who keeps the process moving. They become the person who manages it.
The difference is significant. Managing a provisioning workflow means having a clear view of everything in flight, spotting problems before they become complaints, and applying genuine expertise to the orders that need it. Keeping it moving means spending the day on the scaffolding — the logging, the checking, the updating — that automation handles without thinking.
The coordinator does not become less important when the scaffolding is automated. They become more important. The judgment calls that were always the most valuable part of their role stop competing for time with the parts that were never theirs to begin with.
Summary
The provisioning process is specific. The carriers work differently. The orders have quirks. All of that is true.
None of it means the process cannot be automated. It means the right automation has to be built for your process specifically — not bought off a shelf and applied generically.
The goal is not to remove the coordinator from provisioning. It is to return them to the part of provisioning that actually requires them. The scaffolding runs automatically. The judgment stays human. The process becomes faster, more consistent, and more resilient — and the person running it stops spending their expertise on work that was never worthy of it.
If your provisioning process feels too specific to automate, the Reseller Ops Roadmap is the right place to test that assumption. Fixed scope, fixed fee, and the output is yours — a clear view of which parts of your process are scaffolding, which require judgment, and what fixing the split would mean for your team.
Book a Roadmap conversation: aideal.group
Thanks for reading!