# AI Intake Automation: Design a Reliable Triage Workflow: worksheet

Prepared September 14, 2026. Adapt to your own process. Do not include secrets or private customer records.

## Working record

Follow a single request through the proposed process and fill in the sheet at each boundary. Preserve the distinction between customer-supplied facts, AI interpretation, and authorized action. If the team cannot explain how an uncertain or duplicate request is handled, resolve that gap before adding another channel. The sheet should describe the first bounded release, not every possible future capability.

| Field | Your working note |
|---|---|
| Channel and request identifier | Fill in for your business |
| Minimum collected fields | Fill in for your business |
| Source location and access | Fill in for your business |
| Validation and abuse checks | Fill in for your business |
| Allowed triage categories | Fill in for your business |
| Uncertainty and escalation route | Fill in for your business |
| Human reviewer and queue | Fill in for your business |
| Approved message types | Fill in for your business |
| Retry and reconciliation behavior | Fill in for your business |
| Useful handoff measure | Fill in for your business |

Use the notes to identify the next decision, not to create an appearance of completeness. Mark unknowns openly, assign an owner, and attach a safe evidence reference where appropriate. Do not put passwords, customer records, or private correspondence in a worksheet that will be shared widely.

Review the completed sheet with someone who actually performs the work. Ask them to walk through one ordinary example and one exception using only the recorded instructions. Update the unclear parts, then save a dated version. That small exercise turns a planning template into a practical operating artifact and gives future reviewers a clear starting point.