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
Recommended Components
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
Related Docs
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.