Gemese integration
Claim notifications that arrive by email get prepared in Gemese.
Crafteer.ai reads the claim notification, checks it against the policy, asks the customer for anything missing and prepares the claim. It only stops for your team to approve the notification to the insurer. Gemese stays your brokerage's system.
Book a demoWhat weighs on the team today
Claim notifications keyed into Gemese by hand
Policy, registration, date, place, description. Every notification that arrives by email is read and typed again into the system.
Missing documents requested one at a time
First the accident report is missing, then the driving licence, then the photos. Each request is a new email and the case stalls in the meantime.
Customers asking how their claim is going
“Any news?” The question arrives by email and WhatsApp, and someone has to check the file to answer.
One motor claim notification, through to Gemese
- 1An email arrives from the policyholder describing a bump in a car park, with two photos.
- 2Crafteer.ai reads it and extracts policy, registration, date, place and description.
- 3It checks the data against the customer and policy in Gemese and sees what's missing.
- 4The accident report and driving licence are missing: it drafts the request to the customer.
- 5With everything in, it prepares the notification; your team reviews and approves sending it to the insurer.
How Crafteer.ai helps
Customers and policies
To handle a request, Crafteer.ai needs to know who the customer is and which policies they hold. It reads customers, policies and anything else the Gemese API makes available, and creates or updates customers when needed.
Claims
Crafteer.ai checks what the customer sent against the policy data in Gemese. If anything is missing, it drafts the request to the customer; if everything is there, it goes as far as notifying the insurer, where it waits for your team to approve.
Renewals
Crafteer.ai finds the policies due for renewal in Gemese and compares the renewal price with the current one. When they differ, it alerts your team, runs quotes with other insurers through Mimic Task and drafts the message to the customer, by email or WhatsApp, for approval.
Approval where your team wants it
Each procedure sets what waits for approval. Emails and messages to customers, for example, can sit in a card in the chat with the draft ready: your team approves and sends them, or asks for changes in writing or by voice.
FAQ
Does Crafteer.ai replace Gemese?
No. Crafteer.ai works on top of Gemese, which remains the broker’s management system. It reads what arrives by email and WhatsApp and prepares the work for your team.
How does Crafteer.ai connect to Gemese?
Whenever Gemese has an API, we connect through it. When it doesn't, we use other integration techniques, assessed case by case during setup.
What about work on insurer portals?
It's done by Mimic Task, from the same company, which connects to Crafteer.ai. Today it runs quotes and other tasks on the Ageas, Allianz, Asisa, Divina Seguros, Fidelidade, Lusitania and Tranquilidade portals, using the brokerage's own credentials.
What about requests made by phone?
Scriva, from the same company, transcribes calls and turns them into whatever the call was about: a request, an activity or a new customer in Crafteer.ai.
Does the claim notification to the insurer wait for approval?
Yes. Crafteer.ai does the rest of the work and stops at sending the notification to the insurer, for your team to review and approve. Other steps follow whatever the brokerage sets in each procedure.
Who handles implementation?
The LucidHorizon team, after a demo. Timing depends on each company and is assessed after the process review.