{"slug": "how-we-cut-ten-alerting-agents-down-to-one", "title": "How we cut ten alerting agents down to one", "summary": "A team consolidated ten specialized AI alerting agents into one general agent plus scheduled jobs, after the ten agents' independent urgency rules left a single person sorting every alert. The new system routes routine findings to a daily briefing queue and reserves human interruptions for urgent deadlines, currently blocked work, same-day decisions and urgent client support requests, with repeat alerts on the same work item waiting six hours by default. The team's stated lesson is that noticing a finding and deciding to interrupt a person are separate jobs that should be assigned to separate parts of the system.", "body_md": "We had ten AI agents, and each one checked one part of the business. Most of them could also send an alert to a person on their own. Taken one at a time, the alerts were useful. Together, they left one person to sort through all of them. Giving each agent its own rule for what counts as urgent made that sorting harder.\n\nWe replaced them with one general agent and a set of scheduled jobs. The jobs still check their own parts of the business. Routine findings go into a queue for the daily briefing, and one set of written rules decides what is urgent enough to interrupt someone.\n\nThe lesson for anyone designing agents: noticing something and deciding to interrupt a person are two separate jobs. Give them to separate parts of the system.\n\n## Give one agent the decision about what is urgent\n\nOur general agent holds routine findings for the briefing. It interrupts a person only for urgent deadlines, work that is blocked now, decisions needed the same day and urgent client support requests.\n\nIf you are designing a similar system, ask which part of it can weigh a finding against everything else happening that day. A specialist job can notice that a renewal is coming up. Deciding whether that renewal is worth an interruption needs a view of all the other work competing for attention.\n\nWrite these rules before you add another way to send notifications. List the conditions that justify an interruption, and give routine findings a place to wait.\n\n## Check each finding again before the briefing\n\nOur briefing instructions tell the agent to look up each record again before it repeats a finding. They also tell it to drop meeting acceptances and out-of-office replies that have expired, and to group receipts together.\n\nSo the briefing is a summary of where things stand now, built from the records themselves. It is more useful than a list of messages in the order they arrived.\n\nWhen you design your own queue, decide what makes each kind of finding out of date, and make the briefing check for it. One good test: change the underlying record after a finding is queued and before the briefing runs. The briefing should report the current record, and drop the old text.\n\n## Link every alert to a work item\n\nOur system cannot send an alert to a phone unless the alert is attached to a work item. The alert links to that record, so the person who gets it goes straight to the work it is about.\n\nA repeat alert about the same work item waits six hours by default. The agent can override the wait when the situation has changed in a material way.\n\nSome urgent events follow fixed rules and do not wait for the general agent, including client requests to schedule a meeting and failed jobs. These alerts still attach to a work item in the same way.\n\nIf you run your own agents, settle these questions in writing: what record must exist before an alert goes out, how often an alert can repeat, and what kind of change allows an override. You can inspect and test these rules alongside the model's instructions.\n\n## List every way an agent can interrupt a person\n\nThe specialist jobs are still part of our system. The general agent gives them one place to send routine findings and one rule for what is urgent.\n\nIf your team runs several AI workflows, start by listing every path that can interrupt a person. For each one, record:\n\n- Who decides whether it is urgent.\n- What evidence supports the finding.\n- When that evidence must be checked again.\n- What makes the finding expire.\n- Which work record the alert opens.\n- What stops repeat alerts about the same work.\n\nThis list is a good starting point for a conversation about [AI implementation](https://kznconsulting.com/services/ai-implementation). It connects each agent's instructions to how people receive and act on what the agents produce.\n\nFor the same approach applied to deadlines, read [How to automate follow-up when deadlines slip](https://kznconsulting.com/writing/chasing-deadlines-that-slip). For everything the agent does today, and the rules it follows, see [How we run Kaizen on AI](https://kznconsulting.com/work/how-we-run-kaizen).", "url": "https://wpnews.pro/news/how-we-cut-ten-alerting-agents-down-to-one", "canonical_source": "https://kznconsulting.com/writing/cut-thirteen-alerting-agents-to-one", "published_at": "2026-09-08 00:00:00+00:00", "updated_at": "2026-09-24 04:00:42.959564+00:00", "lang": "en", "topics": ["ai-agents", "artificial-intelligence", "ai-tools"], "entities": ["Kaiz"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/how-we-cut-ten-alerting-agents-down-to-one", "markdown": "https://wpnews.pro/news/how-we-cut-ten-alerting-agents-down-to-one.md", "text": "https://wpnews.pro/news/how-we-cut-ten-alerting-agents-down-to-one.txt", "jsonld": "https://wpnews.pro/news/how-we-cut-ten-alerting-agents-down-to-one.jsonld"}}