Prompt hub

8 AI prompts for sales and customer support (copy-ready and tested)

Sales and customer support both involve writing similar messages many times a day — a cold outreach email, an objection response, a support reply, a call summary — where the content changes but the structure mostly does not. A language model handles that repetition well, giving you a solid first draft so you can focus on getting the tone and the specific facts right.

The prompts here cover a reply to a difficult customer email, a cold outreach email, objection handling, a follow-up sequence, a support macro, a refund or complaint reply, a knowledge-base article, and a call summary. They work with ChatGPT, Claude and Gemini; paste the customer's message, your product details or the call notes into the fill-in fields so the draft responds to the actual situation rather than a generic complaint.

Two pitfalls to watch for. A model does not know your actual refund policy, pricing or account details, so never send a reply that states a policy or a number without checking it against your real terms first — a confident-sounding but wrong answer can cost you a customer's trust. And a drafted reply to an angry or upset customer can come across as flat or overly formal; read it aloud before sending, and add the specific acknowledgement a template cannot generate for you. The free optimiser is a quick way to check a reply prompt for missing detail before you rely on it for a real customer.

All 8 prompts

  • A prompt for a call summary with exactly three sections and a fixed number of next steps, not a loose recap of everything said.

    Show prompt
    The prompt
    You are a sales or support rep summarising a call for the CRM record.
    
    Objective: Summarise the call below with {{CONTACT NAME}} at {{COMPANY OR ACCOUNT}}.
    
    Context: Purpose of the call: {{PURPOSE OF CALL}}.
    
    Constraints:
    - Use exactly three sections, headed exactly "Summary", "Key points" and "Next steps"
    - "Summary" is one sentence; "Key points" is exactly three bullet points; "Next steps" is exactly two bullet points, each naming an owner
    - Base every point only on the call notes below — do not infer a commitment or figure that wasn't stated
    - Keep the whole summary under 130 words
    
    Output format: Return the three headed sections in order.
    
    Before finishing, check there are exactly three sections with those exact headings, exactly three key points and exactly two next steps each with a named owner, and nothing is inferred beyond the notes.
    
    Call notes:
    {{CALL NOTES}}
    
    View full page →
  • A prompt for a short cold sales email that leads with the prospect's own situation and makes exactly one low-effort ask.

    Show prompt
    The prompt
    You are a sales rep writing a first-touch cold outreach email.
    
    Objective: Write a cold email to {{PROSPECT NAME AND ROLE}} at {{COMPANY}} introducing {{YOUR PRODUCT OR SERVICE}}.
    
    Context: A specific, relevant fact about the prospect or their company: {{RELEVANT FACT}}. The problem your product solves for them: {{PROBLEM SOLVED}}.
    
    Constraints:
    - Open with the relevant fact given above, not a generic greeting
    - Keep the whole email between 60 and 100 words
    - Make exactly one, low-effort ask (e.g. a reply, not a 30-minute call) stated once
    - Do not claim a specific result, statistic or client name that wasn't given above
    
    Output format: Return "Subject:" on its own line, then a blank line, then the email body.
    
    Before finishing, check the email opens with the given fact, is between 60 and 100 words, and contains exactly one ask.
    
    View full page →
  • A prompt for a three-email follow-up sequence with a distinct angle per email, spaced out, and no repeated pitch.

    Show prompt
    The prompt
    You are a sales rep writing a follow-up sequence after a prospect went quiet.
    
    Objective: Write a follow-up sequence to {{PROSPECT NAME}} after {{LAST CONTACT — e.g. a demo, a first cold email, no reply in two weeks}}.
    
    Context: What was offered or discussed: {{WHAT WAS DISCUSSED}}. Anything new worth mentioning since then: {{NEW INFORMATION — or none}}.
    
    Constraints:
    - Write exactly three emails, spaced 3 days, 7 days and 14 days after the last contact
    - Each email must take a different angle (e.g. add value, ask a direct question, polite close-out) and not repeat the previous email's wording
    - Keep each email between 30 and 70 words
    - The third email must offer to close the loop if there's no response, without sounding curt
    
    Output format: Return each email as "Email [number] — Day [X]:" followed by "Subject:" and the body.
    
    Before finishing, check there are exactly three emails at the stated intervals, each is between 30 and 70 words, each takes a distinct angle, and the third offers a polite close-out.
    
    View full page →
  • A prompt for a support knowledge-base article with a numbered fix and exactly three steps, not a wall of unstructured advice.

    Show prompt
    The prompt
    You are a support team lead writing a knowledge-base article for customers.
    
    Objective: Write a knowledge-base article explaining how to {{TASK OR FIX — e.g. reset a password, resolve a sync error}}.
    
    Context: Who runs into this: {{WHO RUNS INTO THIS}}. The steps that actually resolve it: {{STEPS THAT RESOLVE IT}}.
    
    Constraints:
    - Open with one sentence stating what the article covers and who it's for
    - Present the fix as exactly three numbered steps, each one short imperative sentence
    - Close with exactly one sentence on what to do if the steps don't resolve it
    - Keep the whole article between 70 and 130 words
    
    Output format: Return the opening sentence, then "Steps:" with the three numbered steps, then the closing sentence.
    
    Before finishing, check there are exactly three numbered steps, exactly one closing "if this doesn't work" sentence, and the total is between 70 and 130 words.
    
    View full page →
  • A prompt for exactly three response options to one sales objection, each under 60 words, without dismissing the prospect's concern.

    Show prompt
    The prompt
    You are a sales rep preparing responses to a common objection.
    
    Objective: Draft responses to this objection about {{PRODUCT OR SERVICE}}: {{OBJECTION — quote it directly}}.
    
    Context: What's actually true about this concern: {{TRUTH ABOUT THE CONCERN}}. Anything the product genuinely cannot do here: {{LIMITATION — or none}}.
    
    Constraints:
    - Provide exactly three different response options, each taking a distinct angle (e.g. reframe, evidence, question back)
    - Keep each response under 60 words
    - Acknowledge the objection as valid before responding to it — do not dismiss or minimise the concern
    - Do not claim the limitation doesn't exist if one was given above
    
    Output format: Return each response as "Option [number]: [angle name]" followed by the response text.
    
    Before finishing, check there are exactly three response options, each under 60 words, and none dismiss the objection outright or hide a stated limitation.
    
    View full page →
  • A prompt for a customer complaint reply that validates the issue first and states one clear outcome, without over-apologising.

    Show prompt
    The prompt
    You are a customer support agent replying to a complaint or refund request.
    
    Objective: Reply to this complaint about {{PRODUCT OR ORDER}}: {{COMPLAINT — quote or summarise it}}.
    
    Context: The decision on this request: {{DECISION — e.g. full refund approved, partial refund, refund declined and why}}. Company policy relevant here, if any: {{RELEVANT POLICY — or none}}.
    
    Constraints:
    - Acknowledge the specific issue described, not a generic "sorry for the inconvenience"
    - Say the word "sorry" or "apologise" exactly once
    - State the decision plainly in one sentence, with no hedging, whatever it is
    - Keep the whole reply between 70 and 130 words
    
    Output format: Return the reply as plain text, ready to send.
    
    Before finishing, check "sorry" or "apologise" appears exactly once, the decision is stated in one plain sentence, and the reply is between 70 and 130 words.
    
    View full page →
  • A prompt for a reusable customer support macro under 90 words with one placeholder for personal detail, not a generic form letter.

    Show prompt
    The prompt
    You are a customer support lead writing a reusable reply macro for a common issue.
    
    Objective: Write a support macro for agents to use when {{SITUATION — e.g. a customer reports a late delivery}}.
    
    Context: What actually caused this, if known: {{CAUSE — or unknown}}. What the business will do about it: {{RESOLUTION OFFERED}}.
    
    Constraints:
    - Keep the macro between 50 and 90 words
    - Include exactly one placeholder, written as [CUSTOMER NAME], for the agent to personalise — no other placeholders
    - State the resolution plainly in one sentence; do not promise a timeframe or compensation beyond what was given above
    - Tone must be warm and direct, not corporate or overly formal
    
    Output format: Return the macro as plain text, ready to paste into a support tool.
    
    Before finishing, check the macro is between 50 and 90 words, contains exactly one placeholder, [CUSTOMER NAME], and promises nothing beyond the resolution given above.
    
    View full page →
  • A prompt for drafting a calm, clear reply to a frustrated or confrontational email without either caving or escalating.

    Show prompt
    The prompt
    You are helping draft a professional reply to a difficult email.
    
    Objective: Write a reply that addresses {{THE PERSON'S}} concern about {{WHAT THEY'RE UNHAPPY ABOUT}} while staying calm and factual.
    
    Context: Your relationship to this person is {{RELATIONSHIP — e.g. client, colleague, manager}}. What you can actually offer or commit to: {{WHAT YOU CAN OFFER}}.
    
    Constraints:
    - Acknowledge their concern in the first two sentences, specifically, not generically
    - Do not apologise for things that were not actually your fault
    - Do not promise anything beyond what was stated you can offer
    - Keep it under 150 words
    
    Output format: Return the email with a subject line, ready to send.
    
    Before finishing, check that nothing in the reply commits to something beyond what was stated as available.
    
    Their email:
    {{PASTE THEIR EMAIL HERE}}
    
    View full page →

Frequently asked questions

Can I send a generated reply straight to a customer?
Check it against your actual policy, pricing and account details first — a model does not know your real terms and can generate a confident but incorrect answer.
Will these prompts work for any CRM or helpdesk tool?
Yes, the output is plain text you can paste into any CRM, helpdesk or email client; the prompts are not tied to a specific platform.
Can these prompts handle an angry customer well?
They give you a structure, but read the tone carefully before sending — generated replies to upset customers can sound flat, so add a specific, genuine acknowledgement yourself.
Do I need to log in to use the sales and support prompts?
No, every prompt is free and works without an account; paste in the customer's message or call notes and fill in the labelled fields.