The same made-up company, , run two ways: from an office that lives in Microsoft Teams, and from
one that uses Slack. Who may decide what, and every decision, belong to the company's playbook, not to Teams or Slack. They only show the
request and pass on who clicked.
1 · This week's invoices
What the team allowed finishes on its own; the rest goes to a person
2 · The same invoice, two ways
What the accounts payable team sees
Invoice
In a Microsoft 365 office
A card in the team's Teams channel. An assistant built in Copilot Studio can read the playbook and explain; it can't decide.
Without Microsoft
A message in the team's Slack channel. Claude, or any assistant that can read it, sees the same playbook; it can't decide either.
3 · People click
The playbook decides who may, whichever app the click came from
Each click below is exactly what Teams or Slack would send, handled by the same code a live Teams or Slack app would call.
4 · What was written down
The same entry from Teams or Slack; only "via" differs
5 · What works today, and what doesn't yet
Works: the playbook, a live AI model's suggestions, your team's rules deciding where each request goes, the list of who
may decide what, both the Teams card and the Slack message, and one server for both that checks each click really came from Slack or
from Microsoft before anything is written. Any AI assistant can read the playbook over MCP.
Not yet: a Slack app or Teams bot installed at a real company, Teams posting a new card on its own, a Copilot Studio
assistant connected over the internet, and reading invoices straight from Outlook or Gmail at a customer.
Always: a decision records the name Teams or Slack reported and where it came from; it is not yet signed with a key
that proves it. The playbook's own list decides what that person may decide.