16 ready-to-use ChatGPT prompts for sales automation. Fill in the bracketed fields, paste into ChatGPT, and go.
Sales · 16 prompts
01
Design an Automated New-Lead Follow-Up Flow with Personalization, Routing, and SLA Rules
Design an automated new-lead follow-up flow with personalization logic, routing rules, response timing, and SLA-aware escalation paths instead of a single generic script.
You are a sales operations strategist designing lead-response automation.
Design an automated follow-up flow using the context below.
Context:
- Offer: [offer]
- Lead source: [lead source]
- Inquiry context: [inquiry context]
- Goal: [goal]
- Tone constraints: [tone]
- Routing rules: [routing]
Instructions:
1. Insert real personalization fields (what they asked about, their source) into the automated message rather than a fully generic template, since a lead can tell the difference and it affects trust in the brand from the first touch.
2. Define routing logic that sends the lead to the right rep or queue based on source and inquiry content, not a single shared inbox that creates response delay.
3. Set an SLA for response time and an escalation path if the SLA is missed (alert a manager, auto-reassign), since automation without an SLA backstop just creates a faster way to still drop leads.
4. Note the point at which the automated flow should hand off to a human rather than continuing to send automated messages.
5. Include a fallback message for when personalization fields are missing or malformed, so the lead never receives a broken template.
Output format:
- Automated message with personalization fields
- Routing logic
- SLA and escalation path
- Human handoff trigger
- Fallback for missing/malformed data
Missing information policy:
Ask up to 2 concise questions only if the lead source or routing rules are unclear.
Quality bar:
- Real personalization, not fully generic.
- SLA has an escalation path, not just a target.
- Includes a fallback for malformed data.
02
Design an Automated Lead Qualification Workflow
Create a workflow for automating sales-lead qualification without losing practical judgment.
You are a sales operations strategist.
Design an automated lead qualification workflow using the context below.
Context:
- Sales process: [process]
- Qualification criteria: [criteria]
- Tools available: [tools]
- Handoff goal: [goal]
- Constraints: [constraints]
Instructions:
1. Limit full automation to clear-cut cases (obvious fit or obvious disqualifier) and route ambiguous leads to a human reviewer, since automated qualification logic can silently drop borderline-but-real opportunities.
2. Define the specific data points the automation checks and where each comes from, so the logic isn't a black box the team can't audit.
3. Build in a periodic audit of leads the automation disqualified, to catch systematic errors before they compound.
4. Note where qualification criteria might go stale (an ideal customer profile that changes) and how the workflow should be reviewed and updated.
5. Keep the workflow simple enough to explain to a new rep in a few minutes.
Output format:
- Automated vs human-review criteria
- Data points and sources
- Disqualified-lead audit process
- Criteria staleness review cadence
Missing information policy:
Ask up to 2 concise questions only if the qualification criteria or tools are unclear.
Quality bar:
- Ambiguous leads route to a human, not silent auto-disqualification.
- Logic is auditable, not a black box.
- Includes a disqualified-lead audit process.
03
Design an Automated Web Inquiry Response Flow with Qualification and Handoff Logic
Design an automated web inquiry response flow with acknowledgement, light qualification, handoff logic, and clear expectations for human follow-up.
You are a sales operations strategist.
Design an automated web inquiry response flow using the context below.
Context:
- Offer: [offer]
- Lead source (contact form, chat widget): [lead source]
- Goal: [goal]
- CTA: [cta]
- Tone constraints: [tone]
- Handoff rules: [handoff rules]
Instructions:
1. Set an accurate expectation in the automated reply about what happens next and when a human will follow up — an automated reply that implies immediate personal attention when the actual response time is a day sets the lead up to feel misled.
2. Include one or two light qualification questions in the automated flow if it doesn't slow down acknowledgment, since faster qualification means faster useful routing.
3. Define the handoff trigger to a human rep clearly, including what context transfers with the lead.
4. Note what happens if the lead replies to the automated message with a question the automation can't answer, so they don't get stuck in a dead end.
5. Keep the tone warm but not falsely personal (avoid implying a human wrote this if it didn't).
Output format:
- Automated acknowledgment message
- Light qualification questions
- Handoff trigger and context transfer
- Dead-end fallback for unexpected replies
Missing information policy:
Ask up to 2 concise questions only if the lead source or handoff rules are unclear.
Quality bar:
- Sets accurate expectations, not implied false immediacy.
- Handoff trigger and context transfer defined.
- Includes a fallback for replies the automation can't handle.
04
Create an Automated Weekly Sales Report Template
Build a weekly automated sales report template with the most useful performance metrics.
You are a revenue operations strategist.
Build a weekly automated sales report template using the context below.
Context:
- Team context: [team]
- Metrics to include: [metrics]
- Stakeholders: [stakeholders]
- Reporting goal: [goal]
Instructions:
1. Design the template around week-over-week change, not just static totals — a number without a trend or comparison doesn't tell a reader if things are improving or slipping.
2. Flag any metric likely to be noisy at a weekly cadence (small sample sizes, seasonal effects) so readers don't overreact to normal variance.
3. Include an automatic "needs attention" section that highlights metrics crossing a defined threshold, so the report does some of the interpretation work rather than just listing numbers.
4. Keep the automated version short; a long automated report is the fastest way for stakeholders to start ignoring it.
5. Note what data source feeds each metric so discrepancies can be traced quickly if the automation breaks.
Output format:
- Week-over-week metric layout
- Noise/threshold caveats
- Needs-attention section logic
- Data source mapping per metric
Missing information policy:
Ask up to 2 concise questions only if the metrics or stakeholders are unclear.
Quality bar:
- Built around week-over-week change, not static totals.
- Flags metric noise explicitly.
- Short enough to actually get read weekly.
05
Design an Automated Nurture Email Sequence
Create an automated nurture sequence tailored to different journey stages.
You are a revenue operations strategist.
Design an automated nurture sequence using the context below.
Context:
- Offer: [offer]
- Customer journey stages: [journey]
- Goal: [goal]
- Segments: [segments]
- Constraints: [constraints]
Instructions:
1. Build branching logic keyed to engagement signals (opened but didn't click, clicked but didn't convert) rather than a single fixed sequence that fires identically regardless of behavior.
2. Define an exit condition — what engagement or lack of engagement should stop the automated sequence, since continuing to nurture someone who's clearly disengaged wastes sends and risks spam complaints.
3. Note where a strong engagement signal should trigger a human handoff instead of continuing pure automation.
4. Keep messaging genuinely differentiated by journey stage; a nurture sequence that reads the same at every stage isn't really stage-aware.
5. Set a maximum sequence length so it doesn't run indefinitely for contacts who never engage.
Output format:
- Stage-based branching logic
- Exit conditions
- Human-handoff trigger
- Maximum sequence length
Missing information policy:
Ask up to 2 concise questions only if the customer journey or segments are unclear.
Quality bar:
- Branches on real engagement signals, not fixed for everyone.
- Includes explicit exit conditions.
- Has a human-handoff trigger for strong signals.
06
Design an AI-Driven Lead Scoring System
Outline a practical system for scoring and prioritizing leads using available signals.
You are a revenue operations strategist.
Design a lead scoring system using the context below.
Context:
- Business model: [business model]
- Ideal customer profile: [icp]
- Data available for scoring: [data]
- Sales motion: [motion]
- Goal: [goal]
Instructions:
1. Weight scoring signals based on what has actually correlated with closed-won deals historically, not on assumed importance, since intuitive signals often don't match what the data shows.
2. Set a recalibration cadence, since a scoring model that isn't revisited drifts out of sync as the ideal customer profile or market shifts.
3. Define what happens at each score tier (auto-route to sales, add to nurture, deprioritize) so the score isn't just a number without action attached.
4. Flag the risk of the score reinforcing existing bias if it's trained only on past deals, which can systematically underscore genuinely good but atypical-looking leads.
5. Keep the model explainable enough that a rep can understand roughly why a lead scored the way it did, rather than a pure black box.
Output format:
- Scoring signal weighting (with reasoning)
- Score-to-action mapping by tier
- Recalibration cadence
- Explainability and bias-risk notes
Missing information policy:
Ask up to 2 concise questions only if the ICP or available data is unclear.
Quality bar:
- Weighting tied to actual historical correlation, not assumption.
- Includes a recalibration cadence.
- Addresses explainability and bias risk.
07
Recommend Tools for Repetitive Sales Task Automation
Recommend categories of tools for automating repetitive sales work like data entry and scheduling.
You’ll needteam contexttasks to automatebudgetintegration needs
Prompt
You are a revenue operations strategist evaluating automation tooling.
Recommend tool categories using the context below.
Context:
- Team context: [team]
- Tasks to automate: [tasks]
- Budget: [budget]
- Integration needs (existing CRM, calendar, email stack): [integrations]
Instructions:
1. Recommend tool categories and evaluation criteria rather than naming specific vendors as fact, since pricing and feature sets change and a name-drop list goes stale fast.
2. Prioritize integration fit with the existing stack over feature richness, since a powerful tool that doesn't sync cleanly with the CRM creates more manual work than it saves.
3. Flag tasks that are actually good automation candidates (high-volume, low-judgment) versus ones that look automatable but need human judgment to avoid errors.
4. Note the switching cost and change-management effort for the team, not just the tool's sticker price, since adoption failure is a common reason automation initiatives don't pay off.
5. Recommend starting with one or two tasks rather than automating everything at once.
Output format:
- Tool categories with evaluation criteria
- Integration-fit priorities
- Good vs poor automation candidates among the named tasks
- Adoption/change-management notes
- Recommended starting scope
Missing information policy:
Ask up to 2 concise questions only if the tasks or integration needs are unclear.
Quality bar:
- Recommends categories and criteria, not just vendor names.
- Integration fit prioritized over raw features.
- Distinguishes good automation candidates from poor ones.
08
Create an Automated Follow-Up Reminder System
Design a system for tracking follow-up tasks and reminding reps about potential clients.
You are a revenue operations strategist.
Design a follow-up reminder system using the context below.
Context:
- Sales workflow: [workflow]
- CRM context: [crm]
- Follow-up rules: [rules]
- Team size: [team size]
- Tools available: [tools]
Instructions:
1. Limit reminders to genuinely actionable follow-ups, since a system that reminds on every open task trains reps to tune out all reminders, including the important ones.
2. Prioritize reminders by deal value or urgency rather than firing them all with equal weight.
3. Define what happens if a reminder is repeatedly snoozed or ignored (manager visibility, reassignment) so at-risk deals don't silently fall through.
4. Note the data dependency — the system is only as reliable as the CRM data feeding it, so flag what happens with incomplete records.
5. Keep the reminder cadence realistic for the team's actual follow-up capacity, not an idealized touch frequency nobody can sustain.
Output format:
- Actionability filter for reminders
- Priority weighting
- Escalation for ignored reminders
- Data-dependency notes
- Realistic cadence
Missing information policy:
Ask up to 2 concise questions only if the follow-up rules or CRM context are unclear.
Quality bar:
- Filters for genuinely actionable reminders.
- Includes escalation for ignored reminders.
- Cadence realistic for team capacity.
09
Design a Sales Chatbot Conversation Flow with Qualification, Routing, and Failure Boundaries
Design a sales chatbot conversation flow with qualification questions, routing rules, lead capture priorities, and failure boundaries for when a human should take over.
You’ll needofferwebsite contextlead info to capturehandoff goaltonerouting or escalation rules
Prompt
You are a conversation design strategist for sales chatbots.
Design a chatbot conversation flow using the context below.
Context:
- Offer: [offer]
- Website context: [website context]
- Lead info to capture: [lead info]
- Handoff goal: [goal]
- Tone constraints: [tone]
- Routing or escalation rules: [routing]
Instructions:
1. Design an explicit failure boundary — after how many unrecognized inputs or how much visible frustration should the bot hand off to a human or offer a direct contact option, rather than looping the visitor through repeated "I didn't understand that" responses.
2. Keep the qualification questions minimal and front-load the ones most likely to route correctly, since visitors abandon chatbot flows quickly.
3. State clearly within the flow that the visitor is talking to a bot, to avoid the trust cost of a visitor realizing later they weren't talking to a person.
4. Define routing logic so captured leads reach the right queue based on their answers, not a single generic "someone will follow up" close.
5. Note what happens outside business hours or when no human is available to take the handoff.
Output format:
- Conversation flow with qualification questions
- Explicit failure/frustration boundary
- Routing logic
- Off-hours handling
- Bot-disclosure note
Missing information policy:
Ask up to 2 concise questions only if the offer or routing rules are unclear.
Quality bar:
- Explicit failure boundary defined.
- Discloses it's a bot.
- Handles off-hours/no-human-available case.
10
Create an Automated CRM Update Process
Design an automated process for updating CRM records after sales interactions.
You’ll needcrm setupinteraction typesdata to updateworkflow constraints
Prompt
You are a revenue operations strategist.
Design an automated CRM update process using the context below.
Context:
- CRM setup: [crm]
- Interaction types (call, email, meeting): [interaction types]
- Data to update: [data]
- Workflow constraints: [constraints]
Instructions:
1. Define conflict rules for when automated updates and manual rep updates touch the same field around the same time, since silent overwrites are a common source of CRM data corruption.
2. Specify which fields are safe to fully automate versus which need human confirmation (e.g. deal stage changes usually shouldn't be fully automated based on a single signal).
3. Note the risk of duplicate triggers firing from the same interaction across multiple integrations, and how the process avoids double-logging.
4. Build in an audit trail so a rep can see what an automation changed and when, in case something needs to be manually corrected.
5. Set a periodic data-quality check to catch systematic automation errors early.
Output format:
- Automated vs human-confirmed fields
- Conflict-resolution rules
- Duplicate-trigger prevention
- Audit trail approach
- Data-quality check cadence
Missing information policy:
Ask up to 2 concise questions only if the CRM setup or interaction types are unclear.
Quality bar:
- Conflict rules defined explicitly.
- Duplicate-trigger risk addressed.
- Includes an audit trail.
11
Create Trigger Rules for Personalized Sales Emails
Build trigger rules for sending personalized emails based on customer behavior.
You are a revenue operations strategist.
Build trigger rules for personalized sales emails using the context below.
Context:
- Customer actions to trigger on: [actions]
- Email goal: [goal]
- Platform context: [platform]
- Segments: [segments]
- Constraints: [constraints]
Instructions:
1. Define a recency window for each trigger, since acting on stale behavioral data (a page visit from two weeks ago treated as a hot signal today) sends emails that feel out of touch.
2. Set suppression rules to prevent multiple triggers firing near-simultaneously from the same contact, which can result in a confusing flood of emails instead of one coherent message.
3. Note which triggers are strong intent signals versus weak/ambiguous ones, and weight the messaging urgency accordingly.
4. Include a frequency cap so a highly active contact doesn't get triggered emails so often that it feels like spam.
5. Build in a way to disable or adjust a trigger quickly if it starts misfiring after a platform or tracking change.
Output format:
- Trigger definitions with recency windows
- Suppression rules to prevent overlap
- Strong vs weak signal weighting
- Frequency cap
- Trigger disable/adjust mechanism
Missing information policy:
Ask up to 2 concise questions only if the customer actions or segments are unclear.
Quality bar:
- Recency windows defined per trigger.
- Suppression rules prevent overlapping fires.
- Frequency cap included.
12
Design an Automated Sales Call Transcript Review
Create a framework for automated analysis of sales call transcripts to identify coaching opportunities.
You are a sales enablement strategist designing automated call analysis.
Design a transcript review framework using the context below.
Context:
- Call types: [call types]
- Analysis goal: [goal]
- Quality dimensions to assess (talk ratio, objection handling, next steps): [dimensions]
- Stakeholders using the output: [stakeholders]
Instructions:
1. Go beyond keyword or talk-ratio counting into judgment-based dimensions (was the objection actually resolved, was the next step concrete) since surface metrics alone miss most coaching-relevant signal.
2. Flag transcripts the automated review is less confident about (poor audio quality, ambiguous exchanges) for human review rather than scoring them with false confidence.
3. Aggregate findings across calls to surface patterns (a rep consistently weak on a specific objection type) rather than only reviewing calls one at a time.
4. Note privacy and consent considerations for call recording and analysis, and flag that this needs legal/compliance sign-off in the relevant jurisdiction.
5. Design the output for coaching use — specific, actionable notes tied to a moment in the call — not just a numeric score.
Output format:
- Quality dimensions assessed (with reasoning, not just keyword counts)
- Low-confidence flag for human review
- Cross-call pattern aggregation
- Consent/compliance note
- Coaching-ready output format
Missing information policy:
Ask up to 2 concise questions only if the quality dimensions or analysis goal are unclear.
Quality bar:
- Goes beyond keyword/talk-ratio counting.
- Flags low-confidence calls for human review.
- Includes a consent/compliance note.
13
Design an Automated SMS Re-Engagement Flow with Timing, Consent, and Exit Rules
Design an automated SMS re-engagement flow with timing, consent boundaries, message sequencing, and clear exit rules for unresponsive or low-intent leads.
You’ll needofferlead typegoalCTAtoneconsent or compliance rules
Prompt
You are a revenue operations strategist designing SMS outreach automation.
Design an SMS re-engagement flow using the context below.
Context:
- Offer: [offer]
- Lead type: [lead type]
- Goal: [goal]
- CTA: [cta]
- Tone constraints: [tone]
- Consent or compliance rules: [consent rules]
Instructions:
1. Confirm the flow only targets leads with valid, documented consent to receive texts — SMS marketing carries real regulatory risk (e.g. TCPA in the US) that email doesn't carry in the same way, and this needs explicit handling, not an assumption.
2. Respect time-of-day sending windows appropriate to the lead's time zone, since unsolicited texts outside reasonable hours are both poor practice and a compliance risk.
3. Include a working STOP/opt-out mechanism honored immediately, and confirm the flow checks opt-out status before every send.
4. Keep messages short and clearly identify the sender, since unclear sender identity in SMS reads as spam or a scam attempt.
5. Set a small maximum message count with a clear exit if there's no response.
Output format:
- Consent verification step
- Time-window and time-zone handling
- Opt-out mechanism and check
- Message sequence (short, sender-identified)
- Maximum count and exit rule
Missing information policy:
Ask up to 2 concise questions only if consent rules or lead type are unclear. Do not proceed with message copy until consent handling is confirmed.
Quality bar:
- Consent verification addressed explicitly, not assumed.
- Opt-out mechanism is immediate and checked before every send.
- Sender identity is clear in every message.
14
Design a Post-Meeting Feedback and Signal-Capture Workflow for Sales Conversations
Design a post-meeting feedback and signal-capture workflow that collects useful buyer signals without degrading the relationship or creating survey fatigue.
You’ll needmeeting typegoalaudiencetonefollow-up use case
Prompt
You are a revenue operations strategist.
Design a post-meeting feedback workflow using the context below.
Context:
- Meeting type: [meeting type]
- Goal: [goal]
- Audience: [audience]
- Tone constraints: [tone]
- Follow-up use case: [use case]
Instructions:
1. Limit the ask to one or two questions, since a longer automated survey after every sales meeting causes fatigue and depresses response rates for the meetings that matter most.
2. Trigger the feedback request only for meeting types where the signal is genuinely useful (e.g. not for every internal sync), since blanket automation creates noise.
3. Frame the request in a way that doesn't feel transactional immediately after a relationship-building conversation.
4. Route negative or concerning feedback to a human for immediate follow-up rather than letting it sit in an aggregate dashboard unnoticed.
5. Note how captured signal feeds back into the deal record so it's usable by the AE, not just collected and archived.
Output format:
- Trigger criteria (which meetings get a request)
- Feedback question(s)
- Negative-signal escalation path
- Deal-record integration note
Missing information policy:
Ask up to 2 concise questions only if the meeting type or goal is unclear.
Quality bar:
- Limited to one or two questions.
- Triggered selectively, not for every meeting.
- Negative feedback escalates to a human.
15
Create a Prospect Engagement Alert System
Design an alert system for when a prospect shows significant website or email engagement.
You are a revenue operations strategist.
Design a prospect engagement alert system using the context below.
Context:
- Engagement signals available (page visits, email opens/clicks, content downloads): [signals]
- Sales workflow: [workflow]
- Alert goal: [goal]
- Tools available: [tools]
- Team context: [team]
Instructions:
1. Define which combinations of signals actually indicate real buying intent (e.g. pricing-page visit plus a recent email click) versus routine low-value activity (a single email open), since alerting on every signal trains reps to ignore alerts entirely.
2. Set a threshold or scoring logic so alerts fire only above a meaningful bar, not on any single touch.
3. Route the alert to the owning rep with enough context to act immediately (what page, when, prior engagement history) rather than a bare notification.
4. Note a rate limit per account so repeated activity from the same prospect doesn't flood the rep with duplicate alerts.
5. Include a feedback mechanism so reps can flag alerts that weren't useful, to tune the thresholds over time.
Output format:
- Intent-signal combination criteria
- Alert threshold logic
- Alert content and context included
- Per-account rate limiting
- Feedback/tuning mechanism
Missing information policy:
Ask up to 2 concise questions only if the engagement signals or alert goal are unclear.
Quality bar:
- Alerts on meaningful signal combinations, not every touch.
- Includes context in the alert, not a bare notification.
- Includes a feedback loop to tune thresholds.
16
Review Where Deal Follow-Ups Are Breaking Down
Review where deal follow-ups are breaking down across the sales process and recommend structural fixes.
You are a revenue operations strategist.
Review follow-up breakdowns using the context below.
Context:
- Follow-up workflow: [workflow]
- Deal stages: [stages]
- Known missed follow-ups: [misses]
- Tools used: [tools]
- Owner confusion or ambiguity noted: [owner confusion]
- Goal: [goal]
Instructions:
1. Distinguish structural causes (no clear task owner, no reminder trigger, a tool integration gap) from individual rep inconsistency, since the fix is completely different depending on which it is.
2. Map where in the deal-stage flow follow-ups most often get dropped, rather than treating the problem as evenly distributed across the whole pipeline.
3. Check whether ownership ambiguity (unclear who's responsible after a handoff) is a root cause, since that's a common and fixable structural gap.
4. Recommend fixes proportional to the cause — a tooling gap needs a tooling fix, not more manager reminders to be more careful.
5. Note how to verify the fix actually reduced dropped follow-ups after it's implemented.
Output format:
- Structural vs individual-inconsistency diagnosis
- Stage-by-stage breakdown map
- Ownership-ambiguity assessment
- Proportional fix recommendations
- Post-fix verification method
Missing information policy:
Ask up to 2 concise questions only if the workflow or known misses are unclear.
Quality bar:
- Structural causes separated from individual inconsistency.
- Breakdown mapped by stage, not treated as uniform.
- Includes a way to verify the fix worked.