How do you connect EZLynx to your inbox so that an attachment ends up under the right policy?
You put Bombos next to your inbox and EZLynx: it reads the email and the attachment, finds the client and the policy in EZLynx and proposes where the document goes, with the reply already drafted. You read the reason and press Approve in Bombos. After that the document is on the record and the reply goes out. Bombos works next to EZLynx, not instead of it.
What Does EZLynx Already Do, and What Not?
EZLynx already does a lot by itself. EZLynx for Outlook, the plug-in for Microsoft Outlook, builds a bridge between EZLynx and your inbox. You add emails and attachments to records in EZLynx, identify existing customers and prospects and see their contact details, and add them to or remove them from email campaigns, all without leaving Outlook.
Plenty still arrives the ordinary way. A client writes from a different address than the one on file. A body shop sends an estimate for a claim, with the client named only in the subject line. A client with a home and an auto policy emails a claim form without saying which one it is about. Someone at the agency reads it, works out the client and the policy, saves the attachment and writes back.
That judgment is where Bombos starts. It reads the email and the form, compares the details with what EZLynx has on the client, and proposes the policy and the document folder with the reason underneath and a draft reply. What only your senior CSR knows, such as how a certain carrier's forms are filed, Bombos asks about and records, so it counts the next time.
Which Tasks Run on EZLynx?
Each task below starts in your inbox and ends, after your approval in Bombos, on the client record in EZLynx or in a reply to the client. Filing incoming attachments is the natural first task: it happens every day, it takes the same lookup every time, and you can check the result in seconds. Emails that arrive without the details you need, and the shared inbox that three people read, follow the same pattern and make a good second step. Each one uses what EZLynx already knows about the client, so the proposal starts from your own records. You start with one task. After that, your own team teaches Bombos the next one, and you do not need to be technical for that.
What Changes in Your Week?
The question "did that form come in?" gets an answer the same day, because nothing waits in one person's inbox anymore. A producer who opens a client in EZLynx finds the latest estimate and the reply that went out, filed under the right policy. Your team reviews proposals instead of hunting for them. That is how the same team does more work, at a higher quality, for less than half a day a week of the employee you would otherwise hire.
You start with one task. We set up the attachments together with you, with your own EZLynx and your own inbox, and we go through the first proposals with you on a call. When you correct one, you say why, and Bombos uses that reason on the next form. After that you can do it yourself, and your team teaches Bombos the next task. Do more with the same team, and keep the way you already work.
What Doesn't Go Out Without Your Approval?
Bombos saves no document on a record in EZLynx and sends no reply to a client or a body shop until someone at your agency has pressed Approve in Bombos. A confirmation says the form has arrived, not that the claim is covered. Bombos handles property and casualty claims only, not life insurance, disability coverage or health data. That limit is always on. Only Bombos can switch it off, at your explicit request and at your own risk.
For every step you can read back afterwards what happened and why. For the work inside your office, such as looking things up, checking and preparing, you decide how much Bombos does ahead of time; messages to customers and payments always wait for your approval. A proposal can be wrong, even when the reason sounds believable. When in doubt, Bombos asks instead of guessing.
Bombos also works with HawkSoft, QQCatalyst, and AMS360.
All tasks Bombos takes on are listed under use cases.