Skip to content

Module 01 · Lesson 01

What an AI agent is — and is not

Choose the smallest useful system for the work instead of calling every automation an agent.

Updated August 2026 · AI Agency Academy

What you will learn

Make a clear, safer operating decision.

You will be able to tell when a simple rule, a human-written response, an AI assistant, or an agent is the right fit. That decision keeps the build cheaper, easier to test, and easier to explain to a client.

Why this matters

Good agent work is useful before it is impressive.

A lead-routing rule does not need a model. A high-stakes refund should not be handed to an agent. The useful middle ground is work that needs judgement from bounded context, has a repeatable outcome, and still has a named human owner.

Field note 01

Make the relationship visible.

Core concepts

The language that keeps the work clear.

AutomationA predictable trigger and rule: when a form says enterprise, assign the enterprise queue.
Saved on this device.
AssistantA system that drafts, summarizes, or recommends while a person makes the decision.
AgentA system that can reason through a limited job, select from allowed actions, and report what it did.
OwnerThe person responsible for the result, corrections, and exceptions after the agent is live.
The practical method

Work through the decision in order.

  1. 01

    Name the job

    Write one sentence: ‘When this happens, help this person reach this outcome.’

  2. 02

    List the judgement

    Underline the parts where rules alone break down: unclear intent, incomplete facts, or several valid next steps.

  3. 03

    Separate actions

    Mark which actions are safe to automate, which need approval, and which must stay human.

  4. 04

    Choose the simplest design

    Use a rule where a rule works. Add an assistant or agent only where its judgement has a measurable purpose.

Worked example

A realistic, bounded implementation.

A home-services business wants faster replies to web enquiries. The first version does not need an ‘AI sales employee.’

A form rule stores location and service type. An assistant turns the customer’s free-text note into a short summary. An agent may ask one approved follow-up question when the request is unclear, then routes the record to the right dispatcher.

The dispatcher still owns urgent requests and pricing. The result is a useful hybrid workflow, not a vague automation promise.

Build it in practice

Use this copyable working template.

Adapt it to the client’s evidence, policy, people, and tools. Do not treat placeholders as approved instructions.

Job: [trigger] → help [user] achieve [outcome]. Judgement needed: [where rules fail]. Allowed actions: [safe actions]. Approval needed for: [actions]. Human owner: [name or role].
Spacebrain implementation

Put the operating system around the agent.

Use forms, CRM routing, automations, and task ownership for the deterministic parts first. Add AI only where it improves a clearly defined handoff or decision.

Practice

Before you move on

  • Choose one repeated workflow from your own business or a prospective client.
  • Classify every step as rule, assistant, agent, or human decision.
  • Remove any agent behaviour that has no clear reason to exist.
  • The job has one user and one intended outcome.
  • The agent is not being used where a rule is enough.
  • A human owner is named.
  • High-impact actions are not implied to be autonomous.

Put the learning to work

Build an AI service people can trust.

Create a free Spacebrain account and use the operating layer around your AI service.

Start free trial