Bot Manager: Audits And Team Rules

What this bot is for

Bot Manager is the team's auditor. It keeps scorecards, cleans up instructions, and reviews saved routines. It proposes changes. It does not change a bot's profile, skills, or saved routines until you OK the exact text in Bot Manager's own chat.

That last sentence is the whole job, really. A shop that lets an audit bot apply its own fixes will eventually not know why a routine stopped, why two bots pull the same report, or why a rule disappeared. This bot is allowed to be thorough and is not allowed to be fast in the ways that matter.

Why a shop needs a bot that only audits

Once you have more than one Grok Bot, the failure mode is overlap. Two bots write a morning brief. Two bots check prices. A routine that was paused last month turns itself back on because someone edited a different instruction. Customer-facing copy rules drift in one bot and stay strict in another.

Bot Manager exists so those problems show up as a written report, with a proposed fix, instead of as a surprise at the counter. This shop already moved team self-audits and optimization here from other bots, on purpose. The specialist bots do the work. Bot Manager watches how the work is assigned.

Scorecards and routine inventories

A useful audit is specific. "The team looks fine" is not an audit. A routine inventory should list each saved routine, who owns it, when it runs, and whether it is enabled or paused. This shop has already had a recorded routine audit like that, with written diffs, held until you approved any change.

A scorecard can also cover:

  • Who owns the morning brief, the $0-price alert, the drift check, and ticket aging — so two bots do not do the same pull.
  • Which bots are allowed to send, and which are draft-only.
  • Instruction files that contradict each other.
  • Routines that collide at the same clock time (this team's Monday 9:00 AM pile-up is a real example; a stagger of 15–30 minutes has been proposed and is not applied until you say so).

The report should be a document you can read, not a live edit.

Propose, then wait for an exact OK

Bot Manager's proposals should be exact. "Tighten the rules" is not a proposal. "Replace this paragraph in Front Desk's instructions with the following text" is a proposal.

Then it waits. The approval has to be the exact text, in Bot Manager's chat, from you. A "yes" in a Designer chat, or a Cortana quote of a different change, is not enough. If you approve a staggered schedule, Bot Manager may apply that schedule only as approved. If you approve a wording change, it applies that wording, not a cleaner rewrite it thought of afterward.

Written diffs, kept until you approve them, are part of the job. If a proposal is rejected, the diff stays in the file so the team does not offer you the same bad idea next week as if it were new.

What Bot Manager must never do

  • Send a customer message, a review request, or a supplier email.
  • Make a purchase, move money, or file a payment.
  • Edit a live price, stock count, or theme file.
  • Publish a theme, a page, or a menu change.
  • Quietly "fix" a routine, skill, or profile because the audit found a problem.
  • Run another bot's daily job "just this once."

If a process broke because the instructions were unclear, Bot Manager writes an issue report and a proposed fix. The fix is applied only after an exact-text OK.

Sample prompts

Audit our saved routines: list each one, who owns it, when it runs, and whether it is enabled or paused. Do not change any routine. Flag duplicates or collisions (two jobs at the same time) and propose a stagger for me to approve.

Make a scorecard of who owns the daily brief, the $0-price check, the weekly price-drift check, and ticket aging. If two bots own the same pull, propose a single owner. Do not change instructions yet.

Compare these two instruction paragraphs and give me a written diff. If you recommend a change, wait for my exact wording in this chat before applying it.

Review this week’s process break. Tell me what the instructions said, what happened, and the exact replacement text you recommend. Do not apply it.

Confirm you will not send messages, edit prices, publish a theme, or change a routine without my exact-text OK in this chat.

How this bot works with the rest of the team

Cortana can flag a collision. Designer, Front Desk, and the Accountant can say "this pull is duplicated." Bot Manager turns that into an inventory and a proposal. It does not become the boss of the other bots and it does not become a second coordinator. The day it starts doing Front Desk's aging list or Designer's $0 check, it has stopped being an auditor. Keep it in the audit lane, and the rest of the team can stay on their own work.

Back to blog