E-signing shows as broken, and the offer letters wait for the fix.
Step 1 of 5: Calendar
Which tools are connected and healthy.
A broken tool connection is visible before an agent depends on it.
Tool execution. It runs Read-only. In the Agent Operating System, it runs every agent’s actions under your rules and carries long work to the finish.
Before a task starts, you can see which of its tools are ready.
A webinar needs three tools. The view shows which are healthy, so the broken one is found before the deck depends on it.
Step 1 of 3: The guest list
The guest list needs the sign-up tool, which shows as healthy, so it is pulled.
A broken tool stays in view until it is healthy again.
The view follows each tool connection through the week, so anyone can see which are healthy now and which one needs fixing.
Step 1 of 4: Monday
Monday: every connected tool shows as healthy.
A broken tool is spotted at the start of a task, not halfway through.
Because every tool’s state is visible, a broken one is seen before anything relies on it, rather than found halfway.
Step 1 of 3: The start
An agent starts arranging a client’s site visit, which needs four tools.
Runs model and tool calls under your rules.
Every model call and tool action runs once, after MS Duplex approves it, with credentials out of the model’s reach.
- A model call, approved first and run onceA model call runs once, after MS Duplex has approved it for that request.
- The same call, streamed as it is writtenAnswers appear as they are written, with the same rules applied.
- A tool action, exactly as approvedA tool action runs once, with exactly the arguments MS Duplex approved.
- Long tool runs, streamed and safe to cancelA long-running tool streams its progress and can be cancelled safely.
- Each model provider, with its own identityYour team connects each model provider with its own identity and credentials.
- Which model connections are healthyA failing model connection is spotted before it slows anyone down.
- Model connections, checked after every changeA model connection is checked before first use and after every change.
- Each tool, with its own permissions and riskEach tool is connected with its own identity, permissions and risk level.
- Which tools are connected and healthyA broken tool connection is visible before an agent depends on it.
- Tool connections, checked after every changeA tool connection is checked before first use and after every change.
See it on your own work.
From your own assistant to every agent your company runs, a pilot puts MS Duplex on your own work, with the measures agreed before it begins.