Back to insights

ATI Lab insight

AI Tools for Insurance Agents: What Writes to Your AMS

The AI tools worth buying for an insurance agency fall into five groups: phone receptionists, intake and quoting prep, policy data entry, certificates of insura...

Analysis for technology leaders and operators planning, buying, and governing AI systems.

AI Tools for Insurance Agents: What Writes to Your AMS

The AI tools worth buying for an insurance agency fall into five groups: phone receptionists, intake and quoting prep, policy data entry, certificates of insurance, and renewal follow-up. In each group, pick the tool that writes its output into your agency management system (Applied Epic, AMS360, EZLynx, HawkSoft) and logs what it did. A tool that leaves staff to re-key its output saves less time than its demo shows.

Most lists of AI tools for insurance agents rank products by features. We judge them on one question instead: where does the output end up? ATI Lab builds AI automations for agencies and other document-heavy firms, so we have an interest in this topic. Every vendor feature below was checked on the vendor's own website on 19 October 2026, and no vendor paid for a mention or saw this text before publication.

What is the AMS write-back test?

The write-back test asks whether a tool puts its result into the client record in your AMS, or leaves a person to copy it there. Your AMS is where your E&O documentation lives, where renewals are triggered and where the next CSR looks first. Output that stays in a chat window or a vendor dashboard has to be moved by someone, and that copying is usually the work you wanted to remove.

Tools sit on four levels:

0Writes nothing to the AMSStaff paste the output by hand. Example: general chat assistants. 1Writes a note or activityCall transcripts and email summaries filed on the client record. 2Writes policy fields after a person approvesPolicy intake agents and AutoFill: extract, propose, a CSR approves. 3Works outside the AMS, keeps its own logNo AMS connection or API fees; the record lives in the vendor's system.

Level 3 is a deliberate trade, and it can be the right one. COI ENGINE, a certificate tool, states that it runs completely outside your AMS so the agency pays no API access fees, and it keeps its own log of every certificate. The cost of that choice is a second place to look when a carrier or an auditor asks what was issued and when.

Should you check your AMS before buying an AI tool?

Yes. Applied Systems (Epic and EZLynx) and Vertafore (AMS360) now ship AI that writes into their own systems, so check what your current contract includes before you add a third-party tool. What we found on their sites on 19 October 2026:

Native features pass the write-back test by design. Specialist tools still win where the AMS has nothing comparable, which today is mainly the phone line and, for some agencies, certificates.

Which AI tools do insurance agents use, by category?

The table lists one or two named tools per category with the AMS behaviour each vendor describes on its own site. Prices are left out because we could not verify them for every tool.

CategoryExamples (checked 19 Oct 2026)What it automatesWrites to the AMS?Fits when
Phone receptionistSonant; LiberateAnswers, qualifies and routes calls; post-call notesYes, notes and call logs (Sonant lists Applied Epic, AMS360, EZLynx, HawkSoft; Liberate logs into HawkSoft)Calls go to voicemail or CSRs spend the day on routine calls
Intake and quoting prepSonant quote intake; Epic Conductor; EVA AutoFill (pilot)Captures risk details from a call, email or documentPrefills AMS or rater fieldsProducers re-key applicant data before every quote
Policy data entryVertafore Policy Intake Agent; Epic AutoFillReads policy documents into structured fieldsYes, after a person approvesCommercial policy detail is missing from the AMS because entry takes too long
Certificates of insuranceCOI ENGINE; Cassidy; Cara AIReads requests, matches the policy, drafts the certificateVaries: COI ENGINE runs outside the AMS; Cassidy pulls from and logs back to itCommercial book with daily certificate requests
Renewal and client follow-upApplied renewal insights; Vertafore Client CommunicationsCompares renewal terms, drafts and times client emailsYes, activity notes and synced contactsRenewal outreach lives in inboxes and spreadsheets
General assistantChatGPT, Claude, Microsoft CopilotDrafting, summarizing, explaining a formNoLow volume, or writing tasks no one needs to log

AI receptionists

An AI receptionist answers every inbound call, identifies the client, handles routine requests and transfers the rest to the right person. Sonant lists integrations with AMS360, Applied Epic, EZLynx, HawkSoft, Momentum and QQCatalyst, and describes post-call notes that update your systems. HawkSoft's announcement of its Liberate partnership describes transcription and logging of conversations into HawkSoft. Before you sign, ask which AMS object each call creates (an activity, a note, a new prospect) and test it on your own system. Our AI receptionist and AMS automation page shows the call flow we set up and the published results behind it.

What AI automation actually works for insurance brokers, with results?

The automations with published results are call answering, policy document intake and loss-run analysis; submission intake and certificates are newer and mostly measured by vendors. All the figures below come from vendors or studies. None of these agencies are ATI Lab clients.

  • Call answering. BIG Pickering Insurance went from a 12% to a 100% answer rate, with 600% ROI in the first month, and O'Connor Insurance Associates reported 8× ROI within 30 days and 58+ hours saved a month. Both are vendor case studies published by Sonant AI in its 2026 guide.
  • Loss runs and coverage comparison. A Best Practices agency reported 7.5 hours saved per staff member per week and 244% ROI from a platform covering loss runs, coverage analysis, SOV comparison and an internal Q&A agent, per the 2025 Best Practices Study as reported by Risk & Insurance in August 2025.
  • Policy intake. Vertafore states 86% time saved for its AMS360 Policy Intake Agent (product page, checked 19 October 2026).
  • Submission intake. Applied's Epic Conductor (launched 29 September 2026) quotes small commercial from email and tracks every submission in one workflow. It is too new for published agency results.
  • Certificates of insurance. COI ENGINE says a certificate that took a CSR 15 minutes becomes a 30-second review of a finished draft. That is the vendor's claim, checked on its site on 19 October 2026.

Our own closest evidence is from freight, which is a different industry with the same problem shape. A shipment-intake system we built and run reads inbound emails, validates the details and creates the bookings, with 95% less manual work and zero monthly entry errors. Policy documents and certificate requests are the insurance version of that email: a request arrives, the details get checked against a record, and something gets written to the system of record. For which broker workflows to automate first, and what the NAIC model bulletin asks of you, see our insurance broker automation guide.

When is ChatGPT or another general assistant enough?

A general assistant is enough when the task is writing or reading and nothing needs to be logged against a client: drafting a renewal letter template, summarizing a carrier bulletin, or explaining an endorsement to a new CSR. It writes nothing to your AMS, so anything client-specific has to be copied in by hand.

Keep client data out of consumer accounts. Applied's own help page for its built-in writing assistant recommends leaving personally identifiable information out of prompts. If staff will paste client details, use a business plan whose terms exclude training on your data, and treat it as a drafting tool whose output a licensed person reads before a client does.

What if your AMS has no API for the tool you want?

When the AMS has no usable API, the work can still be automated with browser automation that drives the same screens your CSRs use, with every action logged. This is slower to build and needs maintenance when a screen changes, so it should be treated as a maintained integration. We cover the options in how to integrate systems with no API, and our insurance broker briefing maps the agency workflows where we use it. A first custom workflow typically takes 6 to 12 weeks to go live.

What should you ask an AI vendor before buying?

Ask five questions, and ask for a demo on your own AMS rather than a sandbox:

  1. Which object does the tool create in our AMS: an activity, a note, a prospect, or policy fields?
  2. Who approves before anything is written or sent, and can we change that per task?
  3. What is logged for E&O, and where can we read it in a year?
  4. What does it cost per month at our call, policy or certificate volume, including any AMS API fees?
  5. What happens to our data and the logs if we cancel?

If you are weighing a custom build against a subscription, our AI agent cost breakdown shows what a custom agent costs to run per month.

Frequently asked questions

What is the best AI tool for insurance agents?

There is no single best tool. Start with the AI already in your AMS, then add a specialist where your AMS has a gap, most often an AI receptionist for the phone line. Choose between specialists on whether they write their output into your AMS.

Can AI tools write directly into Applied Epic or AMS360?

Yes. Applied's Epic Conductor and Vertafore's Policy Intake Agent write into their own systems after a person reviews the data, and receptionist tools such as Sonant list integrations with both. Ask each vendor which records it creates.

Are AI agents for insurance agencies different from AI tools?

Vendors use "agent" for software that takes a series of steps on its own, such as reading an email, finding the policy and drafting a certificate. In practice the useful question is the same for both: what does it write, and who approves it.

Is it safe to let AI issue certificates of insurance?

Let it prepare them and keep a licensed person on the send. A certificate that shows wording the policy does not support creates E&O exposure, which is why every certificate tool we checked keeps a person on review or sends unusual requests to one.

Do small independent agencies need AI tools?

Only where volume justifies it. An agency that misses calls daily or issues certificates every day will see the time back. One that handles a few requests a week may get more from the AI features already in its AMS and a general assistant for writing.

How this article was produced

Written by the ATI implementation team. Vendor features were checked on 19 October 2026 on Applied Systems, Vertafore, EZLynx, HawkSoft, Sonant, COI ENGINE and Cassidy pages; vendor-published results are labelled as such. AI assistance was used in research and drafting; a human owns every claim and recommendation in it.

Next step

Turn the analysis into an implementation decision

Bring us the workflow, business constraint, or architecture question. We will help define the practical next step.