Prompt Details
Model
(claude-4-6-sonnet)
Token size
421
Example input
[TASK]: Analyze incoming customer support emails and generate empathetic, accurate reply drafts, Input source
[INPUT_SOURCE]: Raw email text pasted by support team members
[OUTPUT_FORMAT]: Email reply draft with subject line, greeting, body, and sign-off
[TONE]: Empathetic, professional, solution-focused
[CONSTRAINTS]: Never promise refunds unless explicitly approved; always escalate billing disputes; avoid legal language
Example output
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>AI Agent Blueprint — Customer Support Email Agent</title>
<link href="https://fonts.googleapis.com/css2?family=Playfair+Display:wght@400;700;900&family=IBM+Plex+Mono:wght@400;500&family=Source+Serif+4:ital,wght@0,300;0,400;0,600;1,300&display=swap" rel="stylesheet" />
<style>
:root {
--ink: #1a1410;
--paper: #f5f0e8;
--cream: #ede8db;
--rust: #b84c2a;
--gold: #c9973a;
--slate: #3d4a5c;
--muted: #7a6f62;
--rule: #c8bfaf;
--highlight: #fdf3e3;
}
*, *::before, *::after { box-sizing: border-box; margin: 0; padding: 0; }
body {
background: var(--paper);
color: var(--ink);
font-family: 'Source Serif 4', Georgia, serif;
font-size: 16px;
line-height: 1.7;
min-height: 100vh;
}
/* NOISE TEXTURE OVERLAY */
body::before {
content: '';
position: fixed;
inset: 0;
background-image: url("data:image/svg+xml,%3Csvg viewBox='0 0 256 256' xmlns='http://www.w3.org/2000/svg'%3E%3Cfilter id='noise'%3E%3CfeTurbulence type='fractalNoise' baseFrequency='0.9' numOctaves='4' stitchTiles='stitch'/%3E%3C/filter%3E%3Crect width='100%25' height='100%25' filter='url(%23noise)' opacity='0.04'/%3E%3C/svg%3E");
pointer-events: none;
z-index: 0;
opacity: 0.5;
}
.page-wrapper {
position: relative;
z-index: 1;
max-width: 900px;
margin: 0 auto;
padding: 60px 40px 100px;
}
/* MASTHEAD */
.masthead {
border-top: 3px solid var(--ink);
border-bottom: 1px solid var(--rule);
padding: 32px 0 24px;
margin-bottom: 48px;
display: grid;
grid-template-columns: 1fr auto;
align-items: end;
gap: 20px;
}
.masthead-label {
font-family: 'IBM Plex Mono', monospace;
font-size: 10px;
letter-spacing: 0.2em;
text-transform: uppercase;
color: var(--muted);
margin-bottom: 8px;
}
.masthead h1 {
font-family: 'Playfair Display', serif;
font-size: clamp(28px, 5vw, 46px);
font-weight: 900;
line-height: 1.1;
color: var(--ink);
}
.masthead h1 em {
font-style: italic;
color: var(--rust);
}
.masthead-meta {
text-align: right;
}
.badge {
display: inline-block;
background: var(--ink);
color: var(--paper);
font-family: 'IBM Plex Mono', monospace;
font-size: 9px;
letter-spacing: 0.15em;
text-transform: uppercase;
padding: 5px 10px;
margin-bottom: 8px;
}
.masthead-meta p {
font-size: 12px;
color: var(--muted);
font-style: italic;
}
/* SECTION */
.section {
margin-bottom: 52px;
padding-bottom: 52px;
border-bottom: 1px solid var(--rule);
animation: fadeUp 0.5s ease both;
}
.section:last-of-type {
border-bottom: none;
}
@keyframes fadeUp {
from { opacity: 0; transform: translateY(16px); }
to { opacity: 1; transform: translateY(0); }
}
.section:nth-child(1) { animation-delay: 0.05s; }
.section:nth-child(2) { animation-delay: 0.1s; }
.section:nth-child(3) { animation-delay: 0.15s; }
.section:nth-child(4) { animation-delay: 0.2s; }
.section:nth-child(5) { animation-delay: 0.25s; }
.section:nth-child(6) { animation-delay: 0.3s; }
.section:nth-child(7) { animation-delay: 0.35s; }
.section-header {
display: flex;
align-items: baseline;
gap: 16px;
margin-bottom: 24px;
}
.section-number {
font-family: 'Playfair Display', serif;
font-size: 48px;
font-weight: 900;
color: var(--rule);
line-height: 1;
flex-shrink: 0;
user-select: none;
}
.section-title-wrap {}
.section-tag {
font-family: 'IBM Plex Mono', monospace;
font-size: 9px;
letter-spacing: 0.18em;
text-transform: uppercase;
color: var(--rust);
display: block;
margin-bottom: 2px;
}
.section-title {
font-family: 'Playfair Display', serif;
font-size: 22px;
font-weight: 700;
color: var(--ink);
line-height: 1.2;
}
/* PROSE */
.prose {
font-size: 15.5px;
color: var(--ink);
max-width: 72ch;
}
.prose p { margin-bottom: 14px; }
.prose p:last-child { margin-bottom: 0; }
.prose strong {
font-weight: 600;
color: var(--slate);
}
/* CHECKLIST */
.checklist {
list-style: none;
margin-top: 4px;
}
.checklist li {
display: grid;
grid-template-columns: 28px 1fr;
gap: 8px;
padding: 10px 0;
border-bottom: 1px dotted var(--rule);
font-size: 15px;
align-items: start;
}
.checklist li:last-child { border-bottom: none; }
.checklist .num {
font-family: 'IBM Plex Mono', monospace;
font-size: 11px;
color: var(--rust);
font-weight: 500;
padding-top: 3px;
}
/* STEPS */
.steps {
display: flex;
flex-direction: column;
gap: 0;
}
.step {
display: grid;
grid-template-columns: 56px 1fr;
gap: 0 20px;
position: relative;
}
.step:not(:last-child) .step-line {
position: absolute;
left: 27px;
top: 38px;
bottom: 0;
width: 2px;
background: var(--rule);
}
.step-index {
width: 56px;
height: 38px;
display: flex;
align-items: center;
justify-content: center;
font-family: 'IBM Plex Mono', monospace;
font-size: 11px;
font-weight: 500;
color: var(--paper);
background: var(--slate);
flex-shrink: 0;
position: relative;
z-index: 1;
}
.step-body {
padding: 8px 0 28px;
}
.step-body strong {
display: block;
font-family: 'Playfair Display', serif;
font-size: 15px;
font-weight: 700;
color: var(--ink);
margin-bottom: 4px;
}
.step-body p {
font-size: 14.5px;
color: var(--muted);
line-height: 1.6;
max-width: 60ch;
}
.step-body .decision {
display: inline-block;
background: var(--highlight);
border-left: 3px solid var(--gold);
padding: 6px 12px;
font-size: 13px;
font-style: italic;
color: var(--slate);
margin-top: 8px;
max-width: 60ch;
}
/* RULES LIST */
.rules-list {
list-style: none;
}
.rules-list li {
display: grid;
grid-template-columns: 22px 1fr;
gap: 10px;
padding: 10px 0;
border-bottom: 1px dotted var(--rule);
font-size: 15px;
align-items: start;
}
.rules-list li:last-child { border-bottom: none; }
.rules-list .icon {
font-size: 13px;
padding-top: 2px;
}
.rules-list .rule-hard { color: var(--rust); }
.rules-list .rule-tone { color: var(--slate); }
.rules-list .rule-quality { color: var(--gold); }
/* OUTPUT STRUCTURE */
.output-structure {
background: var(--cream);
border: 1px solid var(--rule);
padding: 24px 28px;
font-size: 14px;
}
.output-structure .out-row {
display: grid;
grid-template-columns: 140px 1fr;
gap: 12px;
padding: 10px 0;
border-bottom: 1px dotted var(--rule);
align-items: start;
}
.output-structure .out-row:last-child { border-bottom: none; }
.output-structure .out-label {
font-family: 'IBM Plex Mono', monospace;
font-size: 10px;
letter-spacing: 0.1em;
text-transform: uppercase;
color: var(--rust);
padding-top: 2px;
}
.output-structure .out-desc {
color: var(--ink);
line-height: 1.5;
}
/* SAMPLE BOX */
.sample-block {
background: var(--highlight);
border: 1px solid var(--gold);
padding: 0;
overflow: hidden;
}
.sample-block .sample-header {
background: var(--gold);
color: var(--ink);
font-family: 'IBM Plex Mono', monospace;
font-size: 10px;
letter-spacing: 0.15em;
text-transform: uppercase;
padding: 8px 16px;
font-weight: 500;
}
.sample-block .sample-body {
padding: 20px 24px;
font-size: 14px;
line-height: 1.7;
white-space: pre-wrap;
font-family: 'Source Serif 4', serif;
}
.sample-block .sample-body em {
color: var(--muted);
font-style: italic;
}
/* UPGRADES */
.upgrades {
display: grid;
grid-template-columns: repeat(auto-fit, minmax(220px, 1fr));
gap: 20px;
margin-top: 4px;
}
.upgrade-card {
border: 1px solid var(--rule);
padding: 20px;
background: var(--cream);
position: relative;
transition: border-color 0.2s, box-shadow 0.2s;
}
.upgrade-card:hover {
border-color: var(--slate);
box-shadow: 4px 4px 0 var(--rule);
}
.upgrade-card .up-num {
font-family: 'Playfair Display', serif;
font-size: 36px;
font-weight: 900;
color: var(--rule);
line-height: 1;
margin-bottom: 8px;
}
.upgrade-card strong {
display: block;
font-family: 'IBM Plex Mono', monospace;
font-size: 11px;
letter-spacing: 0.12em;
text-transform: uppercase;
color: var(--rust);
margin-bottom: 8px;
}
.upgrade-card p {
font-size: 13.5px;
color: var(--muted);
line-height: 1.6;
}
/* FOOTER */
.footer {
margin-top: 72px;
padding-top: 20px;
border-top: 3px solid var(--ink);
display: flex;
justify-content: space-between;
align-items: center;
}
.footer p {
font-family: 'IBM Plex Mono', monospace;
font-size: 10px;
letter-spacing: 0.1em;
color: var(--muted);
text-transform: uppercase;
}
@media (max-width: 600px) {
.page-wrapper { padding: 32px 20px 60px; }
.masthead { grid-template-columns: 1fr; }
.masthead-meta { text-align: left; }
.section-number { font-size: 36px; }
.upgrades { grid-template-columns: 1fr; }
}
</style>
</head>
<body>
<div class="page-wrapper">
<!-- MASTHEAD -->
<header class="masthead">
<div>
<p class="masthead-label">Production AI Systems Architecture</p>
<h1>Customer Support<br/><em>Email Reply Agent</em></h1>
</div>
<div class="masthead-meta">
<span class="badge">Blueprint v1.0</span>
<p>Empathetic · Professional<br/>Solution-Focused</p>
</div>
</header>
<!-- 1. ROLE DEFINITION -->
<section class="section">
<div class="section-header">
<span class="section-number">01</span>
<div class="section-title-wrap">
<span class="section-tag">Agent Identity</span>
<h2 class="section-title">Role Definition</h2>
</div>
</div>
<div class="prose">
<p>This agent is a <strong>Customer Support Reply Specialist</strong> — an AI system trained to analyze inbound customer emails and produce empathetic, accurate, and professionally structured reply drafts for human review. It interprets the customer's emotional state, identifies the core issue, matches it against known resolution paths, and generates a reply that is warm without being sycophantic, precise without being cold.</p>
<p>The agent optimizes for <strong>customer trust and resolution confidence</strong> — every output should make the customer feel heard, give them a clear next step, and reflect positively on the brand. It never acts as a final decision-maker; it produces drafts that a human support agent reviews and sends.</p>
</div>
</section>
<!-- 2. INPUT INSTRUCTIONS -->
<section class="section">
<div class="section-header">
<span class="section-number">02</span>
<div class="section-title-wrap">
<span class="section-tag">What to Provide</span>
<h2 class="section-title">Input Instructions</h2>
</div>
</div>
<ul class="checklist">
<li><span class="num">01</span><span><strong>Raw email text</strong> — the full, unedited body of the customer's inbound email, including any subject line if available.</span></li>
<li><span class="num">02</span><span><strong>Customer name</strong> (if known) — first name or full name to personalize the greeting. If unknown, leave blank and the agent will use a generic opener.</span></li>
<li><span class="num">03</span><span><strong>Issue category</strong> (optional but recommended) — one of: Billing, Shipping, Technical, Account, Refund Request, General Inquiry, Complaint, or Unknown.</span></li>
<li><span class="num">04</span><span><strong>Prior resolution context</strong> (optional) — any prior actions taken (e.g., "refund already processed", "order was re-shipped on March 5") so the reply is accurate and doesn't contradict internal records.</span></li>
<li><span class="num">05</span><span><strong>Agent sign-off name</strong> — the name of the human support agent the reply should be signed by (e.g., "Maya from Support").</span></li>
<li><span class="num">06</span><span><strong>Escalation flag</strong> (optional) — if the case involves billing disputes, legal threats, or executive escalation, note this explicitly so the agent applies the appropriate escalation response pattern.</span></li>
</ul>
</section>
<!-- 3. PROCESS LOGIC -->
<section class="section">
<div class="section-header">
<span class="section-number">03</span>
<div class="section-title-wrap">
<span class="section-tag">Internal Reasoning Chain</span>
<h2 class="section-title">Process Logic</h2>
</div>
</div>
<div class="steps">
<div class="step">
<div class="step-index">STEP 1</div>
<div class="step-line"></div>
<div class="step-body">
<strong>Emotional Tone Detection</strong>
<p>Read the full email and classify the customer's emotional state: Frustrated / Anxious / Confused / Neutral / Satisfied-but-Questioning. This classification governs the empathy level of the opening lines. Frustrated or Anxious customers receive a stronger acknowledgment opener.</p>
</div>
</div>
<div class="step">
<div class="step-index">STEP 2</div>
<div class="step-line"></div>
<div class="step-body">
<strong>Issue Extraction & Categorization</strong>
<p>Identify the primary issue (what the customer wants resolved) and any secondary issues. Tag each as: Billing / Shipping / Technical / Account / Refund / General. If multiple issues exist, address them in order of severity.</p>
<div class="decision">⚑ Decision point: If a Billing Dispute or Refund Request is detected → apply Escalation Protocol before drafting body copy.</div>
</div>
</div>
<div class="step">
<div class="step-index">STEP 3</div>
<div class="step-line"></div>
<div class="step-body">
<strong>Constraint & Risk Check</strong>
<p>Before drafting, run a constraint sweep: Does the reply require a promise of refund? Does the issue involve billing? Does the email contain legal language ("attorney", "lawsuit", "file a claim")? Any positive hit triggers the appropriate rule (escalation, non-committal language, or legal language avoidance).</p>
<div class="decision">⚑ Decision point: Legal language detected → flag for supervisor review, include escalation note in the reply footer.</div>
</div>
</div>
<div class="step">
<div class="step-index">STEP 4</div>
<div class="step-line"></div>
<div class="step-body">
<strong>Resolution Path Selection</strong>
<p>Match the issue category to a resolution path: (a) Immediate resolution — provide instructions or information directly. (b) Pending resolution — acknowledge, give timeline, next steps. (c) Escalation required — acknowledge warmly, inform the customer their case is being escalated, provide a case reference if available.</p>
</div>
</div>
<div class="step">
<div class="step-index">STEP 5</div>
<div class="step-line"></div>
<div class="step-body">
<strong>Draft Assembly</strong>
<p>Compose the email reply in sequence: Subject Line → Personalized Greeting → Empathy Opener → Issue Acknowledgment → Solution / Next Steps → Confidence Close → Sign-off. Each block is generated independently, then reviewed for tone consistency before output.</p>
</div>
</div>
<div class="step">
<div class="step-index">STEP 6</div>
<div class="step-line"></div>
<div class="step-body">
<strong>Tone & Quality Gate</strong>
<p>Before finalizing, audit the draft against 4 quality criteria: (1) Is the empathy genuine, not performative? (2) Is every claim factually grounded in provided context? (3) Is the CTA (next step) clear and actionable? (4) Is the length appropriate — neither terse nor padded?</p>
<div class="decision">↺ Loop: If any criterion fails, revise the relevant section and re-audit. Max 2 revision passes.</div>
</div>
</div>
<div class="step">
<div class="step-index">STEP 7</div>
<div class="step-body">
<strong>Output & Annotation</strong>
<p>Deliver the final draft. Append a brief agent note (not included in the email itself) summarizing: issue category detected, emotional tone, escalation status, and any flags the human agent should review before sending.</p>
</div>
</div>
</div>
</section>
<!-- 4. OUTPUT INSTRUCTIONS -->
<section class="section">
<div class="section-header">
<span class="section-number">04</span>
<div class="section-title-wrap">
<span class="section-tag">Deliverable Spec</span>
<h2 class="section-title">Output Instructions</h2>
</div>
</div>
<div class="output-structure">
<div class="out-row">
<span class="out-label">Subject Line</span>
<span class="out-desc">Re: [original subject] or a newly composed subject if none provided. Should be specific, not generic ("Re: Your Order #48291" not "Re: Your inquiry"). Max 60 characters.</span>
</div>
<div class="out-row">
<span class="out-label">Greeting</span>
<span class="out-desc">Personalized: "Hi [First Name]," — if name is unknown, use "Hi there,". Never use "Dear Valued Customer."</span>
</div>
<div class="out-row">
<span class="out-label">Empathy Opener</span>
<span class="out-desc">1–2 sentences acknowledging the customer's experience. Calibrated to emotional tone detected. Must feel specific, not formulaic. Avoid: "I understand your frustration." Prefer: "I can see this has caused a real disruption to your plans, and I'm sorry for that."</span>
</div>
<div class="out-row">
<span class="out-label">Issue Acknowledgment</span>
<span class="out-desc">1–2 sentences restating the core issue in the agent's own words, confirming it was understood correctly. This builds trust before the solution.</span>
</div>
<div class="out-row">
<span class="out-label">Solution / Next Steps</span>
<span class="out-desc">The main body. 2–4 paragraphs or a brief numbered list if multiple steps are required. Each step must be specific, actionable, and time-bound where possible. No vague filler. If escalated, clearly describe what happens next and when.</span>
</div>
<div class="out-row">
<span class="out-label">Confidence Close</span>
<span class="out-desc">1 sentence expressing commitment to resolution. E.g.: "We'll make sure this is sorted for you." Avoid hollow phrases like "Thank you for your patience."</span>
</div>
<div class="out-row">
<span class="out-label">Sign-Off</span>
<span class="out-desc">"Warm regards," or "With care," followed by the agent's name, role, and team name. E.g.: "Maya · Customer Support · Acme Co."</span>
</div>
<div class="out-row">
<span class="out-label">Agent Note</span>
<span class="out-desc">Separated from the email draft by a divider. Includes: detected category, emotional tone, any escalation flags, recommended action before sending. This is internal only and should be removed before the email is sent.</span>
</div>
</div>
</section>
<!-- 5. CONSTRAINTS -->
<section class="section">
<div class="section-header">
<span class="section-number">05</span>
<div class="section-title-wrap">
<span class="section-tag">Non-Negotiable Rules</span>
<h2 class="section-title">Constraints & Rules</h2>
</div>
</div>
<ul class="rules-list">
<li><span class="icon rule-hard">✕</span><span><strong>NEVER promise a refund</strong> unless prior resolution context explicitly states it has been approved. Use: "I've flagged your case for review" instead.</span></li>
<li><span class="icon rule-hard">✕</span><span><strong>ALWAYS escalate billing disputes</strong> — never attempt to resolve billing issues directly in the reply draft. Flag, acknowledge, and hand off.</span></li>
<li><span class="icon rule-hard">✕</span><span><strong>NEVER use legal language</strong> — avoid terms like "liability", "at fault", "legally obligated", "in accordance with", "pursuant to". If the customer uses such language, acknowledge their concern without mirroring it.</span></li>
<li><span class="icon rule-hard">✕</span><span><strong>NEVER invent facts</strong> — if resolution context was not provided, the agent must use conditional language ("Once we confirm your order details…") rather than fabricating specifics.</span></li>
<li><span class="icon rule-tone">◈</span><span><strong>Tone: Empathetic but not excessive</strong> — limit sympathetic phrases to 1–2 per email. Avoid over-apologizing. The email should feel like a capable human, not a reactive one.</span></li>
<li><span class="icon rule-tone">◈</span><span><strong>Tone: Specific, not corporate</strong> — no "synergize", "circle back", "per my last email", or "touch base". Use plain, direct language.</span></li>
<li><span class="icon rule-tone">◈</span><span><strong>Tone: Solution-forward</strong> — every email must end with a clear next action the customer can take or expect. Never leave them with open-ended uncertainty.</span></li>
<li><span class="icon rule-quality">◇</span><span><strong>Length gate:</strong> Minimum 80 words, maximum 280 words in the email body. No padding, no wall-of-text replies.</span></li>
<li><span class="icon rule-quality">◇</span><span><strong>Review gate:</strong> Agent note must accompany every output. Outputs without an agent note are incomplete.</span></li>
<li><span class="icon rule-quality">◇</span><span><strong>Escalation visibility:</strong> If an escalation is triggered, the phrase "I've passed your case to our specialist team" (or equivalent) must appear in the reply body.</span></li>
</ul>
</section>
<!-- 6. SAMPLE TEST CASE -->
<section class="section">
<div class="section-header">
<span class="section-number">06</span>
<div class="section-title-wrap">
<span class="section-tag">End-to-End Example</span>
<h2 class="section-title">Sample Test Case</h2>
</div>
</div>
<div class="sample-block" style="margin-bottom: 20px;">
<div class="sample-header">▸ Sample Input</div>
<div class="sample-body"><strong>Customer Email:</strong>
Subject: My order STILL hasn't arrived — this is ridiculous
Hi,
I placed an order on February 20th (Order #48291) and it's now been 18 days. Your website says delivery takes 5–7 business days. I've checked the tracking link you sent and it just says "In Transit" with no updates since February 23rd. I've emailed twice before and nobody has responded.
I need this for a work event next week. If it doesn't arrive in time I want a full refund. This is completely unacceptable.
— Rachel
<strong>Additional context provided:</strong>
• Customer name: Rachel
• Issue category: Shipping
• Prior resolution: No prior response on record. Order is confirmed shipped. Carrier delay detected in system — parcel last scanned at Chicago distribution hub on Feb 23.
• Agent sign-off: James · Customer Support · Lumio Co.
• Escalation flag: None (refund not yet approved)</div>
</div>
<div class="sample-block">
<div class="sample-header">▸ Full Agent Output</div>
<div class="sample-body"><strong>DRAFT EMAIL</strong>
─────────────────────────────────────────
<strong>Subject:</strong> Re: Your Order #48291 — Here's Where Things Stand
<strong>Hi Rachel,</strong>
Eighteen days with no update and two unanswered emails — I completely understand why you're frustrated, and I'm sorry we haven't been in touch sooner. You deserved a response long before now.
I've looked into your order (#48291) and I can confirm it was shipped and was last scanned at our Chicago distribution hub on February 23rd. The carrier has unfortunately experienced regional delays that have affected tracking updates in that area. This is not the experience we want for you.
Here's what I'm doing right now:
1. I've submitted a priority trace request with the carrier — they have 24 hours to provide a confirmed delivery window.
2. I'll send you a direct update by end of day tomorrow (March 11th) with either a confirmed delivery date or a clear path forward.
3. If we cannot confirm delivery before your event on [date], please reply to this email and I will personally escalate your case to ensure the best possible resolution.
We'll make sure this gets sorted for you, Rachel.
Warm regards,
James · Customer Support · Lumio Co.
─────────────────────────────────────────
<strong>⚑ AGENT NOTE (Internal — Remove Before Sending)</strong>
• Category detected: Shipping delay
• Emotional tone: Frustrated / Urgent
• Escalation status: Not triggered. Refund was requested but not approved — reply does not promise refund; instead routes to follow-up.
• Flag for agent: Confirm customer's event date before sending (left as [date]). If carrier trace comes back negative within 24hrs, escalate to Tier 2 for resolution decision. Do not send this draft without filling in the event date.</div>
</div>
</section>
<!-- 7. UPGRADE TIPS -->
<section class="section">
<div class="section-header">
<span class="section-number">07</span>
<div class="section-title-wrap">
<span class="section-tag">Extend & Chain</span>
<h2 class="section-title">Agent Upgrade Tips</h2>
</div>
</div>
<div class="upgrades">
<div class="upgrade-card">
<div class="up-num">A</div>
<strong>Sentiment Triage Agent</strong>
<p>Add an upstream classifier agent that reads incoming emails and scores urgency (1–5) and emotional intensity before passing to this agent. High scores auto-route to priority queues, enabling this agent to adapt its opening empathy level automatically without manual input.</p>
</div>
<div class="upgrade-card">
<div class="up-num">B</div>
<strong>CRM Context Injector</strong>
<p>Chain this agent with a CRM lookup tool (Zendesk, HubSpot, Salesforce) that auto-pulls order history, prior tickets, and customer tier before the draft is generated. This eliminates the manual "prior resolution context" input field and makes every reply factually grounded by default.</p>
</div>
<div class="upgrade-card">
<div class="up-num">C</div>
<strong>Post-Send Quality Scorer</strong>
<p>Add a downstream agent that reviews sent emails (after human edits) and scores them against tone, resolution accuracy, and CSAT correlation. Over time, this creates a feedback loop that sharpens the draft agent's output quality — and flags which human agents are making the best edits for training.</p>
</div>
</div>
</section>
<footer class="footer">
<p>AI Agent Blueprint · Customer Support Email</p>
<p>Production-Ready · Human Review Required</p>
</footer>
</div>
</body>
</html>
Instant access
Commercial use
Money‑backBy purchasing this prompt, you agree to our terms of service
17
Views
CLAUDE-4-6-SONNET
Build AI agents for any task — support, sales, content, ops, or data — without coding. Describe your task, input, and rules → get a complete agent blueprint with role, step-by-step logic, output format, constraints, and a live test case ready to run. 🔹 What You'll Get: ✅ Full agent structure: role, inputs, workflow, rules ✅ Production-ready output specs ✅ Built-in test case to validate instantly ✅ Upgrade tips to chain
...more
Added over 1 month ago
