Intermediate
AI for Sales Conversations
Follow-up from notes you already have.
Anyone can use this page. Copy the prompt and try it today.
$6.99
Intermediate
Follow-up from notes you already have.
Anyone can use this page. Copy the prompt and try it today.
$6.99
Everyday AI
Follow-up from notes you already have.
You stay the editor. The model drafts. You decide.
$6.99 · 20 pages
Intermediate shelf · prompts from real call notes · you stay the seller
CONTENTS
Read pages 3 through 6. Then copy one cream box.
THE IDEA
A chat was not beside Elena when the buyer paused and said, “Not during inventory.” It did not hear whether that was a firm no, a timing problem, or a request for another path. It can shape Elena's notes into a clear recap. It cannot decide what the buyer meant.
It drafts from evidence. Give it call notes, exact words, promises, known dates, and approved product facts. If it supplies a number, quote, customer story, price, discount, or competitor claim you did not provide, delete it.
A prompt is a job. Role + Task + Details + Format. Name who it helps, what it produces, which facts it may use, and the answer's shape.
You stay the seller. You choose the question, judge the moment, check every claim, send the message, and own the relationship.
The useful division is simple: notes in, draft out, seller checks.
WHAT THE LABS FOUND
1 · OpenAI Writing is about 40 percent of work-related ChatGPT messages. About two-thirds of those writing messages modify text the user supplied. Start with real notes, not a magical pitch.
2 · Anthropic Clear roles and direct instructions help. With long material, source text first and the question last improved quality by up to 30 percent in Anthropic's tests. “Up to” is not a promise.
3 · Google Useful prompts identify objective, persona, context, constraints, and response format. The cream boxes use Role / Task / Details / Format.
4 · Anthropic Fluency Index People who iterate also show more goal-clarifying and evaluation behaviors. This is correlational, not proof that revision causes sales success.
None of these sources measured sales win rates. The narrower lesson: provide evidence, define the job, and check the draft.
BEFORE YOU PASTE
Jules has twelve rushed lines after a demo. One is the buyer's exact sentence. Two are Jules's guesses. A third contains a private mobile number. Pasted together, guesses may return as polished facts.
THEY SAID Exact words or faithful notes.
WE PROMISED Only commitments your team made.
KNOWN FACTS Approved product facts, dates, and prices.
UNKNOWN Authority, budget, sentiment, competitors, or timing not confirmed.
NEXT STEP Only what somebody actually named.
Remove personal data you do not need. Follow company tool and data rules. Do not paste passwords, payment details, private recordings, restricted files, or confidential customer data.
Before the box, say: “Use THEY SAID, WE PROMISED, and KNOWN FACTS. Keep UNKNOWN visible. Do not turn guesses into buyer facts.”
NOTES INTO A MESSAGE
Diego has five lines: month-end close is painful, Thursday was mentioned, and nobody discussed price. He needs a follow-up, recap, or handoff—not three invented pitches.
COPY THIS
Role: You are a sales-message editor. I remain the seller and sender.
Task: Turn my notes into [buyer follow-up / buyer recap / teammate handoff].
Details: Notes first: [paste]. Audience: [name or role]. Promise: [fact or NONE]. Confirmed next step: [fact or UNKNOWN].
Format: Follow-up: subject + 5–7 sentences. Recap: decisions, open questions, confirmed next step. Handoff: THEY SAID / WE PROMISED / UNKNOWN / NEXT STEP.
Hard nos: Do not invent metrics, prices, discounts, quotations, competitor claims, social proof, urgency, buyer feelings, or next steps. Keep UNKNOWN visible.
Then do this. Match every sentence to a note. If it becomes a brochure, reply: “Remove the pitch. Preserve their words, promises, unknowns, and confirmed next step only.”
DISCOVERY QUESTIONS
Hannah heard, “We hate the current tool at month-end.” Six generic questions would waste the next call. She needs a short path into that sentence without assuming the cause.
COPY THIS
Role: You are a discovery-question editor. I run the conversation.
Task: Build a short sequence from what I actually heard.
Details: Notes first: [paste]. Exact phrase: [month-end is where it hurts]. Person: [ops lead]. Time: [20 minutes]. Gap: [what fails and who is affected].
Format: Up to five questions in order. Cite the note that earned each. Include a clarification, process question, impact question without demanding a number, and next-step question.
Hard nos: Do not assume pain, budget, authority, urgency, competitor, cause, or desired solution. Do not put words in the buyer's mouth.
Then do this. Cross out any question that fits every buyer. If nothing remains, ask: “When you say month-end is difficult, what happens?”
THE OBJECTION IN THEIR WORDS
Rue hears, “This looks like a lot for a team of four.” A canned rebuttal could turn a sensible concern into a contest. She needs to learn what “a lot” means.
COPY THIS
Role: You are an objection-response editor. Help me listen before replying.
Task: Draft a response grounded in their exact objection and approved facts.
Details: Objection: [paste]. Known: [team of four; asked about setup time]. Approved answer facts: [paste or NONE]. Channel: [spoken / email].
Format: One acknowledgment; one neutral question; only if facts exist, a reply under four sentences; one graceful stop.
Hard nos: Do not invent proof, savings, adoption rates, customer stories, discounts, competitor weaknesses, or motives. Do not pressure them.
Then do this. Read the acknowledgment and question first. If the answer outruns your evidence, delete it. A good question is safer than unsupported proof.
THE ASK, ONE SENTENCE
Anika's buyer said, “Send something we can look at Friday.” The draft should not turn that into a booked meeting, deadline, or seven-line close.
COPY THIS
Role: You are a concise next-step editor. I choose and send the ask.
Task: Write one sentence using the next step the buyer named.
Details: Their words: [paste]. What I can send: [approved one-page overview]. Recipient: [name or role]. Timing: [Friday].
Format: One subject. One sentence saying what I am sending and checking the next step. A second sentence only to repeat confirmed timing or invite correction.
Hard nos: Do not invent a meeting, calendar hold, deadline, stakeholder, commitment, metric, discount, or urgency. Do not say “agreed” unless my notes do.
Then do this. Compare the ask with their sentence. If the draft asks for more than they offered, shrink it. If Friday is ambiguous, ask.
PREP FOR THE NEXT CALL
Theo has a Thursday call, three buyer comments, and one large unknown: who else needs to be involved. He needs a memory aid, not an invented executive agenda.
COPY THIS
Role: You are a call-prep editor working only from my notes. I run the call.
Task: Build a one-page prep sheet separating evidence from open questions.
Details: Notes: [paste]. Confirmed attendees: [or UNKNOWN]. Purpose: [or UNKNOWN]. Answers I owe: [list]. Named next step: [or UNKNOWN].
Format: THEIR WORDS; CONFIRMED FACTS; THREE EARNED QUESTIONS; ANSWERS I OWE; OPTIONAL ASK. Mark every gap UNKNOWN.
Hard nos: Do not invent attendees, authority, agenda items, objections, metrics, competitors, buying stages, or outcomes. Do not write a speech.
Then do this. Circle one thing to learn. Open with: “I have us down to discuss [confirmed purpose]. Is that still the useful place to start?”
WHEN THEY PUSH ON PRICE
Priya hears, “Can you do better on price?” No discount was offered. A plausible “standard ten percent” would still be made up and might exceed her authority.
COPY THIS
Role: You are a price-conversation editor. Pricing authority remains with me and my company.
Task: Draft a calm reply using only approved information.
Details: Their words: [paste]. Approved price: [or BLANK]. Discount authority: [limit or BLANK]. Included: [approved facts]. Approver: [role or UNKNOWN].
Format: Acknowledge; ask what “better” means; state only an approved number or [PRICE]; give one accurate review step. Maximum five sentences.
Hard nos: Do not invent a discount, fee, concession, competitor, market rate, urgency, approval, or usual deal. A blank is not an offer.
Then do this. Highlight every currency symbol and percentage. Verify each against an approved source. Otherwise replace it with a blank.
THE BUYING GROUP
Omar knows the ops lead likes the idea, finance has not reviewed it, and “legal will need a look.” That is not enough to declare a champion, blocker, or close date.
COPY THIS
Role: You are an evidence-based stakeholder-map editor. I verify the people and roles.
Task: Map confirmed participants and open questions.
Details: Notes first: [mentions of people, approval, review, access]. Confirmed names and titles: [list]. Exact process words: [paste].
Format: PERSON/TEAM; EXACT EVIDENCE; CONFIRMED ROLE; OPEN QUESTION; WHO CAN VERIFY. Then three neutral questions. Mark unsupported fields UNKNOWN.
Hard nos: Do not invent names, titles, reporting lines, influence, sentiment, authority, procurement steps, legal requirements, or a champion. Do not label a blocker.
Then do this. Delete roles based on inference. Ask: “Who else needs to review this, and what does each person need from us?”
CLEAN CRM NOTES
Camille has scraps across a notebook and invite. The CRM needs usable fields, but the model should not decide the deal is hot or advance its stage.
COPY THIS
Role: You are a CRM-note formatter. Organize evidence; do not judge the deal.
Task: Convert my notes into factual CRM fields for human review.
Details: Raw notes: [paste]. Fields: [contact / stated need / process / promise / next step / date / owner / unknowns]. Stage definitions: [paste or OMIT].
Format: Fill supported fields only. Add a source phrase beside every entry. Use UNKNOWN for gaps. Put contradictions in CHECK.
Hard nos: Do not invent pipeline stage, win probability, forecast value, sentiment, score, authority, close date, metric, quotation, or activity. Do not resolve conflicts silently.
Then do this. Review CHECK first. Enter stages, probabilities, and judgments yourself under company rules.
THE STALLED THREAD
Samira sent the promised one-pager nine days ago. Silence does not prove rejection, busyness, budget trouble, or interest. She needs a low-pressure nudge.
COPY THIS
Role: You are a stalled-thread message editor. I decide whether and when to send.
Task: Draft a brief check-in from the last confirmed exchange.
Details: Last buyer message: [paste]. What I sent: [item]. Date: [date]. Confirmed next step: [or NONE]. Useful new information: [or NONE].
Format: Subject plus three sentences: name the exchange, ask whether the item remains useful, and offer one easy response or clean close.
Hard nos: Do not invent scarcity, deadlines, interest, internal events, budget, a reason for silence, social proof, or “one last chance.” Do not pretend to have news.
Then do this. Remove any sentence manufactured to create anxiety. If there is no useful reason to write, check once or leave the thread alone.
PROPOSAL SKELETON
Owen has discovery notes and an approved service description. He does not have dates, legal terms, or signed-off pricing. A polished proposal could hide those holes.
COPY THIS
Role: You are a proposal-outline editor. I own scope, price, terms, and approval.
Task: Build a labeled draft outline from buyer notes and approved offer facts.
Details: Buyer words: [paste]. Approved offer: [paste]. Scope: [or BLANK]. Price: [approved number or BLANK]. Timing: [dates or BLANK]. Terms: [approved text or BLANK].
Format: DRAFT; THEIR SITUATION; PROPOSED SCOPE; OUT OF SCOPE; OPEN DECISIONS; PRICE; TIMING; NEXT STEP. Use [BLANK—OWNER TO CONFIRM].
Hard nos: Do not invent price, discount, fee, scope, deliverable, metric, saving, result, date, legal term, quotation, or proof. Do not make guarantees.
Then do this. Route every blank to its human owner. Check that the proposal matches what you sell and what the buyer said.
AFTER A NO
Nia hears, “Not this quarter.” She needs a courteous note. Later, she may need an internal review. Neither job should rewrite the no into a hidden yes.
COPY THIS
Role: You are a respectful closeout editor. I choose the message and interpretation.
Task: Produce [buyer thank-you / internal evidence review] from the same notes.
Details: Exact no: [paste]. Given reason: [or UNKNOWN]. Timing named: [or NONE]. Open commitments: [or NONE].
Format: Buyer note: thanks, acknowledge, close commitments, later check only if invited. Internal: FACTS / OUR ACTIONS / UNKNOWN / ONE PROCESS LESSON TO TEST.
Hard nos: Do not invent a loss reason, competitor, budget issue, hidden interest, future date, discount, blame, or comeback strategy. Do not present speculation as feedback.
Then do this. Delete every leftover pitch from the buyer note. Label internal interpretations as hypotheses.
STUCK
When the output is wrong, name the exact failure.
Invented number: “List every number and its source. Delete any without one.”
Marketing copy: “Use buyer wording. Remove adjectives, claims, and unrequested pitch.”
Guessed role or stage: “Mark unsupported roles, sentiment, stage, and probability UNKNOWN.”
Bigger ask: “Use only the next step they named.”
Argument: “Keep one acknowledgment and one neutral question.”
Fake urgency: “Delete scarcity and invented reasons for silence.”
Filled price: “Replace every unapproved number with [BLANK].”
Hidden uncertainty: “Move every inference into UNKNOWN.”
If repair fails, open a clean thread. Paste less material under the five headings from page 5. A shorter truthful draft beats fluent fiction.
WEEK PLAN
This is not a quota for using AI. Use a page only when a real sales moment needs it.
Monday: Sort one set of notes into words, promises, facts, unknowns, and next step.
Tuesday: Turn those notes into one message. Check every sentence.
Wednesday: Prepare two discovery questions or one objection reply.
Thursday: Review one price or stakeholder conversation. Leave authority, discounts, and roles blank until confirmed.
Friday: Clean a CRM record or inspect a stalled thread. Do not assign probability, sentiment, or urgency.
Keep only drafts that saved editing time without creating factual cleanup. Add useful repair lines to your own prompt library.
The goal is not more messages. It is fewer unsupported sentences and clearer human follow-through.
BEFORE YOU SEND
Marcus has a polished email open. Before sending, he runs one final pass with his own eyes.
Numbers: Source every metric, price, fee, discount, percentage, date, and time.
Words: Make every quotation exact. Otherwise paraphrase without quotation marks.
People: Confirm each name, title, role, attendee, approver, and owner.
Promises: Verify every deliverable, concession, result, and deadline.
Proof: Use only approved, relevant product claims and customer examples.
Next step: Was it named, or are you clearly asking?
Tone: Respect no, uncertainty, and silence.
Privacy: Follow company policy and approved-tool rules.
If a sentence cannot point to notes or an approved source, cut it, turn it into a question, or leave a blank. You remain the editor, seller, and sender.
SOURCES
Chatterji et al., “How People Use ChatGPT,” September 2025. Writing share and modification claim.
https://openai.com/index/how-people-are-using-chatgpt/
Anthropic Docs, “Be clear and direct.” Roles, direct instructions, long material first, and questions last; up to 30 percent in long-document tests.
https://docs.anthropic.com/en/docs/build-with-claude/prompt-engineering/be-clear-and-direct
Google Cloud, “Prompt design strategies.” Objective, persona, constraints, context, and response format.
https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/prompts/prompt-design-strategies
Anthropic Academy, “The AI Fluency Index,” 2026. Correlational association between iteration and other fluency behaviors.
https://academy.claude.com/tutorials/the-ai-fluency-index
These sources support writing and prompting practices. They do not establish higher sales win rates.