How it works
Clover works the way a sharp licensed CSR would. Around the clock.
It reads every client message and every COI request. It drafts what should go out. It tracks every policy renewal in your book. And it always escalates the questions that require a license.
The five things
What Clover does, in plain English.
It handles certificate of insurance requests in seconds.
Clover reads every inbound COI request, identifies the certificate holder and any additional insured language, matches the request to the right client and policy in HawkSoft, and populates the ACORD 25 or 28 form using the policy data directly from your AMS. The certificate is queued for one-click producer approval, never auto-sent. Every certificate issued is logged as a note on the HawkSoft client record.
It drafts every client response in your producer's voice.
When a client emails or texts the agency, Clover reads the message, classifies its type (FAQ, billing question, policy change, claim, coverage question, general inquiry), and either drafts a response or escalates it. Drafts use the producer's voice and signature, pulled from voice samples captured during onboarding. The producer reads the draft for ten seconds, clicks approve, and it sends from their actual email or SMS line.
It runs the renewal pipeline year-round.
Clover reads policy renewal dates from HawkSoft daily. At 90, 60, and 30 days out, it surfaces what is coming on the producer's daily briefing. At 60 days (or whatever lead time the producer sets), it drafts a warm renewal touchpoint message in the producer's voice. It tracks who has responded and who has not. Non-responders get surfaced early enough to make a personal call before the renewal moves to a competitor.
It intakes every claim, around the clock.
When a client reports a claim by email or text, Clover acknowledges receipt within 90 seconds, asks the structured intake questions (date of loss, location, description, police report number, injuries, business interruption), and produces a clean intake summary for the producer. Emergency situations (bodily injury, total losses, active loss events) escalate immediately to the producer with no draft created.
It does whatever else you ask, through chat.
Open the chat and tell Clover what you need. 'Pull all commercial renewals in the next 30 days.' 'Find every COI request from Henderson Contractors this year.' 'Draft a follow-up for Apex Construction.' 'Summarize the last six months of communication with the Nguyen account.' Clover picks the right tools, does the work, reports back, and shows exactly what it did in the activity log.
What it connects to
It works with the systems you already use.
Clover connects through real APIs, not browser scraping. That is what makes it fast, reliable, and on the right side of every system’s terms of service.
Agency Management
HawkSoft
Policies, clients, contacts, log notes, certificates, renewal dates. HawkSoft remains the source of truth for your book. Clover reads it daily and writes back every action it takes.
Gmail and Outlook
Each producer connects their own inbox during onboarding. Clover reads, drafts, and (with your approval) sends from your actual account, with your actual signature.
SMS
Twilio
A dedicated agency-wide SMS line for client communication. Clover handles inbound texts, claims acknowledgments, and routine outreach via SMS as fluidly as via email.
Documents
Google Drive
Maintains a consistent folder structure by client and policy. Files signed certificates, renewal confirmations, and policy change packages into the right place.
Certificates
ACORD 25 & 28
Direct population of ACORD 25 (liability) and ACORD 28 (property) certificate templates from HawkSoft policy data. Certificate accuracy comes from your AMS, not from transcription.
Reasoning
Anthropic
Clover is built on Claude, with strict zero-data-retention. None of your client or policy data is ever used to train AI models. That is contractually committed and passed through to your agency in writing.
Setup is roughly 15 to 20 minutes per integration during onboarding. We do it with you. EZLynx, NowCerts (Momentum), and DocuSign integrations arrive in Phase 3.
Approval modes
You decide how much rope Clover gets. Within the limits the architecture sets.
Different producers want different levels of oversight. Clover respects that, at the agency level, the producer level, and the client level. With one exception: certificates of insurance always require producer approval, regardless of any other setting.
Most cautious
Draft and review
Clover drafts everything. Nothing leaves the agency without you clicking approve. The default for every agency during shadow mode and most agencies in production. The approval inbox is fast: keyboard shortcuts, batch approval for routine COI requests, approve and next flow that processes 30 drafts in 5 minutes.
Balanced
Auto-send FAQ, draft for everything else
Clover auto-sends approved FAQ responses (billing, ID cards, office hours, payment methods) without your approval. Anything that requires judgment still drafts and waits. You configure what counts as an FAQ for your agency during onboarding.
Most autonomy
Auto-send routine, escalations and certificates always pause
For producers who have worked with Clover long enough to trust it (typically after the first few months), Clover can auto-send most routine communication. Scope escalations, claims acknowledgments, and certificates of insurance always pause for you. Per-client overrides let you tighten the rope on a sensitive account.
COI approval is hard-coded. No setting can change it. Every certificate is reviewed before it leaves the agency.
What Clover doesn’t do
The work Clover won’t touch.
There is a category of agency work Clover is built to refuse, even when asked. This is not a disclaimer. It is an architectural rule. The list is short, deliberate, and permanent.
Soliciting, negotiating, or placing insurance
Clover never recommends a carrier, never quotes a premium, and never takes any action that constitutes the sale of insurance. It is an unlicensed employee by design and stays inside that boundary.
Coverage adequacy commentary
Clover never tells a client whether their coverage is sufficient, what they need, or whether their limits are appropriate. Coverage advice is licensed work. The producer is the one who answers those questions.
Carrier portal submission
Clover never submits applications, endorsements, or change requests directly to a carrier. It collects the information, organizes it, and produces a clean package for producer review. The producer submits.
Claims interpretation or advocacy
Clover captures intake information and escalates emergencies. It never advises on a claim's merit, predicts coverage outcomes, or advocates with adjusters. Those are licensed judgments.
Auto-sending COI certificates
Certificates of insurance are legal documents. Clover never auto-sends them, regardless of any other auto-send setting. Every certificate is reviewed by the producer before it leaves the agency.
Compensated work tied to policy sales
Clover does not perform any work for which an agency would be paid commission. The work it does is administrative and clerical, by architectural intent. The producer earns the commission; Clover does the paperwork.
Final execution of legal documents
Clover can draft renewal acknowledgments, policy change confirmations, and standard correspondence. Clover cannot send a final policy change submission, COI certificate, or any legally binding document without explicit producer approval at the moment of execution.
The boundary is the product. Not a footnote on the product.
See it yourself
The demo is more useful than the page.
30 minutes. We show you Clover handling real COI requests, drafting client responses, intaking a claim, and refusing the things it should refuse. You will know whether it is right for your agency before the call ends.