Skip to content
How it works

What happens to a call, a certificate request and an email.

InsuraMate connects to the AMS, phone line and inbox your insurance agency already runs. It finishes the routine work inside them, and anything it cannot verify goes to a person on your team with the reason attached.

Book a 15-minute call

Fifteen minutes with Aiste, our CRO.

Your systems

1. It connects to what you already run.

InsuraMate works inside your agency management system, on your existing phone number and in the service inbox you already have. The work lands where your team already looks: the activity on the client file, a draft in Outlook or Gmail, a card in Teams.

Your number stays yours. Calls forward to InsuraMate for the hours you choose, and you can pull the forward back yourself at any time.

What it reads and writes

  • Finds the caller by phone number, and the policy by policy number.
  • Writes the call summary to the client file, and creates new callers as leads.
  • Reads each person's calendar before it transfers a call.
  • Logs every read and write to the call or request it came from.
Calls on your main line, email in your service inbox and texts on your text line come in to InsuraMate. The work lands on the client file in your AMS, as drafts to approve in Outlook or Gmail, and as call cards to claim in Teams. WHERE WORK ARRIVES Main line Service inbox Text line InsuraMate Your AMS the client file Outlook or Gmail drafts to approve Teams cards to claim WHERE IT LANDS
Integrations

Live inside five agency management systems today.

Nexsure, AgencyZoom, QQ Catalyst, AMS360 and NowCerts, with HawkSoft and Applied Epic in rollout. Tell us what you run and we will say where it stands on the call.

Agency management

  • Live

    Nexsure

    Two-way sync between InsuraMate and your Nexsure agency management system.

    Nexsure, in detail
  • Live

    AgencyZoom

    Connect InsuraMate to your AgencyZoom workflows so calls become tracked deals automatically.

    AgencyZoom, in detail
  • Live

    QQ Catalyst

    QQ Catalyst integration that turns inbound calls into structured AMS activities.

    QQ Catalyst, in detail
  • Live

    AMS360

    Two-way sync between InsuraMate and your AMS360 agency management system.

    AMS360, in detail
  • Live

    NowCerts

    Two-way sync between InsuraMate and your NowCerts agency management system.

    NowCerts, in detail
  • In rollout

    HawkSoft

    Two-way sync between InsuraMate and your HawkSoft AMS.

    HawkSoft, in detail
  • In rollout

    Applied Epic

    Applied Epic integration with customer match, call logging, and policy lookups.

    Applied Epic, in detail

Phone and text

  • Live

    Twilio

    Twilio is the carrier under InsuraMate's voice channel. Bring your own Twilio account or use ours.

    Twilio, in detail

Email

  • Live

    Outlook

    Connect Outlook so InsuraMate can triage your agency inbox and draft the replies.

    Outlook, in detail
  • Live

    Gmail

    Connect your agency's Gmail or Google Workspace inbox to InsuraMate.

    Gmail, in detail

Team chat

  • Live

    Microsoft Teams

    Every call posted to your Teams channel as a card someone can claim in one click, with reminders until they do.

    Microsoft Teams, in detail
  • In rollout

    Slack

    The same claim-and-chase call workflow, for the agencies that run on Slack instead of Teams.

    Slack, in detail

CRM

  • Live

    Keap

    Keap CRM contacts are kept in sync with every call InsuraMate handles.

    Keap, in detail
  • In rollout

    Salesforce

    Salesforce integration for agencies running Sales Cloud or Financial Services Cloud.

    Salesforce, in detail
  • In rollout

    HubSpot

    HubSpot CRM integration. Calls become tracked deals automatically.

    HubSpot, in detail
The work

2. It does the routine work, start to finish.

Three pieces of work land on whoever is nearest at an insurance agency: the certificate request, the call and the service inbox. Each one is finished inside your systems and logged where your team will look for it.

Certificates

What it does

A certificate of insurance request arrives by email or text. InsuraMate matches the policy in your AMS, issues the standard certificate, sends it and logs it on the client file, in minutes, any hour. Vehicle-schedule certificates are included, and every VIN is checked against the policy before anything goes out.

Where it stops

Additional insured, waiver of subrogation or primary and non-contributory wording goes to your licensed person with the request parsed and the policy already matched. Missing fields, unreadable requests and duplicates stop.

How it handles a trucking agency's 2am certificate

Calls

What it does

Every call on your existing number is answered in the caller's language, 85 languages with a mid-call switch, after hours and overflow first. The caller is matched in your AMS, the summary and recording are logged, and new callers become leads. Transfers check the person's calendar first, offer a callback, and ring the whole team if no specialist is free.

Where it stops

Inbound only. It never places a call, never states a premium and never binds. It recognizes a claim and sends it to the right person with a summary, and it does not take the claim itself. Callers are told they are speaking with an automated assistant, and you write the greeting yourself.

Every call on your own number is answered in the caller's language, 85 languages with a mid-call switch, matched in your AMS by phone number, and answered from the documents you upload and your AMS rather than general knowledge. It hands the call over three ways: a transfer, with the person's calendar checked first; a claim, to the right person; and a price question, to a licensed producer, never a premium. After every call the summary is logged on the client file, and new callers become leads. ON EVERY CALL A call on your number after hours and overflow first Answered in the caller's language 85 languages, switched mid-call Matched in your AMS the caller, by phone number Answers come from your documents and your AMS, not general knowledge IT HANDS OVER Transferred calendar checked first A claim to the right person A price question never a premium Logged after every call The summary on the client file. New callers become leads.
What happens to a claim call at midnight

Service inbox

What it does

A shared service inbox at an agency of 7 to 25 people takes thousands of messages a month, and most of it is carrier marketing and bulk mail. InsuraMate watches that inbox and the text line, clears the bulk, surfaces client work and carrier notices, and drafts the routine replies.

Where it stops

Every draft waits in your own inbox for a person to approve. Nothing sends itself.

How the inbox works in Outlook
Your team decides

3. Anything it cannot verify goes to a person.

About 400

standard certificates issued to date, and not one went out with a field that did not match the policy in the AMS.

The AI reads the request and decides nothing. Software checks every field against your AMS. Anything it cannot verify stops before it goes out, and your licensed person gets the request with the reason attached.

  1. Request arrives

    By email or text.

  2. Policy matched

    In your AMS.

  3. Every field checked

    • Named insured
    • Policy and dates
    • Holder, from the request
    • VINs on the schedule

Then one of three things happens

  • Issued and sent

    Logged to the client file.

  • To your licensed person

    Special wording, request attached.

  • Stopped for your team

    Missing, unreadable or a duplicate.

The controls, on from day one.

See the full list of what it refuses to do
It shadows before it works

On your real calls and certificate requests, it issues nothing and answers nothing. Your team reads what it would have done, and you say when it goes live.

Review copies while you watch

Every certificate it generates can go to your service team before the requester sees it. Your team decides when that comes off.

Special wording is never issued

Additional insured, waiver of subrogation, primary and non-contributory: those requests go to a licensed person every time, whatever your settings say.

Duplicates never go out twice

A repeat request goes to a person in every deployment. So does anything incomplete or unreadable.

It never quotes or binds

A caller asking for a price has the details taken and handed to a licensed producer. It never states a premium.

A claim goes straight to a person

It recognizes a claim, pulls up the policy and sends the call to the right person with a summary. It does not take the claim.

Transfers check the calendar first

A transfer looks at the person's calendar before it rings them, and rings the whole team if no specialist is free.

One click claims a call

The team sees who has it, so two people never ring the same client back.

Drafts wait for approval

Every inbox reply waits in Outlook or Gmail for a person to approve. Nothing sends itself.

Your number stays yours

Calls forward for the hours you choose, and you can pull the forward back yourself at any time.

Whose hours come back

The routine work stops landing on whoever is nearest.

Your payroll does not drop. What changes is what your licensed people spend the day on.

  • The seven o'clock call

    Answered on your number, matched in the AMS and logged, instead of waiting for whoever carries the phone that night.

  • The Monday certificate

    Issued from the policy in your AMS at any hour, instead of sitting in a licensed agent's queue.

  • The service inbox

    Sorted before anyone opens it, with the routine replies drafted, instead of taking a CSR's morning.

  • The note after every call

    Written and logged to the client file, instead of five minutes of typing for whoever took the call.

Run it against your own numbers
How it starts

Connected in one to two weeks. Live when you say so.

  1. We connect

    Your phone system and your AMS. Your number stays your number.

  2. You load

    Your greeting, your SOPs and your knowledge base. You edit them yourself in the portal, any time.

  3. It shadows

    On your real calls and certificate requests. It issues nothing and answers nothing.

  4. You say go

    Evenings, weekends and overflow first if you prefer, and you decide when it widens.

Questions

What owners ask about how it works.

Does my team have to learn a new system?

Not for the daily work. Call summaries and certificates land in the AMS activity on the client file, inbox drafts wait in Outlook or Gmail, and call cards can arrive in Teams. The portal is where you change the greeting, the SOPs and the knowledge base, and where every call keeps its summary, recording and transcript.

Where does it get its answers on a call?

From the documents you upload and the policy data in your AMS. It is instructed not to answer insurance questions from general knowledge, and it never states a premium or binds coverage.

Will it work with my AMS?

Live today on the AMS side: Nexsure, AgencyZoom, QQ Catalyst, AMS360 and NowCerts. On the CRM side: Keap. Email runs on Outlook or Gmail, alerts on Microsoft Teams, voice and SMS on Twilio, and transfers check the agent’s Outlook or Google Calendar before they ring. In rollout: HawkSoft, Applied Epic, Salesforce, HubSpot and Slack. Tell us what you run and we will confirm where it stands on the call.

What happens to a certificate request it will not issue?

Nothing goes out and nothing is written back to the client file. The request goes to your team with what it understood, what it could not resolve and the reason, and the decline stays on the record.

Can we start with evenings and weekends only?

Yes. Calls forward for the hours you choose, so evenings, weekends and overflow can come first, and you decide when it widens.

Watch it work on your own AMS.

Fifteen minutes. We walk through a call and a certificate request the way your customers send them, on your AMS.

Book a 15-minute call
Aiste Buinauskaite, CRO at InsuraMate AI
Aiste Buinauskaite
CRO. Runs every customer conversation.