Inxure integration
Claims that arrive by email move on to Inxure with the documents already requested.
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. Inxure stays your brokerage's system.
Book a demoWhat weighs on the team today
Claims with lots of emails in between
Customer, insurer, loss adjuster, repairer. A home claim can gather a long trail of messages before it closes, and each one has to be read and filed.
Documents that arrive in pieces
Photos in one email, the repair estimate in another, invoices a week later. Someone has to put it all together and see what is still missing.
Quotes across several portals
To offer the customer an alternative, the team logs into each insurer’s portal and enters the same details again.
One escape-of-water claim, through to Inxure
- 1An email arrives from the customer: “A pipe burst in the kitchen and there are stains on the downstairs neighbour’s ceiling. Photos attached.”
- 2Crafteer.ai reads it and extracts policy, insured address, date, description of the damage and the third party involved.
- 3Matches the details with the customer and the home insurance policy in Inxure and checks what is missing.
- 4The affected neighbour's contact details and a repair estimate are missing: 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 Inxure API makes available, and creates or updates customers when needed.
Claims
Crafteer.ai checks what the customer sent against the policy data in Inxure. 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 Inxure 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 Inxure?
No. Crafteer.ai works on top of Inxure, 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 Inxure?
Whenever Inxure 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.