Scope
This guide covers daily operation for AI Team Operations. Availability depends on your tenant package, role and configured providers.
Purpose
See specialised agents, runs, outputs and team-level activity.
Review active work, outputs, exceptions and follow-up.
Before you start
Correct tenant and project selected
Required source or provider is available
An accountable owner is identified
Test data can be separated from live activity
Procedure
- State the operating objective and the record, audience, campaign or project in scope.
- Review active work, outputs, exceptions and follow-up.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Run due agents for bounded recurring jobs.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Compare run completion, accepted output and operational outcomes.
Verify the result
Compare run completion, accepted output and operational outcomes. Confirm that the intended record, state, run or report is visible to another authorised operator and that its next owner is clear.
Completion checkpoint
The capability is in the intended state, evidence is current, exceptions are owned and the next action can be understood without a separate status message.
Controls and limitations
Keep tasks scoped, observable and reviewable. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.