Skip to content
Seif Essam

AI Agents

Complaint Agent

Tries to resolve, then hands off cleanly — and never escalates itself.

Manual
Escalation paths
1
Read the steps as a list
  1. trigger Delegated by orchestrator
  2. ai Complaint agent loop · GPT-5-mini
  3. integration get_order

    Track-aware variant — not constructed at all for lead-only businesses with no orders.

  4. action log_complaint

    Typed, including the delivered-but-not-received dispute.

  5. condition Resolved?
  6. output Report resolved
  7. output Report unresolved

    The ORCHESTRATOR decides on escalation — not this agent.

The problem

If every specialist can escalate to a human independently, “notify a human” becomes four slightly different code paths that drift apart.

How it works

Looks up the order, understands the complaint, logs it with a specific type — including the “marked delivered but never received” dispute — and reports back whether it resolved the issue.

The outcome

The complaint agent never escalates itself by design. It reports resolution status; the orchestrator, which owns the single consistently-gated escalation path, decides whether a human is needed in that same turn.