That's a Monday, or eight messages of it. Sixty-four arrived since Friday, from seven directions, and the same two account managers are reading all of them before the phones start.
Read down the margin and a pattern shows up. Most of what arrived is information that needs to move: from a form into a client file, from a contract exhibit into a certificate, from an email into a change request. That's the part software does well, and it's most of the inbox. A smaller part needs judgment: a claim, a coverage question, a recommendation. That part stays with a licensed agent, every time.
Three notes are all it takes to sort it. Automate means filed and drafted, and nobody at the agency types it. Draft for review means software prepares it and a person sends it. Agent only means straight to a licensed agent, flagged, file attached.
Automate
The messages marked “Automate” are handled end to end. A website lead is read and filed as a new prospect, and the payroll and loss runs it didn't include get a draft request, ready to send. A carrier's cancellation notice is found, matched to the right policy and put in front of a person with the date. Nobody retypes any of it, and nothing goes out to a client or a carrier without a person pressing send.
What makes these safe to hand over is that they're internal and reversible. A prospect file with a wrong payroll figure is still inside your agency when an agent opens it to pick markets. A notice filed against the wrong policy costs a minute to move. That's a different class of mistake from a wrong coverage recommendation, and it's why the margin says Automate here and not further down the page.
Draft for review
A certificate of insurance is the clearest example. Real requests rarely say “send a COI”. They arrive as a contract exhibit from a general contractor's compliance desk, listing the endorsements the job requires. The certificate is drafted from the policy and compared against the policy's actual terms before anyone sees it. A request the policy plainly meets comes back as a finished certificate waiting for a click. A request with wording the policy may not support, like an additional insured, a waiver of subrogation or primary and noncontributory language, is pulled out and sent to an account manager with the mismatch highlighted. That's an E&O question, and software shouldn't be the one answering it.
Policy changes work the same way. A client writes “bought another F-250, financed thru the bank”, and that becomes a structured change request with the vehicle, the effective date and the lienholder, and the client is asked for the VIN and the bill of sale. A conditional renewal with a premium change gets matched and summarized. Then a person submits the change, and a person explains the increase. The typing is gone. The decisions aren't.
Agent only
A burst pipe in the shop is a claim. “Landlord says we need $2M aggregate. Do we have that?” is advice, and the answer depends on the lease. Neither should be answered by software, and neither should sit in a shared inbox behind a certificate request. The automation's whole contribution here is to recognize what they are and put them at the top of the right person's list, flagged, with the client's file attached.
I'd put binding, carrier selection and anything a licensed person signs in the same column. If it's the kind of message your E&O carrier would ask about later, it's Agent only.
Where it gets things wrong
It misreads. A scanned dec page can come back with the wrong limit or effective date. It mismatches: Ruiz Landscaping and Ruiz Lawn Care look alike to software. It can draft certificate wording the policy doesn't support and sound sure about it. And a claim written as a question, like the roof leak at the bottom of the last message in that inbox, can be sorted as a certificate.
That's why nothing leaves without a person, and why the first few weeks of any setup need someone checking the sorting itself, not just the output.
Mind the carrier portals
Some carriers don't allow automated access to their portals, so check your agency agreement before any software logs in for you. No time saving is worth an appointment. Prepared data should go through your comparative rater, or through a carrier's approved integration where one exists. Where neither does, a person keys it in from the prepared file. The typing is shorter even if the clicking stays. Quote intake and remarketing walks through this in detail.
Where to start
Look at your own inbox for one week and put one of the three notes on every message as it arrives. Tally them here if you like.
Tally a week of your inbox
Add one for each message as you read it. Nothing leaves this page.
- Automate
- Draft for review
- Agent only
Your biggest column is where to start.
Whichever note is biggest is where to start. For most agencies I'd expect it to be certificates or quote intake: high volume, clear rules, and a person still checks every one before it goes out. That combination is what makes a first project low-risk, and what makes it easy to measure afterward.
It's built to work alongside Applied Epic, AMS360, HawkSoft or EZLynx, not instead of them. How much it can read and write depends on each system's integrations, and I'd check that before anything is built. Your management system stays the record, and a licensed person does everything that needs a license.