KUSA
Book a free 30-minute call
Book a free 30-minute call

Capabilities · 05 of 05

Control: you decide what the system may do alone.

Approvals, hand-off to a person, limits, a log of every action, alerts only when you must act, a short daily brief and numbers you can trust. This is the part most AI builds leave out.

Book a free 30-minute callAll capabilities
control.spec7 parts
  • 01Approvals
  • 02Hand-off to a person
  • 03Limits and a stop switch
  • 04The action log
  • 05Alerts only when needed
  • 06The daily brief
  • 07Honest dashboards
Part 05 of a custom AI system

The problem

Most AI tools are built to act and hope. Nobody knows what they said last night, nothing stops them at the limit, and the dashboard counts everything as a success. An owner cannot trust a system they cannot see or stop.

The parts

What control can be made of.

A system uses the parts the work needs, not all of them. Each one is built on the tools you already use where it can be.

01

Approvals

Anything risky waits for a person to approve it in one tap: refunds, discounts, promises, a batch of messages.

  • A refund over a set amount
  • A discount outside the rules
  • A batch of emails before it goes out
  • An approval list
  • Email or Slack buttons
02

Hand-off to a person

The agent stops and passes the conversation to a person, with everything said so far, so nobody asks twice.

  • A complaint
  • A request for a person
  • Anything the brain does not cover
  • A ticket
  • A notification
  • A call transfer
03

Limits and a stop switch

Daily caps, caps per conversation and one switch that stops everything at once.

  • No more than a set number of replies a day
  • One reply per customer per day
  • Stop every send now
  • Settings that fail closed
04

The action log

Every action the system took, and every time it stopped for a person, in one log you can read.

  • “Why did it say that?” with an answer
  • Who approved what, and when
  • A record for audits
  • An append-only log
05

Alerts only when needed

The system tells a person only when that person must act. Everything else waits for the brief.

  • A stuck step
  • A customer asking for a person
  • A limit reached
  • Email
  • Messaging alerts
  • A needs-you and an fyi class
06

The daily brief

One short message each morning: what needs you today and what was handled quietly.

  • The owner’s first read of the day
  • Three decisions, not thirty notifications
  • What the system learned this week
  • An LLM over the system’s own log
  • Email
07

Honest dashboards

Shows only what can be measured. What cannot be measured is shown as missing, not as zero, and nothing is dressed up as a win.

  • A funnel you can trust
  • Counts of real work done
  • Gaps marked as gaps
  • First-party analytics
  • PostHog
  • A small dashboard

The tools named are common choices, not a requirement. We work with what you have.

In other businesses

What it can look like.

Three illustrations from different kinds of business, to show the idea.

Illustration

A car repair shop

The chat agent may book, quote from the price list and confirm. Any discount, any repair over a set amount and every complaint waits for the manager, who approves from the morning brief.

Illustration

A physiotherapy practice

The system may send one reminder per appointment and no more. When a patient asks a clinical question, the conversation goes to a therapist with the history attached.

Illustration

A recruitment agency

Every message the system sends to a candidate is in the log with the rule it followed. When a client asks why a candidate was contacted, the answer is one search away.

How it connects

Control wraps the other four. Every channel, agent and automation checks it before it acts, and every lesson it records goes back into the business brain.

Guardrails

  • Readers fail closed: if a limit or rule cannot be read, the system stops instead of guessing.
  • You set what is automatic, what is a proposal and what is never done, area by area.
  • The stop switch is yours and works at any hour.
  • The log cannot be edited after the fact.

The other four

A system is all five working together.

01ChannelsPhone, messaging apps, email, web chat and forms.Open channels
02AI agentsVoice, chat, email, research and task agents.Open AI agents
03Business brainWhat the business knows, remembers and learns.Open business brain
04AutomationsWorkflows, sequences, schedules, robots and documents.Open automations

Free 30-minute call

Tell us where the work gets stuck.

Bring the tools you use and the jobs your team repeats. You leave the call knowing which parts your system needs, roughly what it costs, and whether we are the right people to build it.

Pick a time on the calendar. It is a 30-minute call, and the invite lands on your calendar when you book. Prefer email? [email protected]

We reply by email within 24 hours.

AI systems call30 MIN
October 2026
MoTuWeThFrSaSu

Checking the calendar…

Questions

What people ask about control

Yes, and most systems should. Once you trust a kind of action, you move it to automatic. You can move it back at any time.

No. Alerts go out only when a person must act. Everything else is in the daily brief and the log.

You and whoever you choose. It shows what the system did, when and why, in plain language.

Because a number that cannot be measured is not a number. A gap shown as a gap keeps every other figure on the page worth trusting.