An agent can return useful work while remaining outside the systems where a team coordinates.
People then relay requests, re-enter results and keep the agent aligned with decisions made elsewhere.
That arrangement can serve isolated requests. Ongoing work also needs a way to receive corrections and return results in the team’s normal flow.
Participation changes the work
An agent participating in a team needs to receive work, accept corrections during a task and return a result people can review. The interaction surface determines how directly the team can do those things.
An agent is a resource on the team
An agent needs a defined role, work suited to its capabilities and an operating record. XSI-AIMS describes governance responsibilities for that work, including human authority and the routing of tasks to appropriate resources.
Meet us where we work
Teams coordinate through Microsoft Teams and Slack, Azure DevOps and Jira, the wiki and the repo, as well as calls. Those surfaces carry assignments, decisions and corrections. An agent participating in the team needs a way to receive that context and return its work to the appropriate place.
So we started with the voice
People often redirect work in the middle of a conversation. A spoken correction can arrive before a task goes further in the wrong direction. Voice gives a person another way to reach the agent while the work is underway.
The voice preview supports a live spoken interaction in which a person can answer, interrupt and redirect the agent. Core inference and governance run within the customer’s environment; external connections have their own authorized data paths. The voice interaction remains subject to the existing authority chain and activity record.
A correction changes the next step
Select diagram to enlargePreview scope
Voice is an early surface offered by invitation and waitlist. Native participation across Teams, Slack, Azure DevOps, Jira, the wiki and other team tools is on the roadmap.
The preview applies the existing authority chain and activity record to the voice interaction. Broader integrations remain work in progress.
Present in the work
The goal is an agent that can follow a changing task alongside its human owner, receiving corrections while the work is underway.
Participation also needs a clear operating record, so people can see what was requested, what changed and what happened.
Voice support is available in preview by invitation and waitlist. The companion whitepaper, Meet Us Where We Work, develops the argument for agents participating in a team’s existing tools.
