From a request a business posted
Month-end review across several bookkeeping platforms
Staff log into each client's platform one by one at month end, then re-enter the figures into a review sheet by hand.
Insurance agencies
In an independent agency, the account manager keeps the client record in EZLynx, HawkSoft, Applied Epic or AMS360, but every carrier site asks for the same facts again. A Medicare agent can type one client's name, birth date and ZIP code four times in a morning, and a P&C account manager does the same for each added car or new address.
Who does what
What you get
Draft for review
The rules it follows
These are your company's own rules, written down and confirmed with your team during the build. It works on its own only within limits you set.
What it learns when your team adjusts its work
The busywork it takes off the licensed account manager. It takes the retyping of names, birth dates, addresses and vehicle details into each carrier site off the account manager. That time goes back to the work only they can do.
What it starts out knowing
It works from these sources, shows which one an answer came from, and asks when the answer is not there.
Who reviews its work, and when review can stop
At first the licensed account manager reviews every prepared form line by line. For a routine type, such as an address change with nothing else attached, that line-by-line review stops once the agent's record on them is good and the agency agrees. A licensed person still approves and submits every change to the carrier.
Anything that touches coverage, new drivers, lienholders or a client's choice of plan keeps going to a licensed person.
It no longer needs review once its record on them is good and you agree, one type of task at a time. New, unusual and high-stakes work stays with a person.
When your team adjusts its work
When the account manager adjusts a drafted home address change so the auto policy's garaging address changes too, that is saved as a rule: an address change updates both policies. Next time, the agent prepares both changes together. The team decides what it learns and can change or remove that rule.
It learns how your company does this job. It does not watch, rate or profile your employees. Your team decides what it learns. You can read everything it has learned and remove anything. Whoever runs it, your team or our engineers, makes sure on a regular cycle that what it learned stays inside the bounds you agreed.
From a request a business posted
A Medicare agent described opening a carrier site and keying in one client's name, birth date and ZIP code, the fourth site that morning to ask for the same facts. The tools they had tried handled pieces of the work. Renewals, commissions, follow-ups and working out which plan a client had picked still fell to them.
Paraphrased from a public post, not quoted, and not a client engagement.
From first principles
Before we build anything, we take the work down to what has to be true. What is left over is habit. Habit gets deleted, not automated.
What has to be true
What is only habit
Typing the facts again from one screen into another is habit, not a requirement. So is keeping a side spreadsheet of which carrier or plan a client ended up with, when the management system can hold it.
What we delete before building anything
We drop the side spreadsheet that tracks submissions and the second round of typing confirmations back into the client file. Where the management system already downloads changes from a carrier, we leave that carrier alone.
What is left
The agent. The agent reads the client record or the client's email, fills each carrier's quote or change form, and saves the confirmation and policy details back to the client record.
A person. The licensed account manager checks each prepared form, settles any coverage question with the client, and submits it.
The kind of work: Systems that don't talk to each other. This is the work of carrying the same facts from one system into another: a client's details into each carrier site, a client's figures into a review sheet, a booking into a door code. Connecting the systems moves the data, but it does not read the email, check the figures against the rules or chase the missing piece, so people still do that part by hand.
What the engagement needs
A login to the agency management system (EZLynx, HawkSoft, Applied Epic or AMS360) with access to client records and activity notes, plus agency logins to the carrier sites the team uses most. We also need a few recent change requests and the agency's list of which changes need a licensed person.
We check the time this job takes, access to your systems and how you would review the result. If a ready-made tool is enough, we say so.
Senior engineers agree the rules with the licensed account manager, test on past cases and set approval limits and a way to switch it off.
Work with the agent in Slack, Teams or text messages. We fix problems and adjust it as unusual cases come up.
You own the agent and keep its source, tests and guide either way. Your team runs it, or our engineers run it with a monthly report. Learning continues on your own servers, in your own cloud account or in our data center.
When we'd point you elsewhere
The fit test checks this first. If one of these covers your case, we tell you, and you keep the map of the work.
Honest limits
The agent prepares forms and records. It does not give coverage advice, and when a carrier site changes its form, the work goes back to a person.
The situation on this page is drawn from a public request a business posted, paraphrased, not a client engagement.
More use cases
From a request a business posted
Staff log into each client's platform one by one at month end, then re-enter the figures into a review sheet by hand.
From a request a business posted
The front desk reads every booking, change and checkout email, then sets each guest's door code by hand.