Skip to main content
Examples show how Duckie components fit together for larger systems. Each blueprint starts with the business process, then breaks the design into deployable functions such as intake, triage, human review, reporting, and feedback loops. These pages are meant to be read alongside the product docs. They explain what to build and link back to the reference pages for how each Duckie component works.

Designing Agent Systems

Learn how to combine workflows, autonomous agents, internal channel agents, Duckie Assistant agents, tools, and deployments.

Ticket Triage

See how to enrich support tickets with customer context, classify intent, apply tags, and route work.

Bug Intake to Engineering

See how to turn customer reports into engineering issues and route questions or fixes back to the customer.

Disputes and Chargebacks

See how to automate payment dispute operations with deterministic workflows and specialized agents.

​
How to Read Examples

Each blueprint is organized by function rather than by product feature:
Page typeWhat it answers
OverviewWhat business process does this automate?
System mapHow do channels, agents, workflows, tools, and humans connect?
Function pagesHow should each deployable part be designed?
Reporting and feedbackHow does the system improve after launch?
Rollout planHow should the system move from testing to live traffic?
Start with the system map, then open the function page for the part you want to build first.

Core Concepts

Review the main Duckie building blocks.

Deployments

Connect agents and workflows to channels, webhooks, and schedules.

Workflows

Build deterministic process logic.

Autonomous Agents

Use agents for judgment, research, and flexible tool use.