Can AI Do My Insurance Agency's COI and Renewal Paperwork?

Short answer: AI is a genuine fit for reading documents and drafting a first pass: pulling data off a dec page, triaging certificate requests, assembling a renewal comparison. On the simple end of certificate issuance it is further along than the coverage suggests: one owner below reports his own management system already sending straightforward certificates out unattended, and at least one vendor gives agencies COI issuance free. The line sits at anything carrying a non-standard additional-insured or waiver-of-subrogation endorsement, and at consumer-facing chat that states coverage. And before any of that matters, ask the question the brochures skip: does the output write back into your management system? If not, a human re-keys it, and your saving is whatever survives that step.

We probably get 50-60 a day and some are urgent

The volume problem is not theoretical. A two-person agency owner, u/zg825, described it in a thread on r/InsuranceAgent that drew 36 comments:

I'm just a 2 person shop with an assistant. I'm getting more into trucking so we have a lot of COI requests along with driver/vehicle updates. [...] The AI will read through the email and then pull out the relevant information that is needed so it's an easy copy/paste, but with my AMS system, we can email COI requests to an email where their AI processes it and then sends out the COI if possible. [...] While simple COI's are easy and take 1-2 minutes, we probably get 50-60 a day and some are urgent. Stopping other tasks to handle it ruin efficiency.

Fifty interruptions a day in a two-person shop is the real cost. The two minutes barely register.

Read the middle of that quote again, because it is the part most coverage of this topic gets wrong. His management system already has an AI that takes a forwarded request and sends the certificate out when it can. The simple end of certificate issuance is not a frontier. It is shipping, inside an AMS he already pays for, and his remaining work is routing and the hard ones.

He does name a real blocker further down the same comment, but it belongs to a different job: he would like AI to draft a baseline quote, and the quoting happens on a carrier portal he has to operate himself. That is new business, not certificates. Some vendors claim in-portal action. Quandri says it automates policy review, requoting inside the carrier portal, and renewal emails [published-by-the-vendor, quandri.io]. Its homepage shows three management-system logos under "Integrates with": Applied Epic, AMS360 and Hawksoft. There is no integrations page behind those three, so if you run something else, that is a question to ask before the demo rather than an answer to assume.

Certificate Hero targets the certificate workflow directly. Its homepage claims "realtime AMS connectivity" without naming a system, but a post on its own blog does name three: Applied EPIC, and Vertafore's AMS360 and Sagitta [published-by-the-vendor].

One thing to know before you start searching. Almost every page-one article about AI and certificates of insurance is written for the party tracking incoming certificates, typically a general contractor checking subcontractor coverage. That is a different product from the one an issuing agency needs. If a vendor's case study is about compliance tracking, it is not evidence about your job.

It hallucinated a coverage limit on like the 3rd account i tested

The most useful renewal-prep report in these threads is also the most cautious one. u/Equivalent-Bat-3269 posted about cutting commercial renewal prep, a thread with 11 comments. His starting position: each commercial renewal was taking 90 to 120 minutes, pulling dec pages out of Epic, typing everything into four or five carrier portals, building the comparison spreadsheet, with 47 accounts due in 30 days. Then, in his words:

tried chatgpt first. paste dec page, ask it to summarize. it hallucinated a coverage limit on like the 3rd account i tested and i almost sent bad data to the underwriter. gave up after 2 days.

He reports getting to roughly 18 minutes per renewal on 34 of 47 accounts, with 3 extraction errors caught before anything was sent. Treat that as a self-report and nothing more. It is unaudited, it is one agency, and a commenter in his own thread questioned whether a human wrote the post at all. u/driplessCoin asked directly: "did Claude code or chatgpt write this post?" The next commenter argued the opposite, and the poster denied it.

The part of his post that deserves the most weight is his own list of what still fails. On umbrella policies with stacked schedules: "claude gets confused, i still do those manually". On old scanned dec pages from before 2018: "OCR quality kills the extraction". And a third category he names flatly, "anything with handwritten endorsements."

That is the honest boundary of document extraction in this trade, written by someone who ran it. Clean, recent, machine-generated dec pages extract well. Stacked schedules, old scans and handwriting do not. Notice too that the near-miss was caught by a human reading the output before it reached an underwriter. That review is the control, not overhead to optimize away later, and it is the pattern we described for document intake in a bookkeeping practice: machine extracts, human approves, nothing leaves without a person's eyes on it.

You sound like a lazy compliance risk

The sharpest reply in that thread was not about accuracy. u/Madeanaccountforyou4 went straight at the data handling:

So you went from doing your job correctly to trying to cut corners by offloading sensitive private client information into AI programs thus giving their developers full access to said information? You sound like a lazy compliance risk tbh

The objection is fair, and it deserves a concrete answer rather than a reassuring one. Pasting a client's dec page into a personal ChatGPT account is a bad idea, and no amount of enthusiasm changes that. The difference is the contract tier, not the model. Business and enterprise tiers, and API access, come with no training on your inputs by default, and consumer tiers generally do not. Retention is a separate question, and it is the one people get wrong. "Zero data retention" is a term of art, not a tier: OpenAI's API default is abuse-monitoring logs kept up to thirty days, and true zero retention is an approval-gated control you apply for, on the endpoints that support it. So the rule is: business tier or nothing, and no personal accounts anywhere near a client file.

Before a single real dec page moves, get four things in writing: that your data is not used for training, that retention is zero or a stated number of days you can live with, the list of subprocessors, and where the data is stored. If a vendor cannot answer those in an email, you have your answer. This is also the moment to loop in whoever handles your carrier agreements, since some speak to third-party data sharing independently of anything the AI vendor promises.

The problem is the AI output doesn't write back to the AMS

This is the blocker that decides whether any of it pays, and it is almost invisible in the published content. u/Jaded_Drag_6534, in the same 36-comment thread, put it plainly:

We are using AI mostly for pulling from carrier portals renewal, cues and commission reconciliation. The reconciliation is the build that took most of our year. The problem is the AI output doesn't write back to the AMS

Treat that as the default assumption for anything you evaluate. Extraction is the easy half. Getting structured output back into Epic or AMS360, on the right policy, in the right fields, with an audit trail, is the half that takes a year. Until it closes, a person copies the output into the system of record, and that re-keying is where the promised savings quietly go.

The vendors know this is the battleground. Applied Systems announced a set of AI features in a press release dated 2025-10-07, including Applied Recon, Epic Max, Epic Bridge, Epic AutoFill, and Epic Submissions Manager [published-by-the-vendor, appliedsystems.com]. The release carries no general-availability dates and no pricing. A named feature in a press release is a roadmap item until your rep will tell you, in writing, that it is live on your instance at your price.

So measure after the re-key, never before. Time the current process end to end, then time the AI-assisted process including the copy step and the corrections. If a vendor's ROI math stops at "extraction complete," it is measuring the wrong finish line.

What happens if there's ever a claim dispute or an E&O situation

u/AmeliaLavender28, sole owner of a four-person Tennessee agency running Applied Epic and HubSpot, described the daily reality in a thread with 35 comments. Read it with one eye open: a vendor turns up in the replies to be recommended and thanks the room for it, and her later update praises that same product.

[...] Instead it turns into opening Epic, clicking through a bunch of screens, waiting on pages to load, checking emails, checking attachments, and piecing together the answer like you're solving a damn crime. That part honestly worries me. You start thinking about what happens if there's ever a claim dispute or an E&O situation and your records are not as clean as they should be

She is worrying about the right thing, and it reframes the project. Scattered records are an E&O exposure, so the reason to organize this work is defensive before it is ever about speed. AI that summarizes without preserving the underlying document makes the exposure worse. Keep the source artifact and treat every summary as a convenience layer over it.

She also tested the obvious adjacent tool and reported back:

We've tried a couple AI note takers and I was hopeful at first, but the output really hasn't been that useful for agency work. A transcript dumped into a file is not helping me much if somebody still has to sit there and read the whole thing and try and decide what matters, what's changed, what needs to be done, and what needs to be documented from an E&O standpoint.

A tool that produces an artifact nobody reads has added storage, not capability.

One question here goes to your own carrier, not to a vendor: when the error originates inside an AI tool your agency chose, does your professional liability policy respond, or is that a technology E&O question, or neither? The nearest thing to an answer we found, a March 2025 piece from the American Agents Alliance, is all mitigation advice and never addresses which policy pays. Ask in writing before the tool touches a client file, not after.

No one is really giving examples of what it's doing well

The most useful skepticism came from u/TraditionalCatch3796, in a 39-comment thread of agency owners reflecting on AI:

All I hear is people talking about how AI is going to take over, but no one is really giving examples of what it's doing well. I'd love some examples of what it's doing well other than reframing simple emails or giving ideas for spreadsheets or reframing spreadsheets etc. Feels like a lot of hype right now. [...]

He is not anti-AI. The half of that comment we cut goes on to say he would love AI to help with account-management work. He just wants an example. In the same thread, u/strikecat18, who describes themselves as a heavy AI user:

I'm techy and use AI a lot. I'm shocked how poorly accuracy has been for a while now and how much progress on that front has stalled. [...]

The concrete example that does exist is narrow, and worth reading closely for how narrow. In the Tennessee thread, u/joeboo5150 described Applied Epic's Renewal Insights comparing a renewing policy line by line against the expiring one: "It caught that the pricing changed, and the deductibles changed (client has diminishing deductibles)" [self-reported-by-a-redditor]. Two qualifiers the enthusiasm usually loses. It was an auto policy, so this is personal lines, not the commercial book. And the deductible moved because the contract says it moves, which is the easiest class of change to detect. That is still what a good example looks like: bounded, checkable, and honest about its own scope. A commenter in the same thread put the limit well, that the review is ten minutes and the follow-through is two days.

The bad example is what a carrier pushes at you unasked. u/Garrett4Real, on the State Farm side, in the 36-comment thread above:

At State Farm, there is a new AI tab that pops up by default in ECRM for every single customer every single time you access their page/account- no way to turn it off [...] It adds time, adds clicks, and is was wrong the one single time I actually used it.

There is a reason the hype smells wrong when you search this topic. One vendor page ranking for these terms prints a breakdown of manual certificate errors totalling a 9.2% error rate, with no source attached to the table at all, and cites Swiss Re one line below it for a completely different number. The same page makes three separate claims that open "According to NAIC" without naming a single NAIC publication. Those numbers may well be right. They are unfalsifiable, which, for a figure you are about to build a budget on, comes to the same thing. Ask every vendor, every time, for the document behind the number, and treat "according to" plus an institution's initials as no source at all.

Where AI is the wrong answer

Five places to keep it out, each for a reason.

Issuing a certificate with a non-standard additional-insured or waiver-of-subrogation endorsement. The owner above puts handwritten endorsements on his own failure list. And a 2026 review post from certificial.com states that over a thousand additional-insured forms exist with state-by-state legal variation, then says flatly: "No 2026 platform fully automates endorsement interpretation. Every major vendor still routes complex endorsements to human reviewers." Read that for what it is, a vendor grading its named competitors and putting itself top, which makes it a claim about the field rather than a confession. It is still the plainest statement of the boundary anyone selling here has put in writing.

Anything on scanned pre-2018 paper. "OCR quality kills the extraction." Extraction quality tracks document quality, and no model fixes a bad scan.

Consumer-facing chat that states coverage. u/geilt, who says he runs a platform supporting both human and AI agents: "They want to allow AI to sell insurance. Which I think is a horrible, horrible idea." And u/NeedleworkerChoice89, arguing that AI agents will struggle to get licensed to sell: "licensing will likely not easily fall for a variety of really good reasons." A tool that tells a client what is covered has effectively given advice you are licensed for and it is not.

Personal ChatGPT accounts holding dec pages. Covered above. Business tier or nothing.

AI note-takers for agency meetings. Owner-reported as not useful for agency work today. Revisit in a year.

What this actually costs

Almost nobody here publishes a price. Certificate Hero has no pricing page at all, the URL 404s, and its homepage FAQ answers the cost question with: "We offer competitive pricing with options to suit various budgets. The cost depends on the type of certificate and the level of customization required." Quandri is the same, demo request only. Third-party figures circulate for both; we are not repeating any of them, because every one we chased traced back to a competitor's comparison page rather than the vendor.

One exception matters more than the rest of this section. Certificial publishes a price list, and on it the Agent & Broker tier is $0: issue smart COIs, respond to requests, let your clients self-serve. The money comes from the requestor side, the general contractor tracking your certificates, from $99 a month. Before you scope a build or a pilot with anyone, find out what a free tier does against your own book. The cheapest automation is the one you did not have to pay for.

Here is our own ladder, which we publish because the alternative is what you just read:

• Free AI opportunity audit at /ai-audit: fifteen to twenty questions, about five minutes, no cost.
• A $500 full audit if the free one surfaces something: read-only access, your top 3 opportunities ranked by ROI, a 90-day roadmap, and a fixed pilot quote. Credited against the pilot if you proceed.
• A fixed-quote pilot, typically $3,000 to $8,000 over 2 to 6 weeks, scoped to one specific piece of the workflow.
• An ongoing relationship after a pilot has proved itself.

Now the disclosure that belongs with it. Ready Bytes has not built or shipped a certificate or renewal-prep system for an insurance agency. We build document-extraction and back-office automation, and we would apply the pattern from Never Trust an AI Agent's Done: verify against the resulting artifact, not the system's own report of success. But we would be entering your trade, not returning to it. Price that in.

A perfectly good outcome of the free audit is that you buy something off the shelf. If a product already integrates with your management system and covers your certificate volume, buying beats paying anyone to build.

Start here

Before you take a single vendor call, go measure three things.

Count your certificate requests for two weeks, split into simple reissues and anything carrying a non-standard endorsement. The first bucket is the automatable one, and its size decides whether this is worth any spend.

Time one commercial renewal end to end, including the re-keying into your management system. That number, not the extraction time, is the baseline every ROI claim has to beat.

Then send two emails. One to your AMS vendor asking which AI features are generally available on your instance today and at what price. One to your E&O carrier asking how the policy responds when an error originates in an AI tool. The answers to those will tell you more than any demo.

---

Shyam Verma founded Ready Bytes in 2009 and has been building software since 2005. He writes about back-office automation, legacy modernization and applied AI at readybytes.in/blog.