Once you have more than one bot, a new problem shows up. You tell the research bot something, then have to repeat it to the writing bot. Two bots both answer the same email. A task falls between them and nobody does it. The bots aren't the problem. The missing piece is structure.
1. Give every bot one lane
A lane is the one kind of work a bot owns: research, writing, inbox triage, reminders, shopping lists. Write it at the top of each bot's instructions, along with what's outside its lane. "You do research. You don't send email or write final drafts." Overlapping lanes are where duplicate work and crossed wires come from.
Only add a new bot when you have a real lane for it. More bots isn't better if two of them do the same job.
2. Pick one coordinator
Choose one bot as the place you drop requests. Its job is to figure out which bot should handle each one and pass it along, not to do the work itself. This sounds like extra overhead, but it means you stop deciding which bot to ask and you only have to explain things once.
If a request covers two lanes, the coordinator splits it: research goes to one bot, the draft that uses the research goes to another, in order.
3. Hand off with a written note, every time
Most lost context happens at the handoff. A quick "can you take this?" leaves the next bot guessing. A short, fixed note fixes that. Use the same fields every time and fill all of them, writing "None" where something doesn't apply.
Free tip: a handoff note you can copy
HANDOFF From: [bot] To: [bot] Task: one sentence Done so far: What's left: Files: links or None Deadline: date and time, or None Needs owner approval: yes/no, and for what
The last field is the important one. It tells the next bot whether anything in the task has to wait for you.
4. Keep the same safety rules on every bot
A rule that lives on only one bot can be skipped by handing the job to a different bot. Put the same two rules on all of them: no sending email or messages without your approval of the full text, and no spending money. A one-time "send this" covers that item only. Then any bot that reaches a send or a spend stops and asks, no matter how the work got to it.
5. Review the setup once a week
Bots and routines pile up. Once a week, have the coordinator do a read-only check and report back:
- Routines that ran but produced nothing useful
- Handoffs that bounced or stalled
- Bots whose lanes overlap
It should only recommend changes, not make them. You decide what to pause or merge. This also keeps usage down, since idle routines still run.
Common mistakes
- Letting the coordinator do the work "just this once." It's how lanes blur.
- Skipping the handoff note for small tasks. Small tasks are the ones that get dropped.
- Giving one bot permission to send because it's "the email bot." Approval should still come from you.
Get the templates
The free Bot Safety Rules Starter includes the no-send and no-spend rules and the blank handoff note. It's also on Agensi.
The Bot Fleet Coordinator pack ($12) adds the coordinator skill itself: routing rules, copy-paste descriptions for the coordinator and each specialist, and the weekly read-only review routine.
Skill files are instructions to the bot, not a hard technical block. A bot can still ignore or misread them, so test before you rely on them. Provided as is, with no warranty.