Libax integration
Customer requests reach Libax already read and organised.
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. Libax stays your brokerage's system.
Book a demoWhat weighs on the team today
Quote requests that arrive in bits
“How much would it be to insure the new car?” The question comes by WhatsApp, the details arrive in pieces and the quote still has to be run.
The same data in Libax and on the insurer’s portal
Name, tax number, registration, date of birth. Typed into Libax and again into every portal where the quote is run.
Renewals that need each customer contacted
Every policy close to renewal needs a message, sometimes a new proposal. In a large book of business, some get left behind.
One motor quote request by WhatsApp
- 1A WhatsApp message arrives: “I’ve bought a car and would like a price for the insurance. Sending the registration and my licence.”
- 2Crafteer.ai reads the message and the details sent, and identifies the customer.
- 3Finds the customer in Libax and gathers the vehicle and driver details.
- 4With Mimic Task, runs quotes on the portals of the insurers the broker works with.
- 5Drafts the message with the options and prices; the team reviews and approves sending it to the customer.
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 Libax API makes available, and creates or updates customers when needed.
Claims
Crafteer.ai checks what the customer sent against the policy data in Libax. 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 Libax 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 Libax?
No. Crafteer.ai works on top of Libax, 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 Libax?
Whenever Libax 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.