How Do You Automate COIs Safely?

You automate COIs safely by automating request details and reminders, not coverage decisions. If 20 certificate of insurance (COI) requests save 5 minutes each, your team gets back 100 minutes a day.

A good COI process saves customer service representative (CSR) time while keeping coverage decisions with the agency. Send coverage questions, requested endorsements, limit changes, and unusual wording to the agency employee authorized to review them, and follow your state’s licensing rules and errors and omissions (E&O) procedures.

TL;DR: Automate the parts that waste time: taking the request, asking for missing details, confirming the deadline, and logging the transcript. Keep coverage wording, endorsements, limit changes, and final review with your agency team. If 20 requests save 5 minutes each, that is 100 minutes back in one day.

How Big Is the COI Problem in a Small Agency?

COI work looks small one request at a time, but the daily math can get ugly fast. If your agency handles 20 requests a day and saves 5 minutes on each one, that is 100 minutes a day before anyone changes coverage, reviews wording, or sends the certificate.

That 20-request example is not an industry benchmark. It is a simple way to price the interruption that many commercial lines teams feel during renewals, endorsements, and certificate season.

Example Requests Per Day	Minutes Saved Per Request	Time Back Per Day	Time Back In 5 Workdays
5	5	25 minutes	2 hours 5 minutes
10	5	50 minutes	4 hours 10 minutes
20	5	100 minutes	8 hours 20 minutes
30	5	150 minutes	12 hours 30 minutes

The payroll cost is only part of the story. The interruption hits when a CSR is trying to finish renewals, quote an endorsement, or call back a commercial client before lunch.

The Bureau of Labor Statistics reports that customer service representatives earned a median $20.59 per hour in May 2024. Your true agency cost is higher after payroll taxes, benefits, training, management time, and mistakes.

COIs are also not generic paperwork. ACORD lists certificate forms, including the liability certificate agencies use every day, on its official forms page at ACORD.org.

That is why I would not treat every COI request as a clerical task. The request may be routine. The coverage question may not be.

How Are COI Requests Usually Handled Today?

In agencies I talk with, COI requests often arrive by phone, email, text, website form, and producer notes. That can work at low volume, but it falls apart when the caller gives half the details and expects a certificate in ten minutes.

Here is the normal pattern I see in independent agencies:

1. A contractor calls and asks for a COI.
2. The CSR asks for the certificate holder name.
3. The caller does not have the mailing address.
4. The CSR asks the caller to email the details.
5. The email arrives with special wording.
6. The CSR stops and checks the policy.
7. Someone asks later, "Did that COI go out?"

The problem starts when the agency receives an incomplete request. The ACORD form is not the first issue.

The agency loses time when it has to ask the same questions twice. It loses more time when a producer has to interpret a vague note like "send cert to general contractor."

This page focuses on COI request automation for insurance agencies. For a narrower setup guide, read my separate post on how COI request automation should work.

What Parts Of COI Work Should You Automate First?

Automate the parts of COI work that do not require coverage judgment: taking the request, asking for missing information, confirming urgency, and sending a complete note to the right agency person. Do not let software decide coverage changes, policy interpretation, endorsement status, or final certificate wording.

Automate the request before you automate the certificate.

That means the AI receptionist should make sure the CSR has a complete note before opening EZLynx, HawkSoft, Applied Epic, AMS360, QQCatalyst, or another agency management system (AMS).

These are starting targets, not industry benchmarks. Adjust them after you measure your own requests.

Step	Who Handles It	Suggested Target
Answer COI call or website chat	AI receptionist or CSR	Immediate
Collect named insured and caller info	AI receptionist	1 minute
Collect certificate holder details	AI receptionist	1 to 2 minutes
Ask about special wording	AI receptionist	30 seconds
Flag additional insured or waiver requests	AI receptionist	Immediate
Review policy and wording	Authorized agency employee	Agency rule
Send certificate and log notes	CSR or account manager	Agency rule
Update caller if details are missing	AI receptionist or CSR	Same day

A good process separates facts from judgment.

Facts are holder name, address, email, job name, due date, and requested wording. Judgment is whether the policy supports the request.

Where Should AI Help, And Where Should A Person Stay Involved?

Use AI to take the request, collect missing holder details, record the deadline, and flag special wording. Keep an agency employee involved when the caller asks about coverage, endorsements, limits, or contract language. The AI receptionist should document the request, not decide whether the policy satisfies it.

Here is the practical split.

COI Task	AI Can Help	Agency Team Must Decide
Caller wants a standard COI	Collect the facts	Final send rules
Holder name is missing	Ask for it	No coverage decision
Caller asks for same-day service	Mark urgency	Staffing priority
Caller asks for additional insured	Capture exact wording	Coverage and endorsement review
Caller asks for waiver of subrogation	Capture request	Policy and endorsement review
Caller asks to raise limits	Capture request	Producer or authorized review
Caller asks if coverage applies	Stop and send to a person	Coverage answer
Caller is upset	Gather facts calmly	Relationship call if needed

A certificate is tied to coverage, contracts, and E&O procedures. Treating it like a simple PDF can create bad habits.

The CSR should get a complete request without taking another call. The agency still decides what can be issued.

What Should The COI Script Ask?

Your COI script should ask the same plain questions every time. The goal is to stop vague notes and give the CSR enough information to act without calling the insured back, unless the request needs coverage review or missing contract wording.

Use something like this for phone, text, or website chat:

"I can help get that certificate request to our team. What is the named insured on the policy?"

"Who should be listed as the certificate holder? Please include the full legal name and mailing address."

"What email address should we send the certificate to?"

"Is this for a job, lease, vehicle, event, or contract?"

"Do you need any special wording, such as additional insured, waiver of subrogation, primary and noncontributory, or a specific project description?"

"When do you need this by?"

"Our team will review the request. If the wording affects coverage, the agency employee authorized to review it may need to check the policy before the certificate goes out."

That last line sets the right expectation without scaring the customer. It also keeps the AI receptionist or unlicensed staff member from sounding like they approved coverage.

If the request includes commercial application data, ACORD fields matter too. This ACORD 125 and 126 field map can help your team keep terms straight.

How Would This Work On A Real Tuesday?

A realistic COI day is not clean. It is a mix of contractors, landlords, vendors, and one angry caller who says the job starts tomorrow. A controlled process should make each request complete, documented, and clear about who must review it.

At 8:12 a.m., a plumbing contractor calls before your office opens. He needs a COI for a school project by noon.

The AI receptionist answers and asks for the named insured, certificate holder, school district address, job name, delivery email, and deadline. The caller says the general contractor also wants additional insured wording.

That request should not be treated as a simple certificate.

The transcript should say something like:

"Urgent COI request. Named insured: [ABC Plumbing]. Certificate holder: [Sample School District], [address]. Job: [North Gym Repair]. Due by noon. Caller requests additional insured wording from general contractor contract. Please review coverage before sending."

At 8:35 a.m., the CSR opens the AMS, checks the policy, and reviews the endorsement status. If the policy and agency procedures support the wording, the CSR issues the certificate and logs the activity.

At 9:05 a.m., a second caller asks for a plain landlord COI with no special wording. That can move faster under the agency’s standard rules.

At 11:40 a.m., the plumbing contractor texts back asking for status. The agency can reply with a plain update instead of taking another phone call.

Nobody guessed at coverage. Nobody promised an endorsement. The CSR started with a complete request instead of a voicemail.

Where Does Sera Fit For COI Requests?

Sera fits before the CSR starts the certificate, when calls, texts, and website chats interrupt the team. Sera does not replace your CSR, issue certificates, bind coverage, quote premiums, give coverage advice, or file claims with carriers.

At Twig, we built Sera to answer these calls and collect the details before a CSR starts the certificate. Sera is an AI receptionist for independent insurance agencies.

Sera answers calls, texts, and website chats 24/7. She asks why the person is calling, collects the needed details, and books a time with your team.

For COIs, that means Sera can answer the call, ask your standard COI questions, flag special wording, and send the transcript to your team. Every conversation is logged with a full transcript.

Sera can also handle missed-call text-back, live transfers to a person, appointment booking, and multi-language conversations on the Growth plan and above. Pricing starts at $49 per month, and every plan starts with a 15-day free trial, voice included, with no credit card.

You can see current plan details on our pricing page.

Sera has no direct connection to EZLynx, HawkSoft, Applied Epic, AMS360, or QQCatalyst. She can send notes by email or to Gmail, HubSpot, Salesforce, or Slack. Your team must then complete the certificate and record the work in the AMS.

Twig is SOC 2 Type II certified. Twig is not HIPAA compliant and does not sign BAAs.

Most businesses are live in under 30 minutes by forwarding the phone line or adding the website chat. If you want the plain definition, read what an AI front desk is.

You can also call Sera’s live demo line at (650) 795-7838.

What Should You Do Next?

Start with one rule sheet before you buy or change software. Write down which COI requests are standard, which need CSR review, and which must go to a producer, principal, or another authorized agency employee.

Then write your script.

Use the same questions for phone, text, email, and website chat. Make sure every request captures holder name, address, delivery email, deadline, and special wording.

After that, use the AI receptionist to take calls and collect the required details.

If your team is drowning in COI calls, start by having AI answer and collect complete requests. Do not start by auto-issuing certificates with no human review.

A controlled way to automate COIs is simple: less phone tag, fewer vague notes, and no pretending that coverage judgment is clerical work.