How do you answer "what is the status of my claim" in one line when the status sits in the package, the email and the insurer's extranet?
Bombos gets an answer ready from the email, your package and the insurer's extranet once that access is set up, and you send it after your approval.
Works with SharePoint, ANVA, CCS, Convect and your own file and client systems.
The status question is where it starts, then the same team helps more clients, does it better and teaches Bombos the next task.
This is how it goes now, and how it goes with Bombos.
"What is the status of my claim?" One line of question, three systems of answer.
Today a staff member gathers the status from the package, the email exchange and the insurer's extranet, then writes one answer. A client asks where their claim stands. You check ANVA or CCS for the policy details and read the latest messages. If the current status only sits with the insurer, you still have to retrieve it from the extranet before answering the client.
The answer is ready, built from the package, the latest email exchange and the insurer's extranet.
Bombos reads the status question, looks up information in your package and email, and prepares a draft answer with the reason included. If the claim status sits in the insurer's extranet, Bombos retrieves it once that access is set up. It does not fill in unavailable information. Instead, it asks you what is missing. You read the draft, add what is needed and send it.
After three months, the answer to a status question is ready before you start searching. You read it, add anything that is missing and send it. Clients hear sooner where things stand and need to call less often. Your team handles more claims with the same people and teaches Bombos the next task itself.
What's ready for you then
- Every status question has an answer ready to send
- Package, email and extranet combined in one answer
- Clients hear sooner where their claim stands
- Phone agreements count once Bombos knows them
Where do you see that?
The proposed answer to the status question sits in Bombos on one list, with the reason attached. You see the status "ready for you" or "waiting on your input". The package does not need to be open to read the draft. The draft shows the details Bombos found in the email and the package. If the status from the insurer's extranet is needed, it sits there with the draft once that access is set up.
The status of the proposal is about the work in Bombos. It is not the claim status at the insurer. That difference matters when reviewing: a draft that is ready is a text to read, not a decision about the claim. You add to the answer and send it. Every action with an effect outside Bombos is recorded in a log you can look through. That keeps visible what was done outside Bombos.
How does it start?
In the first week we go through, in about an hour, which mailbox and which package you use for claim questions. You decide which rules apply to preparing answers and arrange access to the systems for that task. We also go through a phone agreement about the claim that is not recorded anywhere yet.
Nothing moves, no new package is added and no course is needed. Adjusting means filling in settings, not custom work. Even if you do not work with computers much, we set up the preparation together. After three months, the answer to a status question is ready before you have checked three places.
After the setup, Bombos puts the first task live at "proposing". A correction to the claim answer becomes the rule for the next reply. Without that explanation Bombos does not learn what you want to read differently. Once the preparation goes well for a while, you decide whether that task type moves to "run after approval" or "run on its own". Your approval stays needed for outgoing answers.
The status question is the first task, not the whole offer. We take you through the setup. After that your own office teaches Bombos the next task. If the same status question comes from another client, the next draft is already there before you ask, with the reason attached.
One answer, and a team that handles more.
The status question returns every day, and each time someone checks three places. Remove that work and you see what the same people can handle. For an office that is growing fast without wanting to grow headcount, that is the point: more work with the same team, and clients who receive a better answer.
Then your team teaches Bombos the next task itself, without needing to be technical. By simply working with Bombos, your people naturally learn how to use AI. We guide you through the first step. After that, you can do it yourself. That is exactly the intention. We do not want you to keep coming back to us.
Compare it with a new coworker: it costs less than half a day a week of the person you would otherwise hire. Leave your number and we will call you back to talk through your situation.
What Bombos does, in three steps
It reads what comes in
An email, a message, a photo or a PDF: Bombos reads it, looks up the client and the details in the systems you already have, and sees what is missing.
It drafts the work, you approve it
The proposal sits on one list with the reasoning next to it. You read it, adjust it and approve. Only then is anything sent, booked or filed.
It remembers what you decide
Every correction becomes the rule for next time. Once a kind of task has gone well for a while, you hand it over step by step, and you check the log afterwards.
What can Bombos not do here today?
What is recorded nowhere, Bombos does not know. An agreement you made over the phone sits in no system at all. That is why Bombos can interview you: it asks what was agreed with the client by phone about this claim, so that it counts in the answer next time. If information is missing, that question stays open in the draft. When unsure, Bombos puts the question to you instead of guessing. A proposal can be wrong and needs review before use in the claim answer.
This application for insurance covers claims only. Life insurance, disability insurance and health data fall outside it. Bombos never sends messages to third parties without prior approval from a staff member, through any channel. For an answer about the claim status that limit is technically enforced. Only Bombos can switch it off, at your explicit request and at your own risk. That approval is also required to keep a change for good in the file. A draft answer therefore does not mean the claim status in your package has already been updated. For a short answer, the latest status has to be gathered first.