How does email filing put every email and attachment in the right file?
Email filing by hand leaves agreements in one person's mailbox; your AI reads the email and attachment, finds the matching client file with what Bombos remembers and puts the destination with the reason in front of you, and after your approval it goes into the file.
Works with SharePoint, ANVA, CCS, Convect and your own file and client systems.
The client file is the first task; every correction stays in one shared memory for every AI your office uses.
Together we map what your AI forgets. Free, and the plan is yours, with or without Bombos. Join the plugin waitlist →
This is how it goes now, and how it goes with Bombos.
"Where was that agreement again?" means searching three mailboxes and a folder.
Today a staff member decides which client and file each message belongs to, then puts it there by hand. Saving it is quick. Working out where it belongs is the real work. The email sits in Outlook and the file in SharePoint or your package. For claims, a message goes into the policy file in ANVA or CCS. In homeowners association management, email, documents and the work sit side by side in Convect.
The email and attachment sit ready at the right client file, with the reason attached.
Your AI reads what comes in, looks up details in your package and prepares a proposal to place the email and attachment in the right client file. The reason is included, so you can see why that destination was chosen. If it is unclear where the message belongs, your AI asks you. After you approve the proposal, and if your AI has a connection to your files, it saves the email and attachment in the file.
After three months, every email and attachment reaches the client file as soon as you approve it. Everyone knows where an agreement sits, even when the colleague who made it is away. The mailbox search is gone. Every correction has become a rule in the shared memory, and you see where each proposal came from.
What's ready for you then
- Never search three mailboxes for an agreement again
- Every email and attachment in the right client file
- Agreements stay findable when a colleague is away
- You approve, and see where each proposal came from
Where do you see that?
The proposals for emails and attachments sit on one list. Per proposal you see the reason and the status "ready for you" or "waiting on your input". For a proposal that is ready, you review the chosen destination. If your AI asks for your input, something is still needed to move forward. You do not need the package open to view and review the proposal.
After your approval the message sits in the file. With every proposal you see where it came from. The list of proposals and the client file each have their own role this way: on the list you review the work that is ready, in the file sits the approved email with the client.
How does it start?
In the first week we set up preparing email for the client files together. The setup conversation takes about an hour and covers the mailbox, where the client files sit, and your rules for keeping messages. You arrange access to the systems this task needs. If a file sits on a separate drive, access to that drive is part of the setup. You do not need to move files or learn a new file package. We also discuss how you recognize an unclear sender, something only a colleague knows today.
After that, your AI starts with proposals. The chosen destination sits ready for review. A corrected destination becomes the rule for the next email; Bombos keeps those corrections; without them, the memory does not hold how your files are organized. Once a task type has gone well for a while, you decide how much autonomy you give your AI, with Bombos as the memory underneath. Your approval stays needed before anything is kept for good. Adjusting is done with settings, without custom work or training. Even if you do not work with computers much, you set this up together.
The email into the client file is the first task, not the whole offer. We take your office through the setup. After that, every correction becomes a rule Bombos keeps, so the next task starts from what you already agreed. After three months, you no longer have to retype anything to know which client file an email belongs to.
From one mailbox to a whole office.
It starts with an email that belongs in the right client file. The real gain comes next: the agreements and rules behind it stay findable for everyone.
Bombos is the memory layer under the AI your team already uses: Claude, Claude Code, ChatGPT, Copilot, Grok, Codex, Cursor or your own agents. One plugin gives them all one shared memory: your team's knowledge, the rules it learns from your corrections, and what is already in your email, documents and business software.
You see where every answer came from. Bombos runs in the cloud or standalone on your own server, and one person can try the plugin with their own agents first.
The pilot runs three months for €2,000 instead of €3,000, then €1,000 per month, excl. VAT. Book your half hour 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: your AI reads it, finds the client and the details through Bombos 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 it has gone well for a while, you give your AI more autonomy step by step, with Bombos as the memory underneath.
What does Bombos not do here?
Bombos does not act here itself: it gives your AI the memory. Without a connection between your AI and SharePoint or your file system, it stays a proposal.
A proposed destination can be wrong and needs review before a message is kept for good in the file. Your approval is needed for that, just as for an outgoing message. If your AI is unsure about the file, it asks for your input. A file for which no access has been set up cannot serve as a destination today.
With an unclear sender, only the colleague who knows them knows which client they belong to. What is recorded nowhere, Bombos does not know. That is why your AI asks you once how such a sender belongs to a client, and Bombos keeps the answer, so the right destination is found next time.
Fetching the claim status at the insurer belongs to a separate task: the status question. For insurance this application covers claims only: no life insurance, no disability insurance and no health data. You approve outgoing messages to third parties, through any channel, before they go out, including correspondence around a file. You set that in the AI or agent itself. An attachment can only be found again once it is clear which client it belongs to.
What does your AI forget?
- 01You tell us which AI you use and where it keeps starting over.
- 02We show what a shared memory changes there, on your own examples.
- 03You keep the plan, with or without Bombos.
