Your agents do not talk to each other
Several agents can do a team's work while each has a different account of what was agreed.
You own the business, and several AI agents now do jobs you once would have hired people to do. One handles the inbox, another works on orders, and another looks after the website. An agent here means AI software given a job and the means to carry it out.
There's no staff meeting to arrange and no office politics to work round. Nobody calls in sick or leaves for another job. Work can happen across the business without you having staff to manage.
That is useful. But the agents can still fail together, in ways a team of people would find strange. You may have told each agent what to do without giving them the same information. Work moves from one job to another while something you thought was settled never reaches the next agent.
The agreement doesn't reach the next job
An agent working from incomplete notes can miss an agreement that another agent already has. The situations below are hypothetical.
Illustrative: yesterday's session. Suppose yesterday you agreed with an agent to use a customer's trading name in replies. Today you start a separate session with the old account notes, which contain only the registered name. Yesterday's agreement hasn't been supplied. You remember settling the name; today's session has only the old notes to work from.
Illustrative: separate agents. The inbox agent agrees a revised dispatch date for an order. The ordering agent still has the original date and never receives the new date.
Illustrative: a guess passed along. Suppose an agent preparing a stock note has no information about whether an item is available. The agent writes that the item is in stock, without marking the statement as a guess. Another agent uses that note to answer a customer and repeats the claim as fact. The missing stock information has become a definite answer by the time the customer hears it.
I run several coding agents at once on my own builds, and I've seen missing information and confident guesses pass between jobs.
The way I see it, these aren't failures of people working together. Nobody is sulking, ignoring a colleague or withholding news. A quick word can resolve a disagreement between colleagues. Someone who remembers can pass the news on. None of that reaches the agents in these situations unless the missing detail is supplied to their jobs.
Current facts on a shared page
A shared page of current facts gives the agents something common to work from, provided each job actually receives the relevant facts.
The page holds what is true now: current dates, prices and the agreements that still apply this week. The words can be ordinary. A customer's trading name belongs beside the registered name. An order has its agreed dispatch date. You don't need to describe the business from the beginning whenever an agent starts a job.
The meeting you were glad to lose was where the rest of the team heard what had changed.
A short written page can serve that purpose without gathering anybody round a table. But the page has to be part of the work. If the ordering agent is still using an older copy, a revised date on your screen does nothing for the order. Each agent needs the current page when its job begins.
When an agreement changes, you still have to put the new agreement on the page. If work is already under way, the affected agent needs the new information too. Waiting for its next job leaves the present job using the old facts.
Unknown details can stay plainly unknown on the page. If availability hasn't been established, an empty space or a vague stock note leaves the next job without that fact. Writing that availability is unknown tells the next agent that nobody has established whether the item is in stock.
Smaller jobs that you keep connected
Shorter jobs mean fewer actions depend on the same set of supplied facts. That matters when the business keeps changing while work is under way.
A long assignment to deal with customer correspondence could cover exchanges made before and after a new agreement. A shorter batch has a nearer end. The following batch can begin with the current facts supplied again. The point is to leave less work depending on what was said at the start of a single session.
Small jobs still connect to other jobs. A reply about an order may alter what the ordering work needs to know. Sending the reply doesn't tell the ordering agent what changed.
You join the pieces by making sure an agreement reaches every job that depends on it. The inbox and orders may be separate tasks to the agents. To you, they concern the same customer. You know why a message in one place matters to work happening somewhere else.
That part remains yours even when neither agent needs help with its individual task. Someone has to see the work as a whole and carry the relevant facts across.
Before the next agent starts
Your next agent will need facts about work that was already happening before you gave it a job.
It's easy to picture the recurring task you want the new agent to do. You know where the task fits because you've been running the business all week. The new instructions may describe the task perfectly while leaving out an agreement you have already made elsewhere.
The new agent needs the facts you already know. Something another agent was told earlier may be essential to this new job, even though you no longer think of it as news.
Before switching on the next agent, ask what it will not know.
Barry