How do you connect HawkSoft to your inbox so that a claim form lands in the right client file?
You connect HawkSoft to your inbox through the AI your team already uses, with Bombos as the memory underneath. That AI reads the claim form, Bombos gives it the client and the policy from HawkSoft, and it proposes the place in the file with its source and a draft reply. If your AI has a connection to HawkSoft, it files it there after your approval. It works next to HawkSoft, not instead of it.
Together we map what your AI forgets. Free, and the plan is yours, with or without Bombos. Join the plugin waitlist →
What Does HawkSoft Already Do, and What Not?
HawkSoft already does a lot by itself. Documents at the policy level are stored in HawkSoft, and your staff can drag them straight into an email. Virtual Printer captures a document or a carrier web page and attaches it directly to the policyholder's file, with a category that shows what kind of attachment it is. The Action Menu logs every client interaction, and documents it produces, such as an email, are attached to the Action Log automatically.
What arrives from outside is a different matter. A client emails a claim form with four photos of the same dent. Another sends a new vehicle as a change request, in a PDF with no policy number on it. A third forwards the renewal notice from the carrier with one question underneath. Today a CSR opens each email, reads the attachment, looks up the client and the policy in HawkSoft and files it by hand.
That preparation is what your AI does, with Bombos as its memory. It reads the email and the attachment, Bombos gives it the client and the matching policy from HawkSoft, and the AI proposes the place in the file with the reason and the source underneath and drafts the reply. If a rule lives only in someone's head, such as which forms go under the claim and which under the policy, the AI asks about it once and Bombos remembers it, so it counts the next time.
Which Tasks Run on HawkSoft?
Each task below starts with an email or an attachment in your inbox and ends, after your approval, in the client file in HawkSoft or in a reply to the client. The claim form is the usual first one, because it comes in every day and always needs the same lookup: which client, which policy, which file. The follow up email for a missing policy number and the answer to a status question work the same way, with the details from HawkSoft next to the draft. What your team learns on the first task carries over, because the clients, the policies and your way of filing stay the same. You start with one task, in the AI your team already uses. Bombos remembers what you agree and correct along the way, so the next task goes faster, and you do not need to be technical for that. One person can also try the plugin with their own agents first.
What Changes in Your Week?
On Monday morning your CSR no longer opens an inbox full of claim forms from the weekend. She opens a list of proposals: client, policy and file already found, the reason underneath, the confirmation ready to read. She checks, adjusts where needed and approves. The searching in HawkSoft stops, and the time goes to the client on the phone. Bombos is the memory under the AI your team already uses, such as Claude, ChatGPT or Copilot: it gives that AI the knowledge in HawkSoft and the way your office works, and every proposal shows where it came from.
It starts with one task. We set up the claim forms together with you, with your own HawkSoft and your own inbox, over a call and a shared screen. With every correction, Bombos remembers a rule about your way of filing. After that your own team adds the next task, and you can do it yourself. One person can also try the plugin with their own agents first, before the rest of the team joins.
What Doesn't Go Out Without Your Approval?
You approve before anything is saved in a client file in HawkSoft or a confirmation goes to a client. A confirmation says the form has arrived, not that the claim is covered. Bombos is for property and casualty claims only, not life insurance, disability coverage or health data. Where that limit sits, you set per kind of work in the AI or agent itself. With the first task, we go through it together with you.
Every proposal shows where it came from: which email, which record in the package and which agreement. For the work inside your office, such as looking things up, checking and preparing, you decide how much your AI does ahead of time; messages to customers and payments wait for your approval by default. A proposal can be wrong, even when the reason sounds believable. When in doubt, your AI asks instead of guessing, and Bombos remembers your answer for next time.
Bombos also works with EZLynx, QQCatalyst, and AMS360.
All tasks Bombos takes on are listed under use cases.
What does your AI forget?
- 01You tell us which AI you use and where it keeps starting over.
- 02We show what a shared memory changes there, on your own examples.
- 03You keep the plan, with or without Bombos.
