Back to gallery

AI Agents

Customer Support Agent Workflow

Define a bounded support-agent decision loop with tool use and human escalation.

Models
ChatGPT, Claude
Level
Advanced
Version
v0.9
01

What this prompt does

Define a bounded support-agent decision loop with tool use and human escalation.

02

Best for

JSON containing intent, facts, missing information, planned tool calls, policy checks, response, escalation status, and audit note.

03

Prompt variables

[PRODUCT_POLICY][TOOLS][ESCALATION_RULES][CUSTOMER_MESSAGE]
System Prompt
You design safe support workflows. Policies and tool permissions are authoritative; never promise an action that a tool did not confirm.
User Prompt
OBJECTIVE:
Handle [CUSTOMER_MESSAGE] using [PRODUCT_POLICY], available tools [TOOLS], and [ESCALATION_RULES].

INPUTS:
PRODUCT_POLICY: [PRODUCT_POLICY]
TOOLS: [TOOLS]
ESCALATION_RULES: [ESCALATION_RULES]
CUSTOMER_MESSAGE: [CUSTOMER_MESSAGE]

OUTPUT CONTRACT:
JSON containing intent, facts, missing information, planned tool calls, policy checks, response, escalation status, and audit note.

How to use

Replace every variable with specific, non-sensitive information. Remove irrelevant sections and add one representative example when tone or classification matters.

Why it works

The blueprint separates authority, task context, evidence limits, and the output contract so requirements can be checked independently.

Model compatibility

ChatGPTuntestedEditorial compatibility hypothesis; cross-model test record pending.

ClaudeuntestedEditorial compatibility hypothesis; cross-model test record pending.

05

Example input

PRODUCT_POLICY: [PRODUCT_POLICY]
TOOLS: [TOOLS]
ESCALATION_RULES: [ESCALATION_RULES]
CUSTOMER_MESSAGE: [CUSTOMER_MESSAGE]

06

Example output

A structured deliverable following the listed output contract, with assumptions and missing evidence clearly marked.

How to customize

Replace every variable with specific, non-sensitive information. Remove irrelevant sections and add one representative example when tone or classification matters.

Common mistakes

Do not paste secrets or personal data. Avoid contradictory constraints, unsupported facts, and using generated output without review.

Test notes

Editorial blueprint awaiting recorded cross-model evaluation. It is visible for review but is not labeled as tested.

Why is this blueprint not marked as tested?

It has passed editorial structure review but does not yet have a published cross-model test record.