Piet BaudoinBy Piet Baudoin, updated September 26, 2026

How do you handle interview scheduling within the hour of an application?

Interview scheduling starts with a reply: your AI reads the application with what Bombos remembers and, if it runs on the mailbox, sets a personal draft reply ready within the hour, with three interview slots from your calendar, and you check it and send it.

Works with BambooHR and however your hours come in.

No applicant waits a week; your tone and recurring questions stay in one shared memory for every AI your team uses.

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 →

This is how it goes now, and how it goes with Bombos.

Now

Replies on jobs@ sit unanswered, and the best candidate has signed elsewhere in the meantime.

Today someone does the groundwork by hand, and a few days easily pass between the application and the reply. You read the message, look up what you need, and open the calendar for possible times. BambooHR can send standard messages for applications that enter through its applicant tracking system. A loose email on jobs@ still needs a personal answer to what this candidate wrote, not just an acknowledgment of receipt.

Withbombos

Within the hour a personal reply is ready, with three interview slots from your calendar attached.

Your AI reads the application, looks up the available details, and prepares a draft that answers the candidate's question. The reason is attached, so you can see why the reply fits. If you want to offer an interview and your AI has a connection to your calendar, it adds three available slots to the draft. Anything your AI is unsure about comes back as a question. You check the text and the times, then send the reply yourself.

After three months

After three months, no applicant waits a week for a reply. Bombos knows your tone and the questions that keep coming back, so you rarely need to change the drafts. You speak with more candidates in the same amount of time.

What's ready for you then

  • A personal reply ready within the hour
  • Three interview slots from your calendar already included
  • Meet good candidates before another company hires them
  • No application on jobs@ left unanswered

Where do you see that?

The prepared replies to applications sit on one list. Next to each proposal you see the reason and the status "ready for you" or "waiting on your input." You do not need to have your HR package open to view this list.

With "ready for you," the draft is there for your check. You read what your AI proposes to answer on the application received. With "waiting on your input," there is a question you answer first. That status makes clear where your information is needed to move ahead with the reply to the candidate.

With every proposal you see where it came from. In it you can see what happened after your check. With every proposal you see where it came from.

How does it start?

In the first week we discuss the replies on jobs@ together, in a setup conversation of about an hour. Which mailbox do you use, where do the details you look up sit, and which rules apply to your replies? We also agree who checks the prepared replies. A phone arrangement with a candidate that is not written down anywhere yet gets recorded in that conversation.

Your AI then starts preparing replies. This task type starts with proposals: the reply to the candidate sits ready for your check. Your corrections become the rules for next time. That is how you show how you reply to candidates and what needs to change in a draft. Bombos keeps only those corrections as rules for how you respond to candidates.

You keep working with your existing mailbox and package. Nothing needs to move and you do not need a course; we fill in the settings together. 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 set in the AI or agent itself that outgoing messages wait for your approval. With every proposal you see where it came from.

When you see the same kind of question come back, your AI proposes a standing way of answering, with the earlier replies as the reason. You say yes or no.

The replies on jobs@ are the start, not the whole offer. We take you through the first step; after that, every correction becomes a rule Bombos keeps, so the next task starts from what you already agreed. After three months, no applicant waits a week for a reply.

Meet more candidates, from one shared memory.

Fast-growing companies recruit constantly. That is exactly when jobs@ gets neglected, because everyone is busy with the work already on their desk. We start with that first reply.

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

  1. 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.

  2. 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.

  3. 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 your mailbox and calendar, it stays a proposal.

A candidate is not invited and not rejected without your approval. A draft reply does not take over that choice. For an invitation, if your AI has a connection to your calendar, it looks up interview slots and puts them in the draft; you decide which times you offer the candidate.

Bombos only knows the details about the candidate that sit in the mail, the text message, or the package. So it knows nothing of an arrangement you only made by phone and never wrote down anywhere. That is why your AI asks you once what you discussed with the candidate, and Bombos keeps the answer, so you can add that arrangement before using the reply. A proposal can be wrong even when your AI shows no doubt; the content needs a check before you use it in the reply.

You approve before any message goes to the candidate or the client, on every channel, even a short acknowledgment of receipt; you set that in the AI or agent itself.

The waiting time here sits in the groundwork for the reply.

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.