Piet BaudoinBy Piet Baudoin, updated September 27, 2026

How do you connect QQCatalyst to your inbox so that an email is filed under the right policy?

You connect QQCatalyst to your inbox through your team's own AI, with Bombos as the memory underneath. That AI reads the email, Bombos gives it the contact and the policies, and it proposes the policy with its source and a draft reply. If your AI has a connection to QQCatalyst, it stores it there after your approval. It works next to QQCatalyst, not instead of it.

Book your half hour

Together we map what your AI forgets. Free, and the plan is yours, with or without Bombos. Join the plugin waitlist →

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.

Your AI prepares exactly those, with Bombos as its memory. It reads the email and the form, Bombos gives it the contact and the policies from QQCatalyst, and the AI proposes the policy with the reason and the source underneath and the reply below it. If a rule exists only in your head, such as which address a family uses for claims, the AI asks about it once and Bombos remembers it, so it counts the next time.

Which Tasks Run on QQCatalyst?

Each task below begins with an email and ends, after your approval, 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; your AI, with Bombos as its memory, prepares the emails that are left for a person to decide. 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?

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 works because Bombos is the shared memory under the AI of your team, whether that is Claude, Copilot or your own agent: it reads what is already in QQCatalyst and the inbox, keeps the rules it learns from each correction, and shows where every answer came from.

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. When it is not obvious which policy a form belongs with, the AI asks, and Bombos remembers the answer. After that you can do it yourself: with every correction Bombos remembers a rule, so the next task starts from what you already agreed. 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 a file is stored under a contact or policy in QQCatalyst or a reply 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.

All integrations

Bombos also works with HawkSoft, EZLynx, and AMS360.

All tasks Bombos takes on are listed under use cases.

The first half hour · free

What does your AI forget?

  1. 01You tell us which AI you use and where it keeps starting over.
  2. 02We show what a shared memory changes there, on your own examples.
  3. 03You keep the plan, with or without Bombos.
Piet Baudoin
Piet BaudoinYou talk to Piet, from the Bombos teamDutch team from Utrecht and Nijmegen · data in Europe
We reply the same working day.