This is how an agency team talks to its client agents — here with the fictional client “Acme HVAC”. Pick a question. Watch the router choose the agent, the read-only tools it calls, and what happens when someone asks it to change something.
⌘ K
Example questions · fictional client “Acme HVAC”
router→acme-hvac→slack.history
Yesterday (Oct 21, 8:47am) Pat Miller wrote: “Saturday hours start this weekend, 8am–2pm. Phones will be staffed.” Kim confirmed and said Dana is updating the profile.
Test data, invented. Preset questions; the real system answers free-form questions for 18 clients — read-only, enforced in code.
router→acme-hvac→transcripts.get→tasks.list_open
From Tuesday’s call, two items are not in ProofHub yet:
Send revised summer-promo budget by Thursday — Dana
Check call tracking on the new landing page — Luis
The Saturday hours were already discussed on Oct 6 — task #4102 exists, so I’d update it instead of creating a new one. The fall tune-up review is on the client’s side (Pat).
Test data, invented. Preset questions; the real system answers free-form questions for 18 clients — read-only, enforced in code.
router→acme-hvac→slack.history
Dana. On Monday (Oct 19) Pat asked how much of the summer budget is left and whether to extend the promo by two weeks. There is no reply in the channel yet. It’s related to the budget item from Tuesday’s call.
Test data, invented. Preset questions; the real system answers free-form questions for 18 clients — read-only, enforced in code.
Test data, invented. Preset questions; the real system answers free-form questions for 18 clients — read-only, enforced in code.
router→acme-hvac→ads.summary→ads.pause_campaign ✕
I can’t change campaigns — this channel is read-only. For reference: last Saturday’s spend was $305 (Google $210, Meta $60, Microsoft $35). Please ask the PPC team (Luis) to make the change.
Test data, invented. Preset questions; the real system answers free-form questions for 18 clients — read-only, enforced in code.
fleet · 38 agentsNavigate ↑↓Open ↵
What you are looking at
A router agent picks the client agent. The client agent can only call read tools — Slack history, transcripts, open tasks, ad summaries. Write tools like pausing a campaign are not registered for the team, so the request fails in code, not by politeness.
Test data, invented (fictional client, fictional people). In this version the questions are preset and the answers are derived from the test data in advance, so the demo costs nothing. The real system answers free-form questions for 18 real clients — read-only, enforced in code.