In this article
Nothing stops a group having several bots, and plenty do: one for moderation, one for the shop, one that posts the feed. Between them they can add up to something like a system.
They can also add up to four things that break separately, run by four people you have never met. Deciding how many bots a room should have is an operational judgement, not a technical one.
What you will be able to do
- check_circle Decide whether a second bot is worth it.
- check_circle Split by audience rather than by feature.
- check_circle See what several operators means in practice.
- check_circle Diagnose a failure when bots depend on each other.
From the members' side there is no system — only several accounts that answer when spoken to.
account_tree Bots do not talk to each other by watching
The intuition people arrive with is that adding two bots to a room lets them cooperate, the way two people in a meeting would. They cannot. Each one receives what is addressed to it, and one bot posting a message is not something another bot is sitting there noticing.
Anything that looks like coordination is happening behind them, in whatever the operator built: one service doing several jobs and speaking through several accounts, or separate services connected by their owner. The room is where the output appears, not where the joining-up happens.
Which reframes the question usefully. You are not assembling a system in your group; you are deciding how many separate parties get a presence in it, and how many places a failure can come from.
Four arrangements, from simplest to most fragile
Each one is right somewhere; the failure modes are what separate them.
smart_toy The default, and usually the answer
group A public bot and an admin one
construction Three bots from three providers
alt_route When one depends on another
Add a second bot to separate who talks to it, not to add a feature.
history Finding out which one did something
With more than one bot in a room, the practical skill is attribution. The group's recent actions log records what was removed, pinned, promoted or changed and by whom — including bots — and it is the only place that answers the question reliably.
It is worth reading it after any complaint rather than reasoning about which bot is configured for what. Configuration describes intent; the log describes what happened, and the gap between those two is where every long moderation argument lives.
settings Running more than one
- Start with one Most groups never need a second.
- Split by who addresses it Members, or admins.
- Keep the powers on the admin-facing one Not on the public one.
- Give them distinguishable names Similar ones cause wrong commands.
- Make every automated step announce itself Silence is untraceable.
- Read the actions log before arguing It names who did what.
This page adds more parties to a room. The curriculum step is how you find out what any of them did: what the log records, how long it keeps it, and what to look for when something has gone wrong quietly.
At a glance
- 1Second bot?
Split bots by who uses them, not by feature.
- 2More operators
Each bot is another party that can see the group.
- 3Chains fail quietly
Bots that depend on each other are hard to debug.
Updated
