Build a support email workflow

This learning path starts with one synthetic email and grows it into a reviewable support draft. You will author the files yourself, then compare them with the runnable final example.

1. Set up the project.
2. Classify one email.
3. Extract the requested action.
4. Route to a branch.
5. Look up an account.
6. Try a bounded model tool loop.
7. Handle several requests.
8. Evaluate the workflow.
9. Connect it to your application.

The setting stays the same: a fictional subscription support team receives Please review the duplicate charge on invoice INV-7 for account A-100. The direct path classifies the email, extracts an account reference, looks up a synthetic account, and drafts a reply for an agent to review. It never sends email or changes an account.

The final example contains three workflows. support_email uses an authored direct MCP call. agent_reply shows a bounded model tool loop for the same read-only lookup; it is an alternative, not the next step in one invocation. support_multi prepares independent requests in a bounded collection. Offline scripted model responses prove wiring and validation. Live model quality requires separate evaluation.

Foliqant runs one bounded invocation in memory. A host owns incoming HTTP, identity checks, persistence, and sending a reviewed reply. See HTTP integration for that boundary.