30 ChatGPT Prompts for SDRs: Research, Cold Emails, Calls and Follow-Ups
Fill the brackets with your notes to get research notes, emails, openers, objection replies and follow-ups. The prompts tell the model to use only the prospect facts you paste and to tag missing facts [VERIFY].
In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Drafted with AI writing assistance and checked against our editorial policy.
Prospect Research Notes
5 promptsAccount Brief From My Notes
1/30✨ What it does
Turns your rough prospect notes into a one-page account brief in table form. Check each row against the company's own site before you use it on a call.
Here is what I know about [PROSPECT COMPANY] and the [JOB TITLE] I want to reach: [PROSPECT NOTES]. Build a one-page account brief as a table with the columns Fact, Source in my notes, Why it matters for my call. Use only facts in my notes. Mark any gap, such as team size, tools in use or recent news, as [VERIFY]. Do not invent a figure, a name or a date. Keep the table to 12 rows at most.
Pro tip: Paste the raw notes as you took them. Typos do not matter, missing sources do.
Research Questions I Still Need
2/30✨ What it does
The model asks five questions about your prospect, then turns your answers into a checklist of research still to do. Work through the open items before you write anything to the prospect.
Ask me first. I am about to research [PROSPECT COMPANY] before a cold email to a [JOB TITLE]. Ask me exactly 5 questions, one at a time, about what I already know and what I still need, such as the reason to reach out now or the tool they probably use. Wait for each answer. After my fifth answer, write a checklist of open research items, and tag any item I did not answer as [VERIFY]. Do not invent an answer for me.
Pro tip: Answer in short phrases. Writing unknown is better than guessing, and the checklist keeps the gap visible.
Referral Ask From a Happy Call
3/30✨ What it does
Drafts a 60-word referral ask in four labelled lines from what the contact actually said. Check any name in the who line against what the contact said before you send it.
Draft a 60 word note I can send to [CURRENT CONTACT] at [COMPANY NAME] asking for an intro to a [TARGET ROLE]. Use only what they said on the call: [WHAT THEY SAID]. Write it as four labelled lines: thanks, why I am asking, who I want to meet, how they can decline. In the who line give [TARGET ROLE]. Add a person's name only if [WHAT THEY SAID] contains one; otherwise write [VERIFY] for the name. Do not invent a compliment, a result or a colleague name they did not mention.
Pro tip: Ask only after a call that went well. A cold referral ask from a first touch reads as pushy.
Reasons to Reach Out Checklist
4/30✨ What it does
Builds a list of reach-out lines, one per trigger your notes support, with the source line from those notes. Check every [VERIFY] trigger against a source you can open before you use it.
Read my notes on [COMPANY NAME]: [PROSPECT NOTES]. Make a checklist of possible reasons to reach out now. Test each candidate against these triggers: a named initiative, a change in the role, a hiring post I read myself, a launch I saw announced, and a referral. Do not invent a trigger that my notes do not contain. Output one line per trigger my notes support, in the form: Trigger, reason to reach out, [source line from my notes]. After those, list each trigger my notes do not support as [VERIFY]. Eight lines at most.
Pro tip: A reason with no source is not a reason. Delete any line you cannot back with a link.
Buyer Pain Hypotheses
5/30✨ What it does
Gives three labelled pain point hypotheses for the buyer, each framed as a question for the call, and picks the one your notes support. Test the chosen question on the call before you rely on it.
Act as a sales researcher for a [PRODUCT CATEGORY] vendor that sells to [JOB TITLE] at companies of [COMPANY SIZE BAND]. Company notes: [PROSPECT NOTES]. Give three pain point hypotheses such a buyer might have, each written as a question I can test on a call. Label all three as hypotheses. Pick the one my notes best support and explain in two sentences. If my notes do not support any, say so and write [VERIFY]. Do not invent a company detail to make a hypothesis sound firmer.
Pro tip: Hypotheses are questions to test, not facts to quote. Never read them out as this company's problems.
Cold Email Drafts
5 promptsFirst Touch Under 90 Words
6/30✨ What it does
Drafts a first cold email under 90 words with one real detail from your notes and a single question. Read it aloud and cut any sentence you would not say to a stranger.
You are an SDR writing a first cold email to a [JOB TITLE] at [COMPANY NAME]. Sign it as [MY NAME] at [MY COMPANY]. I sell [WHAT I SELL IN ONE LINE]. Use one real detail from my notes: [PROSPECT NOTES]. Keep the email under 90 words, with one question at the end and no attachments or links. Add one subject line of four to six words. If my notes hold no real detail, write [VERIFY] in its place. Do not invent a result, a customer name or a claim about the product beyond that line.
Pro tip: Paste the one detail you checked yourself. The email is only as honest as the note behind it.
Three Subject Lines, Pick One
7/30✨ What it does
Offers three subject lines for your draft and picks one with a one-sentence reason. Check that the chosen line makes no promise the email body does not keep.
Here is my draft email to a [JOB TITLE] at [COMPANY NAME]: [DRAFT EMAIL]. Notes: [MY NOTES ON THE PROSPECT AND OFFER]. Write three subject lines, each under seven words, and pick the one a busy [JOB TITLE] is most likely to open. Give the reason in one sentence. Do not let the subject line promise anything the body does not deliver. Flag any result, customer name, number or promise in the draft as [VERIFY] so I can source it. Do not invent support that is not in my notes.
Pro tip: Subject lines that promise more than the body get deleted. Match them to what the email delivers.
Critique My Cold Email
8/30✨ What it does
Scores your cold email on five criteria in a table and rewrites the weakest sentence. Use the score to decide whether the email is ready, then send the rewrite only after you check each claim.
Read my cold email draft below and score it from 1 to 5 on relevance, clarity, length, call to action and tone. Then rewrite only the weakest sentence. Output a table with the columns Criterion, Score, Reason, and end with the rewritten sentence on its own line. Background: [MY NOTES ON THE PROSPECT AND OFFER]. If the draft names a customer, a number or a result that is missing from my notes, tag it [VERIFY]. Do not invent a result or a customer name to strengthen it. Draft: [PASTE DRAFT EMAIL]
Pro tip: Ask for one rewrite at a time. A full rewrite often loses the parts that were already working.
Same Email for a Different Reader
9/30✨ What it does
Rewrites one cold email for a different buyer role, keeping one ask and under 80 words. Check that the swapped detail is one you can source before you send it.
Rewrite the email below for a [NEW READER ROLE] instead of a [ORIGINAL READER ROLE]. Keep it under 80 words and keep the single ask. Swap the detail for one from [NEW DETAIL] that fits this reader, and do not invent a new one. If the new reader needs a fact that is not in the email, mark it [VERIFY]. Email: [PASTE EMAIL]
Pro tip: Run the same draft for each role, then compare the two versions side by side before choosing.
Final Email After Silence
10/30✨ What it does
Writes a short final email after several unanswered messages, with a plain opt-out and no false urgency. Send it only after the earlier emails are logged, so the count in your record is right.
Write a short final email to a [JOB TITLE] at [COMPANY NAME] who has not replied to [NUMBER OF PRIOR EMAILS] earlier emails. Write it in four numbered parts, one job each: 1. why I am writing, 2. the close of the loop, 3. a plain opt-out, 4. the door left open. Keep the whole email under 60 words. Offer notes: [MY OFFER NOTES]. Sign it as [MY NAME]. Use only these notes and do not invent a deadline, an offer or a reason. Tag any gap as [VERIFY].
Pro tip: A plain opt-out line reads as respect. Do not bury it in the last paragraph.
Call Openers and Discovery
5 promptsFifteen Second Cold Call Opener
11/30✨ What it does
Writes a roughly 32-word cold call opener in three numbered parts with one real reason and an easy question. Say it aloud before you dial and time it.
Write a cold call opener I can say in about 15 seconds, roughly 32 words, in three numbered parts: 1. who I am, using [MY NAME] at [MY COMPANY], 2. one real reason I am calling, drawn from [PROSPECT NOTES], 3. one question that is easy to answer. I sell [WHAT I SELL IN ONE LINE]. Give one version only. If my notes give no real reason, write [VERIFY] in part 2; do not invent one. Say nothing about results or customers; the product is only what that line says.
Pro tip: Read it aloud with a timer. Cut any word that does not earn its place.
Discovery Questions as a Table
12/30✨ What it does
Builds a six-row discovery question table with a reason and a listen-for note for each question. Pick three questions for the call and cut the rest so the conversation stays open.
I am preparing a discovery call with a [JOB TITLE] at [COMPANY NAME]. Make a table of six discovery questions with the columns Question, Why I ask it, What to listen for. Base the questions on [PROSPECT NOTES] and on the product area [PRODUCT AREA]. Do not write a question that assumes a tool, team size or budget I did not state. Write [VERIFY] beside any gap in my notes. Do not invent facts about the prospect.
Pro tip: Pick three questions before the call. Six questions in a table is a plan, not a script.
Voicemail Under 20 Seconds
13/30✨ What it does
Fills a short voicemail template with your name, company and one reason, under 35 words, counting [MY CALLBACK NUMBER] as 10 words. Check the callback number before you save the script, because a wrong digit wastes the message.
Fill this voicemail template with my details and nothing else: Hi [PROSPECT FIRST NAME], this is [MY NAME] from [MY COMPANY]. I am calling about [ONE REAL REASON]. You can reach me at [MY CALLBACK NUMBER]. Keep the full message under 35 words, counting [MY CALLBACK NUMBER] as 10 words. Do not invent a claim, a result or a name that is not in my brackets, and write [VERIFY] for any reason I did not give. Output the voicemail, then one line on what to say if they pick up instead.
Pro tip: Name one reason only. Two reasons in a voicemail get neither one heard.
Ask Me Before the Gatekeeper
14/30✨ What it does
Asks five questions about a gatekeeper block, then writes a 25 word gatekeeper line and a 25 word callback line. Use only the facts you answered, and check any [VERIFY] tag before you dial.
Ask me five questions, one at a time, about a gatekeeper block at [COMPANY NAME] before I try to reach a [PROSPECT TITLE]. Cover who usually answers, what I say in the first sentence, what they typically ask, who owns the decision, and my fallback if I am turned away. Wait for each answer. After my fifth answer, write a 25 word gatekeeper line and a 25 word callback line for a [GATEKEEPER ROLE, IF KNOWN]. State who I am truthfully; do not suggest the prospect knows me or expects the call. Do not invent a name, a title or a policy I did not give. If I skip a question, write [VERIFY] in that part of the line.
Pro tip: Answer with what actually happens on that switchboard. A made-up gatekeeper line dies on the first call.
Post-Dial Log From This Attempt
15/30✨ What it does
Turns a rough dial attempt into a six-line log covering outcome, who answered, what was said and the next action. Check the next date against your calendar before you save the log to the CRM.
Build a six-line post-dial log from this attempt to reach a [JOB TITLE] at [COMPANY NAME]: [WHAT HAPPENED ON THE DIAL]. Use these labels, one line each: Outcome, Who answered, What I said, What they said, Next action, Next date. Take every fact from my notes. If a line has no fact, write [VERIFY] there. Do not invent a reply, a name or a date to make the log look complete. Output the six lines only, 20 words or fewer each.
Pro tip: Paste what actually happened, including no answer. Empty logs hide the work you did.
Like these prompts? There are full tutorials behind them.
Learn the workflows, not just the prompts. Easy-to-follow tutorials inside AI Academy, and the library keeps growing.
Objection Replies
5 promptsObjection Table With Proof
16/30✨ What it does
Builds a table of objections with a short reply and the proof you still need for each one. Use a reply only when you hold its proof, and treat the proof column as your to-do list.
Here is a list of objections I hear from [JOB TITLE] buyers: [OBJECTIONS HEARD]. I sell [WHAT I SELL IN ONE LINE]. Build a table with the columns Objection, Short reply under 30 words, Proof I need to supply. In the proof column, name the kind of proof, such as a case note or a reference call, and write [VERIFY] where I have not given one. Do not invent a customer, a result or a number. Give six rows at most.
Pro tip: A reply with no proof behind it is an opinion. Fill the proof column before the call.
Compare Two Replies
17/30✨ What it does
Compares two replies to a common objection in a four-column table and picks one with a reason. Read the claim column first, because that is where a reply can promise more than the product does.
Compare these two replies to the objection 'we already use a tool for this'. Reply A: [REPLY A]. Reply B: [REPLY B]. Notes: [MY NOTES ON THE PROSPECT AND OFFER]. Put them in a table with the columns Tone, Claim made, Risk, Next step it leads to. Then pick the reply I should use with a [JOB TITLE] and give one reason. Mark any claim in either reply that is not in those notes as [VERIFY]. Do not invent a claim to make a reply sound stronger.
Pro tip: Pick the reply with the smaller claim, even if it sounds weaker on paper.
Critique My Objection Reply
18/30✨ What it does
Scores your objection reply on four points and rewrites the one sentence most likely to end the call. Use the rewrite only if every claim in it is one you can prove.
Read my reply to the objection '[OBJECTION]' below. Score it from 1 to 5 for listening, honesty, brevity and next step. Then name the one sentence most likely to end the call and rewrite only that sentence in under 25 words. Notes: [MY NOTES ON THE PROSPECT AND OFFER]. Put [VERIFY] on any proof, name or figure in my reply that those notes do not contain. Do not invent a result to strengthen the reply. My reply: [PASTE REPLY]
Pro tip: Paste the reply exactly as you would say it. Written polish often sounds wrong out loud.
Send Me Info Reply in Three Sentences
19/30✨ What it does
Writes a three-sentence reply to a request for information, with one question and a call offer. Send it only after you have checked that the question fits the need the prospect stated.
You are a calm SDR answering a prospect who says 'just send me some information'. Reply in exactly three sentences: thank them, ask one question about [PROSPECT NEED], and suggest a 15 minute call at a time they choose. Do not attach a link or claim a result. If I leave [PROSPECT NEED] blank, write [VERIFY] and do not invent a need.
Pro tip: The question matters more than the offer. Ask about the need they named, not about your favourite feature.
Budget Not This Quarter Ladder
20/30✨ What it does
Gives a three-step reply ladder for a budget objection, from acknowledgement to a dated follow-up. Set the follow-up date in your CRM before you send step one.
Build a three-step reply ladder for a [JOB TITLE] who says the budget is not open this quarter. Step 1: a short acknowledgement and one question about timing. Step 2: a note that parks the talk for a set date. Step 3: one follow-up for that date. Keep each step under 40 words. Do not invent a budget figure, a fiscal calendar or a date. Write [VERIFY] where my notes say nothing. My notes: [PROSPECT NOTES]
Pro tip: Only promise a follow-up date you will keep. A broken date does more damage than no date.
Follow-Up Sequences
5 promptsFourteen Day Sequence Plan
21/30✨ What it does
Lays out five touches over fourteen days in a table, each with a channel, a purpose and a message angle drawn from your call notes. Check the angle of each touch against what the prospect actually said.
Plan a 14 day follow-up sequence after a first call with a [JOB TITLE] at [COMPANY NAME]. Make a table with the columns Day, Channel, Purpose, Message angle. Use exactly five touches, on days 1, 3, 6, 10 and 14. Base each message angle on [CALL NOTES]. Do not invent a fact, a deadline or a customer name. Write [VERIFY] where the notes stop.
Pro tip: Stop the sequence the moment the prospect replies or asks you to stop.
Re-Engage After a Quiet Spell
22/30✨ What it does
Writes a short re-engagement message in four numbered parts after a long quiet spell, with one new reason and an easy way to decline. Send it only if the new reason is real and dated.
Write a re-engagement message to a [JOB TITLE] at [COMPANY NAME] who went quiet for [DAYS QUIET] days after [LAST CONTACT DATE]. Give it as four numbered parts: 1. one line on why I am back, 2. one new reason from [NEW NOTE], 3. one easy question, 4. a plain way to say no. Keep it under 70 words. If [NEW NOTE] is empty, write [VERIFY] in part 2 and do not invent a reason.
Pro tip: A new reason is required. Repeating the old pitch after two months rarely gets a reply.
Post Meeting Recap Email
23/30✨ What it does
Fills a post-meeting recap email with what the prospect said and the agreed next step, in about 120 words. Read the recap back against your notes before you send it, because a wrong date in writing causes confusion.
Fill in this recap email using only my notes. Hi [PROSPECT FIRST NAME], thanks for the call today about [TOPIC]. What I heard: [WHAT THEY SAID]. Next step we agreed: [NEXT STEP AND DATE]. Tighten my wording to fit about 120 words and flag a missing owner or date in the next step as [VERIFY]. If a detail is missing, write [VERIFY] and do not invent one. Output the email only.
Pro tip: Write the next step with a date and an owner. Vague next steps stall deals.
Sequence Check Before Launch
24/30✨ What it does
Checks each message in your sequence against five lines and marks each one pass or fail. Fix every fail by hand, then rerun the check before the sequence goes live.
Check the five message sequence below for problems. Output a checklist with one line per message, each marked pass or fail, covering: sender name present, one ask, opt-out present, no unsupported claim, under 90 words. My notes: [MY NOTES ON THE PROSPECT AND OFFER]. Tag any promise, number or customer mention in the sequence as [VERIFY] if those notes do not contain it. Do not invent a missing detail to fix a fail. List it instead. Sequence: [PASTE SEQUENCE]
Pro tip: Paste the whole sequence in one go so the checks compare messages against each other.
Shorten a Step for a Busy Reader
25/30✨ What it does
Cuts one follow-up step to 50 words for a phone reader and keeps its single question. Compare the short version with the original to make sure no promise was lost in the cut.
Rewrite follow-up step three below for a busy [JOB TITLE] who reads on a phone. Use 50 words or fewer, with the ask in one sentence and no more than two sentences before it. Keep the same single question. Step: [PASTE STEP THREE]. If the rewrite needs a fact that is not in the step, mark it [VERIFY] and do not invent it.
Pro tip: Read the short version on a phone screen. If the ask gets cut off, move it up.
Go from copy-pasting to actually mastering AI.
AI Academy: hands-on tutorials on ChatGPT, Claude, Midjourney, and many other tools. New tutorials are added regularly.
CRM Notes and Pipeline
5 promptsCall Notes to CRM Fields
26/30✨ What it does
Turns raw call notes into a six-field CRM table with the source line for each value. Check each field against the call before you save it to the record.
Turn these raw call notes into a CRM update table with the columns Field, Value, Source line. Use six fields: Contact role, Stage, Pain in their words, Next step, Next step date, Open question. Take each value from the notes below only. Write [VERIFY] for any field the notes do not cover, and do not invent a date or a name. Notes: [CALL NOTES]
Pro tip: Write the next step date as a real date. A vague date makes the record useless for follow-up.
Five Bullet Call Summary
27/30✨ What it does
Summarises a call in exactly five bullets, one each for want, current tools, blocker, next step and open question. Share it with your manager only after you have checked each bullet against the call.
Summarise this call in exactly five bullets for my manager: [CALL NOTES]. Each bullet has 20 words or fewer. Bullet 1 is what the prospect wants, bullet 2 is what they use now, bullet 3 is the blocker, bullet 4 is the agreed next step, bullet 5 is what I still need to find out. Write [VERIFY] inside any bullet the notes do not cover. Do not invent a number or a name.
Pro tip: Five bullets forces priority. If a point does not fit, it is probably not important.
Three Next Steps, Pick One
28/30✨ What it does
Offers three possible next steps for a call, picks one and gives a reason tied to what the prospect said. Propose only the step your prospect can actually agree to.
My prospect said: [WHAT THEY SAID]. Give three possible next steps I could propose, each under 20 words. Pick the one that best fits what they said and give a one-sentence reason. Do not invent a commitment the prospect did not make. Mark any next step that depends on a fact I do not have as [VERIFY].
Pro tip: Pick the smallest step that still moves the deal. Small yeses are easier to get.
Troubleshoot My Stalled Deals
29/30✨ What it does
Picks the three stalled deals that need a call this week and names a likely cause and a question for each. The causes are hypotheses drawn from your list, so test each one on the call.
Troubleshoot my stalled deals from their symptoms. Today is [TODAY'S DATE]. Each deal is listed with its last reply date, its stage and the last thing the prospect said: [STALLED DEALS LIST]. Pick the three that need a call this week. For each one, name the likely cause in one line and the question to ask in one sentence. Do not invent activity or a reply that is not in the list. Mark any deal with missing data as [VERIFY].
Pro tip: Paste dates, not feelings. A last reply date beats I think they are interested.
Weekly Update Paragraph
30/30✨ What it does
Writes a 100-word weekly update paragraph from your own counts, with one blocker and one change for next week. Check each number against your CRM before it goes to your manager.
Write a 100 word weekly update paragraph for my manager using only these numbers from my week: calls made [CALLS MADE], meetings booked [MEETINGS BOOKED], replies received [REPLIES RECEIVED]. Open with the result, then name my blocker using my words from [MY BLOCKER], then the change I will make next week from [MY CHANGE FOR NEXT WEEK]. Use my words; write [VERIFY] if either is blank. Do not add a number, a target or a comparison I did not give, and do not invent one.
Pro tip: Use the real counts from your CRM export, even when they are low. Managers trust an honest week.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of hands-on tutorials on ChatGPT, Claude, Midjourney, and many other AI tools. New tutorials are added regularly.
7-day free trial. Cancel anytime.
Related guides