Inside InsuraMate
Certificates, calls
and inbox. Handled.
For independent insurance agencies with busy service teams.
Request a demo01 / Certificates
Certificates issued. From your AMS.
Please send our certificate to Northline Builders.
- Customer matched
- Policy fields checked against your AMS
- Standard certificate issued
Sent to the recipient. Logged for your team.
Certificate
of insurance
- Insured
- Cedar Lane Construction
- Certificate holder
- Northline Builders
Issued from your AMS policy
Special wording or missing information? Your team takes over.
Your agency remains the issuer of record.
02 / Calls
Calls answered.
In 85 languages.
English, Spanish and more. On your agency’s number, with your routing rules.
Your team gets the summary, recording and transcript in the portal.
Hear a real call
Certificate request
The caller was asked to email the certificate request.
The request
A certificate for a job.
Read the transcript
To make sure names, addresses, and other certificate details are perfectly accurate, COI requests need to be submitted in writing. Would you prefer to send the request via email or text message, or would you like to speak with customer service?
What do you need for a certificate?
Please send the certificate holder’s name and address, plus any written requirements.
03 / Inbox
Inbox sorted.
Replies drafted.
Important mail stays visible. Routine replies wait in your mailbox’s Drafts folder for your team to review and send.
See the connected toolsYour tools. Your rules.
We confirm the scope, configure your routing and test in your systems before going live.
From request to record.
Everything InsuraMate does ends in your systems. A standard certificate is issued from the policy data in your AMS and logged against the policy. A call ends with a summary and, with a supported AMS, a note on the client file. An email is sorted and, when it needs a reply, a draft waits for a person. Nothing happens in a separate tool your team has to check.
Calls, start to summary.
The call is answered on your existing number with your greeting. The caller is matched to their record, routine questions are answered from what is on file, quote requests and changes are taken down for a licensed producer, and a caller who asks for a person is put through after a check of that person’s calendar. When a caller reports a loss, the call is routed the way your agency chooses: to the right agent, or straight to the carrier’s claims department.
The summary goes wherever your team already works: Microsoft Teams, Slack or another messenger, email, your CRM or your AMS. You choose. After hours, nothing rings your team’s phones.
Setup and go-live.
Setup is included, and you approve every step that matters.
- We confirm your systems and the scope of the work before you sign.
- We connect your phone, service mailbox and AMS, and configure your greeting, rules and routing.
- We test the work with your team in your own system.
- Certificates can start as review copies, checked by a person before they go out.
- You approve go-live, and automatic certificates and AMS updates switch on only then.
Certificates, calls and the inbox together make up most of an agency’s routine work. See how an AI insurance back office compares with outsourcing it.
Product questions, answered.
Do we need a new phone number?
No. Calls are forwarded from your existing number. We check your phone system supports the forwarding before go-live.
Does it send emails on its own?
No. Routine replies are drafted for a person to review and send. Standard certificates go out through the approved certificate workflow, which is separate.
Which languages does it speak?
Conversations run in 85 languages, Spanish included, on the same number.
Where do call summaries go?
The summary goes wherever your team already works: Microsoft Teams, Slack or another messenger, email, your CRM or your AMS. You choose.
When does automatic work start?
When you approve go-live.