How do you answer the ten questions customers or residents ask every week from Outlook, with the real numbers from your software next to it?
An answer to a recurring customer question is a draft with the details found in the file, which you review before sending it from your own email.
Works in your own Outlook, next to your own software.
Recurring questions are where you start; every answer shows where it came from, and every correction improves the next one.
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.
"What is my notice period", "could you send the invoice again"; every time, someone types the same answer over again.
One customer asks about the contract term, another wants the invoice again. You know the wording by heart, but the detail sits with the contract, so you look up this customer's information in your software. In homeowners association management, that might be the resident's share in the reserve fund. At a bookkeeping firm, it might be a question about closing the year-end accounts. TwinQ has its own mail assistant that drafts answers from its property management software.
The answer sits ready in your own tone, with the real details in it instead of a stock text.
Your AI recognizes the question in the email and looks up the sender's details, with what Bombos remembers. For a contract question, a draft answer is ready with the contract term or notice period it found, and the information used sits beside it. You check the answer, adjust it and send it from your own email. If a detail is unavailable or its meaning is unclear, your AI asks for your judgment.
After three months, recurring questions take no effort from your team. The answer is ready with the right detail, and someone approves it. Meanwhile, a suggestion for the next recurring question is already waiting. Your team has time for customers who genuinely need attention.
What's ready for you then
- Recurring questions answered with this customer's details
- The contract detail is there, no searching required
- Nobody types the same answer again every week
- Every correction improves the next answer
Where do you see that?
Answers to recurring customer questions sit with the contract details found on one list of suggestions. Next to each suggestion is the reason and the status "ready for you" or "waiting on your input". For a contract question, that is where you review the contract details found and the text for the sender. They sit together, so you can check whether the text actually answers the question asked. Your software does not need to be open separately for that.
For a missing notice period, the request for your input sits next to the prepared answer. So a text that reads smoothly is not yet a complete answer. You review the content and give approval for the message. With every proposal you see where it came from.
How does it start?
In the first week we choose the first recurring question together during a setup conversation of about an hour. You show us the mailbox and the software and point out where the details we need sit. We fill in the rules: which detail belongs in the answer, and who reviews the draft? You give access to what is needed for that. Your existing email and software stay in use. Nothing has to move; you do not need to take a course or know much about computers. In that same conversation, we also bring up the fixed explanation you have been giving by phone for this question for years.
After that, your AI starts preparing that contract question. Every task starts with proposals. A correction to the detail used or the answer text becomes the rule for the next contract question. Bombos keeps those corrections as rules; without them, it does not know what information belongs in your answer. 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. You approve a message to the customer; you set that in the AI or agent itself. Choosing the mailbox, software and answer rules is done with settings, without custom work. After three months, the ten standing questions no longer cost you a day a week.
If the same question comes up again after that, a suggestion for a second recurring question sits ready, with the reason attached. This one question is the start, not the whole offer: we take you through the first one, and after that, every correction becomes a rule Bombos keeps, so the next task starts from what you already agreed.
From ten questions to one shared memory.
Ten questions that return every week may sound small. Yet they take time every week, and the answer always depends on the same contract details.
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 Outlook and your software, it stays a proposal.
If the information needed is not in the reachable email or your software, Bombos does not know it either. That is why your AI asks you once how you have been answering this question by phone for years, and Bombos keeps the answer, so that fixed explanation is in the draft right away next time. When in doubt your AI asks for your judgment. That also applies when the question uses the same words as an earlier message. The sender and the matching contract determine which details belong in the answer.
A draft with details found can also be wrong or incomplete. So reviewing covers both the text and the contract details used. You approve before outgoing messages go to third parties, whatever the channel, even for a recurring contract question. You set that in the AI or agent itself. An answer about a notice period also changes nothing about the contract itself. It states the information found; it is not a cancellation on the customer's behalf. The question repeats; this customer's details belong with it every time.
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.
