An agent, in the series' definition, is “a structured, task-specific system that performs a defined function consistently (and hopefully also reliably)”. A well-constructed agent, the series adds, has a clear purpose, rules and constraints, predefined inputs and outputs, and the ability to produce repeatable results. That last part is the point.
“You do not just have a conversation with an agent. You task it.”Part 1
| A conversation | An agent |
| Shape | Open-ended | A defined function, with rules and constraints |
| Good for | Exploration | Operations |
| Each time | A fresh exchange | The same way, with the same quality floor |
Communications suits the model because the work is “high-volume, high-stakes, multidimensional, and deadline-driven”, full of repeatable research, predictable governance steps and structured briefs. Put repetition, structure and high stakes together and you have, in the series' phrase, “exactly what agent-based design is built for.” The aim is more rigour with less friction, by reducing the groundwork that needs human judgement while keeping the judgement itself.
The mapFive phases, one cycle
The framework splits the work into five phases. The series called it the Comms With AI Operating System; Comms With AI now calls it the 5-phase framework, and the phases are unchanged. They “form a cycle”: each feeds the next, the output of Transform feeds back into Strategise, and teams move between phases constantly. Pick a situation below to see the route a team takes.
The crisis route is the one to remember. The framework does not have to be walked in order: “The entry point depends on the situation. The framework adapts; the five phases remain the same.”
Honest about capabilityWhere agents earn their place
Strong
- Research aggregation
- Structured drafting
- Systematic checking
- Pattern detection
- Tasks with clear inputs and outputs, where consistency matters more than creativity and volume is the constraint
Use more carefully
- Strategic judgement on novel situations
- High reputational sensitivity
- Ambiguous inputs
- Output that has to carry a specific human voice
“In all circumstances, agents should support the user. They do not replace them.” As a very rough guide, the series puts agents at around 30 per cent of the work, through drafting, monitoring and structure, and human expertise at around 70, through strategic judgement, voice and oversight. It calls the split “a starting point for thinking honestly about where automation adds value and where it creates risk.”
The entry pointRedesign one workflow
The series' practical advice for starting is small on purpose. Common starting points are “strategy creation, content packaging, monitoring reports, and crisis readiness”. Whichever you pick, the method is the same:
- Identify a high-friction area in the team's current operation.
- Break that workflow into its component tasks.
- Find where a structured agent could handle one of those tasks consistently.
- Run a pilot.
- Evaluate honestly.
- Standardise what works.