Skip to main content
Use a scheduled deployment for recurring stakeholder reporting. The recommended agent type is a Duckie Assistant agent because the report should inspect Duckie runs, summarize behavior, and surface improvement items without requiring a custom cron job.

​
What It Does

The daily reporting agent:
  • Runs on a schedule, such as every weekday at 9 AM in the stakeholders’ timezone
  • Reads Duckie runs, classifications, and operational systems for the reporting window
  • Summarizes new cases, pending approvals, submitted cases, outcomes, deadline risks, and failures
  • Highlights follow-up work and owners
  • Posts the digest to a stakeholder channel
  • Links back to relevant runs, tickets, and cases
NeedDuckie component
Recurring runScheduler deployment
Reporting logicDuckie Assistant agent
Duckie run reviewDuckie Assistant MCP or Runs API
DestinationSlack app tools
Follow-up trackingIssue tracker or ticketing tools

​
Flow

​
Deployment Steps

1

Create the reporting agent

Create a Duckie Assistant agent that can inspect Duckie runs, summarize system behavior, and report improvement items.
2

Give it read tools

Enable read access to Duckie runs, analytics, ticketing, processor, and case systems needed for the report.
3

Connect the stakeholder channel

Use Slack app tools to post to a channel such as #payments-ops or #disputes-daily.
4

Create a Scheduler deployment

Choose Scheduler as the trigger and set a preset, plain-language schedule, or five-field cron expression.
5

Start in Testing mode

Review the scheduled output before switching the deployment to Live.

​
Report Contents

Include:
  • New cases opened
  • Cases accepted, countered, withdrawn, submitted, won, lost, or closed
  • Cases waiting on account response
  • Cases waiting on human approval
  • Cases at deadline risk
  • High-value or policy-sensitive cases
  • Tool failures and retries
  • Escalations sent and resolved
  • Recommended follow-up work
  • Links to runs, cases, tickets, and review threads

​
Example Digest Shape

Daily dispute operations summary

Window: Previous business day

Volume:
- New cases: 18
- Submitted responses: 7
- Accepted or closed: 3
- Waiting on account: 5
- Waiting on approval: 2

Risk:
- 3 cases due in the next 48 hours
- 1 high-value case needs policy review

Automation health:
- 2 tool retries
- 1 escalation resolved by reviewer

Follow-ups:
- Review missing evidence pattern for reason category X
- Confirm owner for overdue account response cases
Scheduled runs appear in Analyze > Runs with source Scheduler, which gives the team an audit trail for every posted report.

Scheduled Deployments

Run the report on a recurring schedule.

Duckie Assistant Agents

Build a reporting agent that can inspect Duckie runs.

Runs

Review scheduled report executions.

Slack

Post the report to a stakeholder channel.