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.
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.
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. Gather your inputsHave the items above to hand.
- 2. Fill in the formYour prompt updates as you type.
- 3. Copy or open in your AIClaude, ChatGPT or Gemini.
- 4. Review before you sendCheck it against your notes.
Your prompt · 0 of 7 filled
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.
How to install
- Claude: download the zip and upload it as is under Settings, Capabilities, Skills.
- Other assistants: open SKILL.md, copy it, and paste it into the assistant's custom instructions or project.
- 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…
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
- [Quote needed: how enquiries arrived by WhatsApp, email and calls, and how the team lost track]
- Topic: the Dubai buyer. "we were embarrassed when a Dubai buyer had to ask twice" (verbatim from notes, needs approval)
- [Quote needed: how the setup went for the team]
- [Quote needed: what changed now that every enquiry is logged in one place]
- [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.
- 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.
- 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.
Draft for review. Rakesh has agreed to be named and to share the approved results. Written approval of the final draft is still pending.
HeadlineSharma Textile Exports brings buyer enquiries into a shared tracking sheet
SummarySharma Textile Exports, a family-run garment exporter in Surat selling to buyers in the UAE and the UK, needed a shared way to track buyer enquiries. We set up a shared WhatsApp Business catalogue and a simple enquiry-tracking sheet for its sales support team.
The problemBuyer enquiries reached Sharma Textile Exports through WhatsApp, email and calls. Rakesh Sharma said the team often lost track of them. Staff kept separate lists rather than using a shared record.
For Rakesh, the problem was not just how the team organised its records. It also showed up in conversations with buyers. He recalled feeling embarrassed when a Dubai buyer had to ask again.
The situation involved both incoming enquiries and the lists used to track them. Buyers contacted the business through different channels, while staff maintained separate records. The team needed a way to keep track of those enquiries together.
What we did togetherWe set up a shared WhatsApp Business catalogue and a simple enquiry-tracking sheet for the sales support team.
The work focused on these practical tools. The catalogue provided a shared WhatsApp Business resource. The sheet gave the team a shared place to record buyer enquiries, rather than continuing with separate lists.
The team now logs every enquiry in the shared sheet. This is the change Rakesh described in how the team keeps track of incoming buyer requests.
Our role was to set up the catalogue and tracking sheet. The results below describe enquiry handling; they do not establish whether the work increased sales.
The resultRakesh approved these results for publication:
Every buyer enquiry is now logged in one place.
First reply to new enquiries goes out within one working day.
These results address the enquiry-tracking problem Rakesh described. The business now has a shared record of incoming buyer enquiries, and a stated timeframe for the first reply.
For export business owners considering similar help, this story concerns a specific part of sales support: recording buyer enquiries and replying to them. It does not claim a wider commercial outcome.
Quote placeholders- Buyer follow-up: “we were embarrassed when a Dubai buyer had to ask twice” — verbatim from notes, needs approval.
- [Quote needed: keeping track of enquiries across WhatsApp, email and calls]
- [Quote needed: using the shared enquiry-tracking sheet]
- [Quote needed: replying to new buyer enquiries]
- Final draft: Written approval is still pending.
- Names: Sharma Textile Exports and Rakesh Sharma. Naming permission was given by phone; confirm their use in the final draft.
- Customer description: Surat location, family-run garment exporter, and sales to buyers in the UAE and the UK.
- Problem claims: Enquiries arrived through WhatsApp, email and calls; the team often lost track; staff kept separate lists; a Dubai buyer had to ask again; Rakesh felt embarrassed.
- Work described: We set up the shared WhatsApp Business catalogue and simple enquiry-tracking sheet for the sales support team.
- Current practice: The team now logs every enquiry in the shared sheet.
- Results and their figures: “Every buyer enquiry is now logged in one place” and “First reply to new enquiries goes out within one working day” were already approved on 6 Nov. Preserve that wording in the final draft.
- Quote: Approve the exact words shown in the buyer follow-up slot. Supply and approve wording for the remaining slots.
- Figures withheld from the story: About 60 staff; two staff keeping separate lists; setup over four weeks, also described as about a month. These need approval before inclusion.
- Date withheld from the story: 6 Nov, covering the phone permission and results approval. It is used here only as an approval-status record.
- Who is responsible for logging enquiries and checking that they receive a reply?
- How does the sales support team use the catalogue?
- What information does the tracking sheet capture?
- How is the first-reply timeframe checked?
- Can Rakesh provide an approved example of how enquiry handling has changed?
- Is there evidence of sales growth? If not, keep sales outcomes out.
- Will Rakesh approve the final draft and the proposed quotations in writing?
- About 60 staff: Not an approved publication figure.
- Two staff maintaining separate lists: The separate-list problem is included, but the unapproved count is omitted.
- Four weeks / about a month: Setup duration is not an approved publication figure.
- Possible sales growth: Rakesh was unsure. No sales-growth claim is made.
- Managing Director: The supplied job title is not needed in this draft.
- 6 Nov: Permission and approval dates are kept outside the customer story.
- The Dubai remark as a published testimonial: It appears only as a quote placeholder awaiting approval.
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 reviewReview before you send
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.
Client confidentiality is often tight. Expect to anonymise the client, and check that the problem description does not identify them by detail.
Stories involve process changes, buyers and sometimes contract terms. Confirm with the customer which plant, product line or buyer details can be shared.
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.
Run the prompt with the approved results field marked 'none yet'. The result section should then describe the outcome in plain words without figures, and any figures from the notes should appear on the approval list. Check that none slipped into the story.
Only if your company's rules allow it for this kind of material. Where possible, use a business workspace where your data is not used for training, and remove personal details the story does not need.
Yes. Write 'anonymous' in the permission status and describe the customer in general terms, such as a Surat garment exporter. Check that no detail in the draft makes them easy to identify.
Last checked · Updated