Skip to main content
A weekly customer report should show what support achieved and what still needs action. Give a scheduled agent the assignment to assemble current service evidence, identify unresolved risks, request the account team’s context, and prepare a reviewed customer update with an owned follow-up queue. This extends the support loop across incidents and requests. A healthy-looking summary does not close an unresolved ticket; the report should link its commitments to the work that will fulfil them.

​
Workflow dependencies

Configure the supported worker service connections before delegating these actions. Keep each report scoped to the correct customer. Native Teams approval routing is off; customer delivery can use an eligible Graph, Outlook, Gmail, or help-desk connection with the required worker account and scopes. Each external connector write requires an independent authorized manager to approve the exact request. Assign a person when the required delivery route is unavailable.

​
From scheduled review to customer follow-up

1

Configure the scheduled agent

Create the agent, its instructions and service connections, and a supported schedule trigger. Define the reporting period, customer scope, required evidence, review owner, and output. A desktop procedure remains a separate execution environment; saving one does not create a scheduled cloud worker.
2

Collect the current source evidence

Retrieve the authorized monitoring, ticket, backup, and security records through the available cloud tools. Preserve the source references and reporting period. Flag missing data instead of filling the gap with an assumption.
3

Reconcile outcomes and exceptions

Distinguish resolved incidents from open risks, accepted exceptions, and overdue commitments. Compare relevant prior results when they are available. Use eligible organization-visible Org Brain knowledge for reusable service guidance, while checking the customer-specific source records directly.
4

Request the account team's context

Create human tasks for material gaps: a recovery that is not verified, an unexplained monitoring gap, or a customer commitment with no owner. Incorporate the response in the report and carry unresolved questions forward explicitly.
5

Prepare and review the report

Produce the supported report output with an executive summary, service results, open issues, and proposed next actions. Route it to the account owner for the configured review before external delivery. If a customer requires a PDF or another format outside the worker’s available tools, assign that formatting step to an operator.
6

Deliver and retain the approved result

Send through an available, authorized connection or give the assigned person the approved report and recipient list. Record delivery and archive the result through the configured process. Do not assume a Teams post or customer email happened because the report was generated.
7

Create the next support work

Use supported ticketing actions or explicit human tasks to assign agreed follow-up. Each action needs an owner and a clear outcome. Review the run to improve the next reporting cycle without obscuring work that remains open.

​
What success looks like

  • The customer sees verified service results and understandable open issues.
  • The account owner reviews the material before it leaves the team.
  • Every new commitment becomes owned work, with the source evidence attached.
  • The run distinguishes a report prepared, a report delivered, and follow-up completed.

Digital workers

Configure the agent, schedule, connections, human decisions, and output.

Files and artifacts

Review and share the report using the appropriate workspace tools.