The smallest useful change you can make to an agency service operation is to stop doing certificates yourself.
Not restructure the agency. Not migrate the AMS. Not commit to a transformation programme. Pick the one request type that arrives constantly, rarely needs judgment, and always seems to go out late, and send it somewhere else. Everything else stays exactly where it is.
This piece covers why certificates are the right first workflow, what a COI request actually involves once you break it apart, how to hand one off without losing control of it, and what to look at after a month to decide whether to widen it.
Why certificates, and not something bigger
Certificates have four properties that make them the natural first thing to move, and very little else in an agency has all four.
- High volume. They arrive every day, from every part of the book, which means you learn whether a change works in days rather than quarters.
- Low judgment. Most of the work is reading a request, checking what is already true on the policy, and producing a document. The judgment calls are the exception, not the rule.
- Immediate feedback. A late certificate is visible the same day, usually because a client tells you. There is no lag between a problem and the signal.
- Reversible. If you do not like how it goes, you stop sending them. Nothing has been restructured and nothing has been handed over.
That last point is the one owners underrate. Most proposals to change a service operation ask for a decision that feels permanent. Sending certificates somewhere for a month is not that kind of decision, which is exactly why it is a good way to find out what is true.
A certificate is not one task
The reason certificates feel small and behave large is that a single request is a sequence, and each step can stall on its own. In COVU OS a certificate playbook decomposes into 6 discrete tasks.
Read the request and work out what is actually being asked for. Identify the right policy on the right entity. Confirm the coverage and limits the holder is asking you to evidence. Check the holder language against what the policy will actually support. Produce the document. Deliver it and record that it went.
Written out like that, it is obvious why the two-minute job takes three days. It is not two minutes of work. It is six small pieces of work that have to queue behind whatever else landed in the same inbox, and any one of them can wait on a carrier, a colleague, or a question nobody has asked yet.
What usually goes wrong
Certificates land on the person who owns the account rather than the person with capacity, which means they compete directly with the work only that person can do. A producer with a renewal conversation and eleven certificate requests will do the renewal conversation, correctly, and the certificates go out late.
The client does not see any of that. They see that they asked for something simple and it took four days, right before a job site deadline or a closing. It is also, quietly, how agencies lose clients at renewal, which is worth understanding on its own if retention is the pressure you are feeling.
The usual fix is a reminder or a rule about turnaround times. It survives until the next busy week, because nothing about where the work goes has changed.
How to hand off certificates without losing control
The objection to moving any service work is reasonable: you lose visibility, and you find out about problems from the client. Three things prevent that, and they are worth insisting on wherever you send the work.
- Routing by license and skill. The steps that legally require a licensed person go to one. The steps that do not, do not. That split is what makes the economics work without creating a compliance problem.
- An audit trail. Every action, human or AI, logged with actor, timestamp, and reason, so a question about a specific certificate has an answer that is a record rather than a recollection.
- Your own staff stays the default. This is extra capacity when you need it, not a replacement for the people who know your book.
The mechanic is deliberately unremarkable. You send us the requests and we complete them and send them back. Nothing is carved out, the book stays yours, and you decide request by request. COVU runs on top of your AMS, not instead of it, with 8 AMS integrations live, so the certificate is issued and recorded where you already work.
What the production data shows
Across the agencies we operate:
- AI triage filters about 68% of inbound as noise, meaning carrier notifications, duplicates, and automated confirmations that never needed a person, so real requests stop queuing behind things that were never work.
- Classification runs at a 98% triage success rate, in under 10 seconds per item.
- Roughly 44% of completed service tasks are executed by AI, with the rest routed to people by license and skill.
- Median handle time on a task is 3.8 minutes, down 16% from 4.5.
- Escalations, meaning a task where someone is stuck and has to hand it on, are down 20%, from 435 a day to 348, and still declining.
Licensed work is handled by licensed agents, commercial and personal lines, U.S.-based with 8 or more years of experience, licensed in all 50 states.
What to look at after 30 days
Give it a month and then look at three things, none of which require a dashboard.
How long a certificate takes from request to delivery, measured from when the client asked rather than when someone picked it up. How many came back for a correction. And what your producers did with the time, which is the number that actually decides whether this was worth doing.
If those three look right, the question of what to move next answers itself, and you will have learned it from your own book rather than from a case study.
Frequently Asked Questions
What is a certificate of insurance, and why do agencies struggle with them?
A COI is a document evidencing that coverage exists, usually requested by a third party such as a landlord, lender, or general contractor. Agencies struggle with them because the volume is high, the deadline is external, and each request is a short sequence of steps rather than a single action, so it queues behind larger work and goes out late.
Can COI processing be handled without a licensed agent?
Parts of it can. Service work decomposes into steps with different requirements, and the steps that legally require a licensed person are not the whole request. Routing by license and skill keeps licensed work with licensed people while the rest moves, which is the same mechanism that relieves the licensing bottleneck.
How long should a certificate take?
Measure it from when the client asked rather than from when someone opened it, because the gap between those two is usually where the delay lives. Most agencies are surprised by the difference the first time they look at it honestly, which is the same pattern that shows up when you audit where the service week actually goes.
Do we have to change our AMS to move certificate work?
No. COVU runs on top of your AMS, not instead of it, with 8 AMS integrations live, so the work is completed and recorded in the system you already use. There is also a playbook for running alongside an existing AMS rather than replacing it.
What happens if we want to stop?
You stop sending requests. That is the point of starting with one workflow: nothing is carved out and nothing is handed over, so the decision stays reversible. The book stays yours and your own staff stays the default, with this as extra capacity when you need it.
Is starting with certificates the same as outsourcing our service team?
No. Your team stays your team. What moves is a defined set of requests, sent in and returned complete, with cost and speed visible per task. If you are weighing the broader models, the back office overview covers how they differ.