One invoice, with Microsoft 365 or without it

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

If your office runs on Microsoft 365, keep it; the record renders into it. A card in the team's Teams channel. An assistant built in Copilot Studio can read the playbook and explain. It has no button to press; an agent signs only what your steward grants.

Without Microsoft

If you don't use Microsoft, you need none of it. A message in the team's Slack channel. Claude, or any assistant that can read it, sees the same playbook, and has no button to press 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

How it works, in four pictures · Try the sample inbox · Start