MarketingSaves about one to two hours per story draftTested on Claude Sonnet 5.5 and GPT-6, Nov 2026

Draft a customer story from interview notes and approved facts

What this does

This playbook turns your interview notes or transcript into a first draft of a customer story, with problem, approach and result sections. It uses only the facts and numbers the customer has approved. It leaves placeholders for quotes and lists everything that still needs the customer's sign-off. A marketing manager gets a draft ready for review in one sitting, plus a short, specific approval email to send.

Fill in your detailsDownload skill
On this page

Before and after

Before

  • Someone on the marketing team listens to the call recording again, copies lines into a document and writes the story from memory.
  • Figures get rounded, quotes get tidied, and the customer finds the mistakes at the approval stage.

After

  • The notes and approved facts go into one prompt, and a structured draft comes back with the quotes left as placeholders.
  • The reviewer checks the approval list against the draft, so the email to the customer is short and specific.

Saves about one to two hours per story draft

From my practice

When I work with marketing teams on customer stories, the drafts that go smoothly start with facts the customer has already agreed. Writing first and asking later leads to rewrites and awkward emails. I let AI shape the draft, and a person confirms every number, name and quote with the customer before anything goes public.
· AI workflow and adoption consultant

What to have ready

  • The interview notes or a transcript of the customer call, even if rough.
  • The customer's name, and whether they have agreed to be named in public.
  • The results the customer has approved for publication, worded the way they approved them.
  • A line or two on the customer's business: what they do, where, and roughly how big.
  • What your company supplied to them, in plain words.
  • Where the story will appear (website page, PDF, LinkedIn post, sales deck), who should read it and the target length.

Build your prompt

  1. 1. Gather your inputsHave the items above to hand.
  2. 2. Fill in the formYour prompt updates as you type.
  3. 3. Copy or open in your AIClaude, ChatGPT or Gemini.
  4. 4. Review before you sendCheck it against your notes.
Fill in your details

Fill these in. Your prompt updates as you type, and stays in this browser tab.

Your prompt · 0 of 7 filled

You are helping a marketing team write a customer story. Use only the material below. Do not add facts, numbers, dates, job titles or quotes that are not in it. Customer: Customer's business name and the contact person you interviewed, with job title Permission status: What the customer has agreed to, and what is still pending About the customer: A few lines on what the customer's business does and its size What we supplied: What your company did or supplied for this customer Where the story will be used, who will read it and how long it should be: Where the story will appear, who it is for and the target length Interview notes or transcript: Paste your interview notes or transcript as they are, rough is fine Results the customer has approved for publication: Only the results the customer has approved, with the wording they approved Task: Draft the story with these headings: Headline, Summary (two sentences), The problem, What we did together, The result, Quote placeholders. Rules: 1. Numbers. Use only figures listed under approved results, worded as approved. If the notes mention any other figure, keep it out of the story and list it under Needs customer approval. 2. Quotes. Do not write quotes. Under Quote placeholders, give three to five slots. Each slot names the topic. Where the notes contain the customer's exact words, show them in quotation marks and label them 'verbatim from notes, needs approval'. If the notes are only a paraphrase, write [Quote needed: topic] and nothing more. 3. Describe the problem from the customer's point of view, in their situation. Keep our role factual and modest. Make no claim that we are the best or the first. 4. If the permission status does not clearly allow naming the customer or publishing a result, write [Customer name pending] or leave the result out, and say so. 5. Mark any assumption you had to make with [ASSUMPTION: ...]. After the draft, add three lists: - Needs customer approval: every name, job title, figure, claim and quote in the draft that the customer must confirm. - Gaps: questions to ask the customer to fill missing detail. - Left out: anything in the notes you did not use, and why. Write in plain, short sentences. Avoid hype words.
Open in
Open in Claude (opens in a new tab)Open in ChatGPT (opens in a new tab)

Gemini cannot be filled from a link, so the prompt is copied first. Paste it with Ctrl+V or Cmd+V.

Use it as a skill

Add this playbook to your assistant once, then ask for it by name.

Download skill for ClaudeView SKILL.md (opens in a new tab)
How to install
  1. Claude: download the zip and upload it as is under Settings, Capabilities, Skills.
  2. Other assistants: open SKILL.md, copy it, and paste it into the assistant's custom instructions or project.
  3. Ask for the playbook by its task, and give it your details when it asks.

The skill is plain text with no scripts, links or commands. Read SKILL.md before you install it, and use a company-approved AI workspace. Need help setting it up? Book a call.

See a real result

Sample input: Sharma Textile Exports, Surat. Contact: Rakesh Sharma… · Rakesh agreed by phone on 6 Nov to be named and to share… · Family-run garment…

Sample output from Claude Sonnet 5.5, run 14 Nov 2026
Draft customer story

Headline Sharma Textile Exports now logs every buyer enquiry in one place

Summary Sharma Textile Exports, a family-run garment exporter in Surat, used to receive buyer enquiries across WhatsApp, email and calls. We set up a shared WhatsApp Business catalogue and an enquiry-tracking sheet, and every enquiry is now logged in one place.

The problem Sharma Textile Exports sells garments to buyers in the UAE and the UK. Those buyers wrote on WhatsApp, wrote by email and phoned.

Enquiries arrived through three channels, and staff kept separate lists. The team often lost track of them.

Rakesh Sharma, Managing Director, said the team was embarrassed when a Dubai buyer had to ask again.

What we did together We set up a shared WhatsApp Business catalogue for the sales support team. We also set up a simple enquiry-tracking sheet.

The team now logs every enquiry in that one sheet. [ASSUMPTION: the sales support team is the group that previously kept the separate lists and now uses the sheet.]

The result

  • Every buyer enquiry is now logged in one place.
  • First reply to new enquiries goes out within one working day.

Quote placeholders

  1. [Quote needed: how enquiries arrived by WhatsApp, email and calls, and how the team lost track]
  2. Topic: the Dubai buyer. "we were embarrassed when a Dubai buyer had to ask twice" (verbatim from notes, needs approval)
  3. [Quote needed: how the setup went for the team]
  4. [Quote needed: what changed now that every enquiry is logged in one place]
  5. [Quote needed: advice for other export business owners]

Permission note: Rakesh agreed by phone on 6 Nov to be named and to share the approved results, so the customer is named. Written approval of the final draft is still pending. Do not publish until it arrives.

Length note: The draft is well under 450 words. The notes do not support more without adding facts. The Gaps list shows what would fill it out.

Needs customer approval
  • Name: Sharma Textile Exports, Surat.
  • Name and job title: Rakesh Sharma, Managing Director.
  • Description: family-run garment exporter that sells to buyers in the UAE and the UK.
  • Results (approved 6 Nov, confirm again in the final draft):
    • Every buyer enquiry is logged in one place.
    • First reply to new enquiries goes out within one working day.
  • Claims from the interview:
    • Enquiries came in on WhatsApp, email and calls.
    • Staff kept separate lists.
    • The team often lost track of enquiries.
    • A Dubai buyer had to ask again, and the team was embarrassed. This incident has not been approved for publication.
  • Our work: the shared WhatsApp Business catalogue and the enquiry-tracking sheet, set up for the sales support team.
  • Quote: "we were embarrassed when a Dubai buyer had to ask twice" (verbatim from notes).
  • Figures in the notes that are not approved (kept out of the story):
    • about 60 staff
    • four weeks of setup, also described as about a month
    • two staff keeping separate lists
    • "twice" (appears only in the verbatim quote)
  • Final written approval of the whole draft.
Gaps
  • Who exactly kept the separate lists, and what were the problems with them?
  • What happened with the Dubai buyer, and is Rakesh happy for it to be mentioned, even without the buyer's name?
  • How does the team use the shared WhatsApp Business catalogue day to day? What is in it, and who uses it?
  • How is the sheet used? Who logs enquiries, and when?
  • What was the first-reply time before the change? Is Rakesh willing to share it?
  • Has anything else changed for buyers or the team? Can Rakesh give a specific example?
  • Can Rakesh provide the quotes for slots 1, 3, 4 and 5?
  • Is the "about 60 staff" figure, or the setup time, approved for use?
  • Are there any numbers on sales? Rakesh was not sure whether sales had grown.
Left out
  • Sales may have grown: Rakesh was unsure and it is not an approved result.
  • About 60 staff: a figure not on the approved list.
  • Four weeks and about a month: figures not on the approved list.
  • Two staff keeping separate lists: a figure not on the approved list. The story says only "staff kept separate lists".
  • "Twice": left out of the story text. It appears only in the verbatim quote slot.
  • Any claim about how the catalogue or sheet caused faster replies: the notes do not say this.

Was this playbook helpful?

Want this set up for your team?

I can fit this playbook into your CRM, helpdesk or inbox and train your team to use it.

Book a 30-minute review

Review before you send

Check the result

Watch out for

  • Invented numbers or quotes. models fill gaps if allowed. The prompt forbids it, but still check each figure and quote yourself before the draft leaves your team.

  • Filler claims. models add linking sentences that sound harmless, such as 'this gave the team a shared tool'. Each one is a claim about your work. Delete it or put it on the approval list.

  • Incidents from the notes. a moment the customer described, such as a buyer having to ask twice, is still their account. Keep it in a quote slot or on the approval list until they confirm it can be used.

  • Permission. a verbal yes is not the same as approval of the final text. Send the finished draft to the customer and wait for written approval before publishing.

  • Personal and customer data. interview notes can contain names, phone numbers and commercial details. Remove what the story does not need, use your company's approved AI workspace, and follow your data protection duties under India's DPDP Act or GDPR where they apply.

  • Over-claiming. a story can imply that your service caused a result the customer only partly credits to you. Keep the wording to what the customer said and approved.

  • Third parties. if the notes mention the customer's own buyers, staff or suppliers, leave them out unless they have agreed to be named.

Tips for your industry

This playbook works for any business. These notes help you adapt it.

Customer stories often rest on usage or time-saving figures. Use only figures the customer has agreed to share, and confirm which product features and plan they are describing.

Questions people ask

It should not. A quote is the customer's own statement, so the playbook leaves a placeholder or shows words taken exactly from your notes. The customer must confirm the wording before you use it.

Last checked · Updated