> ## Documentation Index
> Fetch the complete documentation index at: https://docs.duckie.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Example Duckie patterns and architectures for real customer operations

Examples show how Duckie components fit together for larger systems and integration patterns. Use the short pattern pages for focused implementation ideas, and use the blueprints when you want a fuller business-process design.

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.

<CardGroup cols={2}>
  <Card title="Designing Agent Systems" icon="diagram-project" href="/examples/designing-agent-systems">
    Learn how to combine workflows, autonomous agents, internal channel agents, Duckie Assistant agents, tools, and deployments.
  </Card>

  <Card title="Duckie as an External Subagent" icon="plug" href="/examples/duckie-as-external-subagent">
    See how to call Duckie from your own orchestration agent and send structured results back.
  </Card>

  <Card title="Ticket Triage" icon="inbox" href="/examples/ticket-triage/overview">
    See how to enrich support tickets with customer context, classify intent, apply tags, and route work.
  </Card>

  <Card title="Bug Intake to Engineering" icon="code-branch" href="/examples/bug-intake-to-engineering/overview">
    See how to turn customer reports into engineering issues and route questions or fixes back to the customer.
  </Card>

  <Card title="WISMO Order Status" icon="truck" href="/examples/wismo-order-status/overview">
    See how to automate order-status support with proactive updates and specialist agents.
  </Card>

  <Card title="Disputes and Chargebacks" icon="credit-card" href="/examples/disputes-and-chargebacks/overview">
    See how to automate payment dispute operations with deterministic workflows and specialized agents.
  </Card>
</CardGroup>

## How to Read Examples

Use focused pattern pages when you need one integration shape. Use blueprints when you need a full operational design organized by function rather than by product feature:

| Page type                  | What it answers                                                |
| -------------------------- | -------------------------------------------------------------- |
| **Pattern pages**          | How should one integration or agent pattern work?              |
| **Overview**               | What business process does this automate?                      |
| **System map**             | How do channels, agents, workflows, tools, and humans connect? |
| **Function pages**         | How should each deployable part be designed?                   |
| **Reporting and feedback** | How does the system improve after launch?                      |
| **Rollout plan**           | How should the system move from testing to live traffic?       |

<Tip>
  Start with the system map, then open the function page for the part you want to build first.
</Tip>

## Related Docs

<CardGroup cols={2}>
  <Card title="Core Concepts" icon="book" href="/core-concepts">
    Review the main Duckie building blocks.
  </Card>

  <Card title="Deployments" icon="rocket" href="/deployments/overview">
    Connect agents and workflows to channels, webhooks, and schedules.
  </Card>

  <Card title="Workflows" icon="diagram-project" href="/workflows/overview">
    Build deterministic process logic.
  </Card>

  <Card title="Autonomous Agents" icon="wand-magic-sparkles" href="/agents/autonomous-agents">
    Use agents for judgment, research, and flexible tool use.
  </Card>
</CardGroup>