Your service team spends its day on certificates, not on selling.

The work that fills an agency day is mostly the same twenty requests

Walk into any independent agency at ten in the morning and the service side is doing three things. Producing a certificate of insurance because a general contractor won’t let a sub on site without one. Sending an ID card to somebody sitting at the DMV. Telling a commercial client, again, what their renewal date is.

None of that is hard. All of it is interrupting. A CSR handling a real coverage conversation gets pulled out of it eleven times before lunch, and the eleven interruptions are the part nobody would miss.

What we actually build for an agency

Not one system. A small number of specific automations, picked because they take real hours off real people. We scope them after an hour of watching how your office already works.

• Certificate and ID-card requests — the request comes in by phone, email or web form, the assistant collects what’s missing (holder name, address, the job it’s for, whether additional insured is required) and hands a complete request to the person who issues it.
• Renewal runway — a sequence that starts well before the renewal date instead of two weeks after everyone got busy, with the reminders going to your producer as well as the client.
• Quote follow-up — the quotes that went out and went quiet. Most agencies lose these to nothing more sinister than a week passing.
• Missed-call text-back — every unanswered call gets a text from your own number within a minute, which matters most on the personal lines calls that shop three agencies at once.
• AEP season cover for a Medicare book — an assistant on the phone and the chat widget through October to December, when call volume triples and hiring for ten weeks isn’t realistic.

What it does not do, and this list is not negotiable

An insurance assistant sits closer to a regulated line than almost anything else we build, so the boundaries get written before the first script does.

• It does not quote coverage. Not a premium, not a range, not "usually around".
• It does not bind, endorse, or change a policy.
• It does not answer a claims question — whether something is covered, what the deductible does, what happens next. Those go to a person.
• It does not read a declarations page back to somebody and tell them what it means.

AEP is the season that breaks a Medicare book

From mid-October to early December a Medicare agency’s phone behaves like a different business. Every call is time-sensitive, most of them are the same handful of questions about what changed, and the enrolment work itself has to be done by a licensed person.

The split is unusually clean, which is why this works. The assistant answers the phone, confirms who’s calling, books the appointment with an agent, and sends the reminder. The plan conversation happens with the licensed agent, as it has to.

It runs inside your agency management system, not beside it

The thing that kills agency automation is a second place to look. If the assistant’s notes live somewhere your CSRs don’t open, the notes may as well not exist.

So it writes to what you already run — the AMS, the CRM, or the shared inbox — under your accounts, on your phone number, on your card. If we stop working together, the automation and everything it has collected stay with you.

Nobody is letting this run unwatched

Every conversation produces a transcript, and somebody in your office reads them. For the first couple of weeks that means all of them — that’s how the gaps get found, and there are always gaps in the first fortnight.

The assistant tells callers what it is. It doesn’t pretend to be Denise at the front desk, and it offers a person the moment anyone asks. It also doesn’t replace your service team. It removes the certificate requests so the same team can do the work that needs a license.

When we would tell you not to bother

A two-person agency writing a handful of personal lines policies a month doesn’t have an interruption problem worth a build. Neither does an agency whose real bottleneck is that the carrier portal is slow — automation can’t fix somebody else’s software.

The agencies this pays for are the ones where a CSR could tell you, without thinking, roughly how many certificate requests came in yesterday. That number is the business case.