How do you connect QQCatalyst to your inbox so that an email is filed under the right policy?
You put Bombos next to your inbox and QQCatalyst: it reads the email and the attachment, finds the contact and the policy in QQCatalyst and proposes where the file goes, with a draft reply. You press Approve in Bombos, and only then is the file stored and the reply sent. Bombos works next to QQCatalyst, not instead of it.
What Does QQCatalyst Already Do, and What Not?
QQCatalyst, by Vertafore, already does a lot by itself. The Mailroom, a feature you subscribe to, looks through the emails you send and receive and matches the email addresses with the ones in your contact records. With QQConnect you drag an email from Outlook onto a square on your desktop; it scans the message and a PDF attachment for contact and policy details, and when it finds a single match it attaches the file to that contact's policy. Automated emails and task management are built in.
The emails that need a person are the ones in between. A claim form arrives from a spouse whose address is not on file. A PDF carries a name but no policy number, and the client has three policies with you. A change request asks for a new driver and a new address in the same message. For these, a CSR picks the contact and the policy by hand and then writes the reply.
Bombos prepares exactly those. It reads the email and the form, looks up the contact and the policies in QQCatalyst, and proposes the policy with the reason underneath and the reply below it. If a rule exists only in your head, such as which address a family uses for claims, Bombos asks about it and records it, so it counts the next time.
Which Tasks Run on QQCatalyst?
Each task below begins with an email and ends, after your approval in Bombos, under the right contact and policy in QQCatalyst or in a reply to the client. The attachments that need a choice are a good first task, because a CSR handles them every day and each one takes the same few lookups. The follow up email for missing details and the recurring questions about a claim come next, with the policy details from QQCatalyst placed next to the draft. The Mailroom and QQConnect keep doing what they do; Bombos picks up the emails that are left for a person to decide. 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 emails that used to sit until someone had time for them get a proposal the moment they arrive. Your CSR spends her morning checking choices instead of making them from scratch, and the client gets a clear confirmation the same day. Nobody has to remember which of three policies a form was about. 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 it up together with you, with your own QQCatalyst and your own inbox, over a call where we look at the forms you file by hand today. Bombos asks which policy a form belongs with when that is not obvious, and we write the answer down. After that you can do it yourself: your team teaches Bombos the next task. Do more with the same team, and grow without adding a desk.
What Doesn't Go Out Without Your Approval?
Bombos stores no file under a contact or policy in QQCatalyst and sends no reply 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.