Before the
reply goes out.
Review a customer-facing message before an AI assistant sends it. Decide which replies should come back to your team.
HUMAN OVERSIGHT FOR BUSINESS AI
AI acts.
You
decide.
Before a reply is sent or a record changes,
your team should have a say.
We’re building approvals, pause controls and a clear
record of the actions your connected AI takes.
ABB / CONTROL CONCEPT — 001
A HUMAN CHECKPOINT.
AI AGENTS / LLM APPLICATIONS / AUTOMATIONSSEE THE IDEA
01 / WHEN AI TAKES ACTION
The next step matters.
Keep your team in the decision.
A customer reply sent. A contact record changed. A workflow triggered. We’re building Agent Black Box so business teams can decide which connected actions proceed, which need approval and when to pause.
For people responsible for operations, customer service and business systems in growing businesses.
REVIEW THE REQUESTSee what’s
See what’s
about to change.
A connected system requests an action.
Your team sees what it wants to do
and which record or recipient is involved.
MAKE THE DECISIONLet routine work
Let routine work
follow your rules.
The plan: allow routine actions, block others
and hold selected requests for approval
before they can proceed.
REVIEW THE OUTCOMEA record you
A record you
can follow.
See the request, the decision and the result.
An approval isn’t proof of completion.
Unconfirmed outcomes stay visible.
HOW THE PRODUCT IS INTENDED TO WORK
CONCEPT VISUALISATION
02 / TRY A HUMAN CHECKPOINT
Need a moment?
Press pause.
Pause the example, then try a new action. It will be blocked until you resume.
Interactive simulation with fictional activity. It isn’t connected to your AI tools. In the planned product, pause applies to new actions through the controls we connect; it doesn’t undo completed work or guarantee stopping work already underway.
BLACK BOX / SIMULATION RUNNING
FICTIONAL ACTIVITY
NO BUSINESS TOOLS CONNECTED03 EVENTS
03 / WHERE WOULD A CHECKPOINT HELP?
Start with one
business action.
Examples we want to explore with operations and business-system owners. These are proposed pilot use cases, not available integrations.
Before the
Before the
record changes.
Check a proposed update to a customer record. Approve the specific change, or reject it before it reaches the connected system.
Before the
next step runs.
Add a checkpoint before an agent or automation triggers a follow-up task. Pause new connected actions while your team investigates.
04 / A FOCUSED START
One workflow.
An agreed scope.
A pilot conversation starts with the action you want more control over and the tools your team already uses.
Choose the action.
Identify what needs approval, who should decide and what a useful record would show.
Understand the setup.
Each protected action needs an integration. We would agree supported systems, technical help and setup effort before a pilot. A developer or implementation partner may be needed.
Prove it with sample data.
The proposed first step is a contained test of approvals, pause and outcomes before considering live use.
Today: a local prototype with mock actions. Live integrations and customer access are still in development.
05 / BEFORE YOU EXPLORE A PILOT
A few useful
answers.
Who is Agent Black Box for?
We’re starting with small and growing businesses using AI or automation to take actions in their tools. The best fit to explore is an operations, customer-service or business-system owner who can name one action that needs more oversight. Smaller enterprises and implementation partners are welcome to discuss a focused use case too.
Is it only for automation workflows?
No. We’re designing for connected actions from AI agents, LLM-powered applications and conventional automations. That could be an assistant sending a reply or a workflow changing a record. It doesn’t automatically monitor every AI conversation or guarantee the accuracy of an AI answer.
Will it work with the tools we use?
That needs to be assessed for your workflow. No live integrations are available today. Each protected action must be connected so it cannot skip the permission check. Setup may need technical help; there is no universal, one-click connection.
What if our workflow already has approvals?
Those may already cover your needs. A pilot conversation would explore any remaining gaps in visibility, permissions or pause controls across the actions you care about. We’re testing whether a separate control layer would add enough value.
What does Pause actually stop?
In the planned product, it blocks new actions through the connected controls and invalidates queued permissions. Resuming would require fresh permission for cancelled requests. Pause cannot undo completed actions or guarantee cancellation of work already in progress.
Is there a product I can use today?
There is a working local prototype with approvals, rejection, pause and saved mock records. It uses fictional activity. Live integrations, customer sign-in and production readiness are still being developed. The interactive example on this page is a separate simulation.
What would a pilot involve, and what would it cost?
We would start by understanding one workflow and assessing whether we can support it. Scope, setup responsibilities, timing and any price would be agreed before starting. Pricing and pilot availability are not set. An enquiry is a conversation, not a purchase or a reserved place.
Is the black box a physical device?
No. Agent Black Box is a software concept. The box and red button are a visual way to show the idea of keeping a human checkpoint around automated actions.
HELP SHAPE A FUTURE PILOT
Which action would
you want to approve?
Bring one workflow and the moment you want a person involved.
We would explore the fit, the connection and what success should look like.
No purchase commitment. No immediate product access.
Website preview: the enquiry form is a demonstration and sends nothing.