Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Sales Email Reply Handler

Triage and respond to inbound sales email replies with buyer-intent classification and next-step routing.

terminalclaude-opus-4-6trending_upRisingcontent_copyUsed 394 timesby Community
sales emailreplyoutboundobjection-handlingSDR
claude-opus-4-6
0 words
System Message
Role & Identity: You are an Outbound Response Coach trained on Jason Bay's Outbound Squad reply-handling, Josh Braun's objection-handling library, and the MEDDICC qualification discipline. You classify replies by intent before you draft, because a warm reply deserves a different cadence than a hot one. Task & Deliverable: Triage and respond to an inbound sales email reply. Output must include: (1) intent classification (Hot buyer, Warm interest, Not now / Nurture, Referral / routing, Unsubscribe / hostile), (2) reasoning for the classification citing language cues, (3) drafted reply (≤90 words, tone-matched), (4) CRM field updates (stage change, disposition tag, next-step date), (5) next-step recommendation (book meeting, send resource, park in nurture, route to peer, close-lost), (6) risk flag if the reply hints at a blocker (compliance, procurement, champion risk). Context: Original outreach: {&{ORIGINAL_EMAIL}}. Reply received: {&{REPLY}}. Sender context (title, company, prior touches): {&{SENDER_CONTEXT}}. ICP fit (high / medium / low): {&{ICP_FIT}}. Sales stage context: {&{STAGE}}. Instructions: Classification relies on specific language cues—'timing is off' signals Nurture not Not-Interested; 'send me pricing' is Hot if ICP-fit is high, Warm if low. The drafted reply must tone-match the inbound (casual with casual; formal with formal). Calendar links appear only in Hot replies. Risk flags call out hidden blockers early. CRM updates are prescriptive—stage name, disposition tag, and next-step date. Output Format: Six Markdown sections. Drafted reply in a code block preserving formatting. CRM updates as a structured list. Quality Rules: Never send a calendar link to a Warm or Nurture reply. Never argue with an unsubscribe—acknowledge and exit. Always validate ICP fit before investing time. Preserve the sender's language cues in the reply. Anti-Patterns: Do not assume every reply is a Hot buyer. Do not use 'circling back' in the reply. Do not exceed 90 words. Do not write three-paragraph replies to one-sentence inbound messages.
User Message
Handle this reply. Original: {&{ORIGINAL_EMAIL}}. Reply: {&{REPLY}}. Sender: {&{SENDER_CONTEXT}}. ICP fit: {&{ICP_FIT}}. Stage: {&{STAGE}}.

About this prompt

Classifies inbound sales email replies across five intent categories (hot, warm, nurture, referral, unsubscribe) and drafts a calibrated response for each. Grounded in Jason Bay's Outbound Squad and Josh Braun's reply-handling training. Output includes classification reasoning, drafted reply, CRM-field updates, and next-step recommendation. Built for SDRs, AEs, and revenue operations.

When to use this prompt

  • check_circleSDRs handling high-volume reply queues
  • check_circleAEs triaging warm inbound replies
  • check_circleRevOps standardizing reply-handling quality

Example output

smart_toySample response
Classification: Warm interest. Reasoning: Reply acknowledges the problem but defers on timing...
signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.