How do you connect HawkSoft to your inbox so that a claim form lands in the right client file?
You put Bombos next to your inbox and HawkSoft: it reads the claim form in the email, finds the client and the policy in HawkSoft and proposes the place in the client file, with a draft reply to the client. You check the proposal and press Approve in Bombos. Only then does the form go into the file and the confirmation go out. Bombos works next to HawkSoft, not instead of it.
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 Bombos does. It reads the email and the attachment, finds the client and the matching policy in HawkSoft, proposes the place in the file with the reason 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, Bombos asks about it and records 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 Bombos, 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. 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?
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. 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.
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. Every correction you make teaches Bombos your way of filing. After that your own team adds the next task, and you can do it yourself. Do more with the same team, without a new system and without coming back to us for every step.
What Doesn't Go Out Without Your Approval?
Bombos saves nothing in a client file in HawkSoft and sends no confirmation to a client 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 EZLynx, QQCatalyst, and AMS360.
All tasks Bombos takes on are listed under use cases.