Case studies / The clicks nobody has to make
A property and casualty agency runs on AgencyZoom. The native automations handle the drips and the triggers, but the day is still full of clicking. Reading the inbound, creating the deal, sending the right template, moving the stage, setting the next task. We put Claude in the browser through the Chrome integration and let it do the clicking, so the producers could stay on the phone instead of in the CRM.
AgencyZoom does a lot for a P&C agency. Pipelines, native automations, reporting, the whole service side. But if you watch a producer's actual day, a surprising amount of it is still manual clicking inside the tool. A lead comes in, someone reads it, creates the deal, picks a template, sends it, drags the card to the next stage, and sets a follow-up task. None of it is hard. All of it is time, and it is time spent in the CRM instead of in front of a client.
Native automations cover the parts with a clean trigger. They do not cover the look-at-it-and-decide clicking in between, and that is where the day quietly goes.
Instead of bolting on another tool, we let Claude operate AgencyZoom the same way a person does, through the browser. The Chrome integration lets Claude see the page that is on screen and act on it. Click, type, and read the result back. AgencyZoom itself does not change at all. It just has a fast, consistent operator working inside it.
The core of it is the new-business workflow, the same sequence a trained CSR runs for every lead. Claude does each step on the live screen.
Because it is reading the actual page, it handles the parts a rigid automation chokes on. A name in the wrong field, a template that depends on the line of business, a stage that should only move once a condition is met. It looks at what is there, does the sensible thing, and leaves a clean record behind.
Here is the split. AgencyZoom's own automations were already doing the easy, trigger-based work. What was left was the clicking that needed a human to look and decide. That is the column Claude took over.
Across a representative day, this is the volume of admin the agent quietly handled. Every one of these was a click, or a few, that a producer would otherwise have made.
The producers did not get a new dashboard to learn. They got their afternoons back.
A browser automation working inside an agency's CRM has to be trustworthy, so the setup is deliberately boring about it.
The reason this was a short build and not a long migration is that nothing got replaced. The agency kept AgencyZoom, kept their pipeline, kept their templates. Claude just sits on top of all of it.
That is the part agencies actually care about. They did not buy a new system or retrain a team. They kept the tool they know and put a tireless operator inside it.
If your producers spend more time in the CRM than on the phone, this is the kind of build I do. Tell me your workflow and what eats the day, and I will tell you honestly what is worth automating and what is not.
Tell me about your workflowHow an agent drives a real browser to operate the tools you already use.
The voice version. Dialer recordings transcribed, qualified, and filed.
The outbound version. Scrape, verify, qualify, and send, end to end.
Advisory and build engagements on systems like this one.