Your work OS · Insurance brokerage
Your insurance brokerage in ChatGPT.
Present your service areas and let customers describe their needs. A broker follows up; this enquiry journey does not recommend a policy or confirm coverage.
Illustrative client file
- Need
- Review cover after a change in activity
- Waiting for
- An updated company document
- Next step
- Check the insurer’s reply before following up
“Where are we with this client?”
Authorized context. Advice and decisions remain with the professionals.
What customers can do with your application.
What customers browse: The services and areas of support your brokerage makes public.
What you receive: The enquiry topic and useful contact details, without medical records or sensitive documents in the public journey.
Your benefit: Prepare the initial contact without treating the enquiry as advice already provided.
Which needs can your brokerage help with?
How can I request an appointment with a broker?
Please call me so I can describe my enquiry.
Illustrative examples of the journey to configure. A submitted enquiry is not an accepted service order or a confirmed appointment.
The assistant does not select a policy, calculate premiums or confirm cover. Claims and individual files remain in their authorised processes.
Your initial scope and extensions.
The Customer AI Application includes your company identity, an authorised offer catalogue, conversational search, contextual enquiries, an administration dashboard and WebApp, plus initial configuration and launch testing.
Additional team workflows: Documents, insurer responses, renewals, WhatsApp follow-up and colleague handovers.
Booking journeys, business integrations, private documents and the internal workspace are defined separately, according to available features and the quote. They are not automatically added to the customer application.
A call describes the need. A document arrives on WhatsApp. The insurer replies elsewhere. The team reconstructs the story before every follow-up.
The broker sees the client context, what is still missing and the next action before contacting them.
A day in practice
A handover. Not a fresh start.
An illustrative workflow across channels and colleagues, using the connections and access enabled for the team.
The client’s needs change
A business activity has changed. The client asks whether their current cover is still suitable.
One document is missing
The request identifies what is missing, who must provide it and what it will unblock.
The insurer replies
The reply stays connected to the original request, the quote and the earlier objection.
The broker takes over
The context and next questions are ready. The broker reviews the proposal and decides what to send.
In your daily work
The context that makes the next step useful.
The need comes before the proposal
A conversation can reveal the situation, the cover sought, an objection or a recent change. The broker reviews that context before considering proposals; an old statement may need to be checked again.
Quotes and outstanding documents
Keep the quote connected to the client need, the insurer’s response and open questions. A document request should identify who must supply it and what it will unblock.
Receiving a document does not establish its validity. A drafted reply does not constitute an insurer’s commitment.
Renewals and claims follow-up
A renewal begins with changes in the relationship, not just a date. Claims follow-up can keep track of contacts, documents and outstanding replies without being mistaken for a compensation decision.
Opportunities and continuity
An earlier refusal can explain why a request deserves another look. A call outcome should not erase that context. Authorized colleagues can see what still needs a callback or a decision, within the access rules of the client record.
Language and professional advice
A translation can help explain a request; the broker checks its meaning and prepares an appropriate response. The assistant must not invent commitments, exclusions or conditions.
The role of your professional systems
AlefOS does not calculate premiums, underwrite risk, automatically recommend policies, issue policies or decide claim coverage. Advice remains the broker’s responsibility, decisions belong to the insurer, and official records stay in the specialist systems.
Renewal: revisit the change, not just the date
A client has added a new activity. The broker checks what changed, asks for the missing document and compares the insurer’s response with the request. A colleague taking over sees the outstanding question and its owner. A reminder is not evidence of renewed cover.
Claims and portfolio follow-up
For a claim, distinguish the report received, the requested document and the insurer’s decision still awaited. For a new offer, revisit an earlier objection across authorized client context, then check whether it is still relevant before preparing a callback. These are two separate workflows; neither replaces professional advice or the insurer’s official system.
WhatsApp follow-up that the next broker can continue
The client sends a requested document on the configured WhatsApp channel, while the insurer replies through a connected mailbox. Keep the received exchanges, the outstanding question and the broker responsible for the next reply in the client context. A colleague taking over can ask a compatible assistant what still needs clarification, within their access. The official insurer decision remains separate from a message received or a follow-up prepared.
Modules for this workflow
Explore the functions behind the example.
Your organization, your AI OS
Start with one client journey.
Deploy this workflow in your company’s AI OS, under your brand. Together, define the capabilities, access and connections your team needs.