AI workflows for BubbleIn brokerage software

Covera builds AI workflows for insurance brokers. BubbleIn is a French brokerage software. No integration route is documented for BubbleIn, so Covera starts from what the agency can produce: the client list export, imported by the Covera team.

What Covera reads from the BubbleIn export

• Clients: names and contact details, from the one-sheet client list export.
• Policies: none, because the BubbleIn client list carries no policy.

Claims, receipts and documents are not imported, and nothing is written in BubbleIn.

What it unlocks, and what it does not

With clients in Covera, the carrier quoting workflow finds the client when a new file opens and prefills the risk profile with the known identity and contact details. The assistant answers questions on the imported client list.

Workflows that run on policies stay inactive for a BubbleIn agency: past-due collections, renewals and account rounding need to know what each client holds. This is said plainly before starting, so the agency knows which workflows it gets. The document collection workflow still works on files opened by hand or from quoting, since it does not need the policy book.

How it works in practice

The agency sends its complete client list export, never a partial extract, since an import rewrites every line it covers. The Covera team runs a test import, reviews the result, then writes the client list. The agency has no import screen: the export is a transition solution operated by Covera.

Keeping client records stable

The BubbleIn export does not include a client identifier, so Covera builds one from the client name. Two clients with the same name could swap their contact details from one import to the next. The durable fix is an export that includes the BubbleIn client identifier, which Covera asks the agency for.

Edits made in Covera are kept

Contact details corrected on a client record in Covera, such as a phone number, an address or a note, are stored next to the imported book: the next import does not overwrite them, and the record shows both values with a way to restore the original. The client identity stays the one in BubbleIn.

Limits

The client list is as fresh as the last export, with no live read and no document store access. A client created in Covera does not appear in BubbleIn: create it in BubbleIn, and it enters Covera at the next import. For French brokerages, data is stored in the European Union, and Covera does not train any AI model on agency data.

Other integrations

Covera also connects to other brokerage software used in France: Maia, Modulr, Excalibur, Coorty and Adhoc. Emails and documents come from Gmail, Outlook and SharePoint.