Inbox empty, you decide

After three months, not only is every email handled, in your shared inbox and at your own address. Your whole team works more efficiently, that is our promise. We start with the inbox: your AI has a proposal ready for every message, with what Bombos remembers about the sender, and you approve it.

Book your half hour

Together we map what your AI forgets. Free, and the plan is yours, with or without Bombos. Join the plugin waitlist →

An email, a WhatsApp message and a colleague's phone note arrive one after another. Sanne picks what comes first; the rest waits.

Who Picks Up the Mail When It Arrives at info@ and at Everyone's Own Address?

At an office that manages homeowners associations, every manager has their own portfolio, and the mail still piles up. Residents write to info@, to their manager's own address and to the address for invoices. One resident reports a leak in the bathroom, another asks about service costs, and the cleaning company sends an invoice. Some of it is answered in two sentences, some of it belongs to a colleague, and the leak still needs a job order in your software. You sort that out message by message, all day long. At a bookkeeping firm the questions in between are different, and there too you look up the client's details first.

Doesn't a Rule in Outlook Solve This?

A rule sorts the mail in one inbox, but it does not look up the resident. What arrives at your colleague's address, that rule never sees. Outlook has categories and rules for sorting mail, and TwinQ is rolling out a mail assistant that sorts messages, places them with a homeowners association and a staff member, and drafts replies. So this work does not start from an empty table.

The moment a message needs details from your software, or an answer from another company, somebody has to gather that information before a reply can go out. After that, a leak still needs a job order in your software, and you now retype it from the email. That groundwork moves, it does not disappear.

Using different software? Bombos gives your AI what is in the software you already have, for example:

What Is Ready Before You Do Anything?

For the leak, the address, the contact details and the homeowners association are already sitting next to the message. Your AI reads the mail at the addresses you connect, looks up the resident or the client in your software and suggests the manager who has the building in their portfolio. The reason is right there, so you can see what the suggestion rests on.

The reply to the resident is ready too, with the report from the email and the details that were found next to it. You read what was reported, check that the address is right, adjust the reply and approve it. A question that takes two sentences to answer then only costs you the reading. For the leak, the job order for the contractor is ready as well, so you do not have to retype it from the email. The inbox is the first task, and every correction stays in the team's shared memory.

If the building belongs to a different manager, you correct the suggestion and say why. Bombos keeps that correction as a rule, and your AI uses it on the next message. If the memory does not say who a building belongs to, your AI asks. Filling in a name as a guess is not part of this.

Where Do You See What's Going On, Without Opening Your Software?

In one list, where the mail from every address comes together. You no longer divide it up in Outlook. After your approval, if your AI has a connection to Outlook and your software, it puts the approved documents where they belong: the reply with the resident in your own Outlook and, if one is needed, the job order with the contractor in your software. Every message names the manager picking it up, so you can see who has it and what is already on record.

Does It Stop With the Inbox?

No. Bombos is not just another inbox tool. The inbox is where it starts. Behind every email is more work like it: a job for the contractor, a question about service costs, a document that belongs in a client file. All of it leans on the same knowledge about your clients, your agreements and how you work.

Bombos is the memory layer under the AI your team already uses. Claude, Claude Code, ChatGPT, Copilot, Grok, Codex, Cursor or your own agents all draw on 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.

It runs in the cloud or standalone on your own server. One person can try the plugin with their own agents first, before the whole team joins.

How Do You Start, and What Does It Cost?

In the first week we sit with you and look at the mail, together with the managers who handle it now. Your AI asks which buildings belong to which manager and which messages go to the back office, such as the invoice from the cleaning company. We write those agreements down, so a message reaches the right manager, whichever address it came in at. Your mail stays in your own Outlook, and you do not need any experience with this kind of system.

First the inbox. Every correction becomes a rule Bombos keeps, so the next task starts from what you already agreed. For the recurring questions about service costs, a standard reply is waiting later on, with the reason attached, and you read it and say yes or no. The pilot runs three months for €3,000 €2,000, after that it is €1,000 a month, excl. VAT.

Price as of .

What Doesn't Go Out Without Your Approval?

You approve before any mail goes out or anything is booked or saved for good; you set that in the AI or agent itself. So a drafted reply about a leak does not mean a contractor has already been given the job. If only your colleague knows which manager a building belongs to, your AI asks once before it bases a suggestion on that, and Bombos keeps the answer. For every message you keep seeing what is ready and what has already gone out. Every message still needs someone to see it through, and that stays the case.

The first half hour · free

What does your AI forget?

  1. 01You tell us which AI you use and where it keeps starting over.
  2. 02We show what a shared memory changes there, on your own examples.
  3. 03You keep the plan, with or without Bombos.
Piet Baudoin
Piet BaudoinYou talk to Piet, from the Bombos teamDutch team from Utrecht and Nijmegen · data in Europe
We reply the same working day.