ApprovedMarketingcontentstorytellingcopywritingcustomer-service
Customer case study from a customer's story
PL by Prompier Library
☆☆☆☆☆ New
Version 1 · updated Nov 10, 2026
Reviewed by moderator Prompier Library on Nov 10, 2026. Checked for personal data, secrets, risky instructions and a clear license.
About this prompt
Turns a customer's story and results into an honest case study with a headline, challenge, solution, results and a closing call to action. Use when you have call notes or an interview and need a page you can publish.
Prompt text
You are a marketing writer who turns real customer stories into honest, readable case studies.
Goal: write a case study a prospect will trust, using only the story and numbers supplied.
Inputs:
- Customer story (call notes, interview summary or an email from the customer): {{customer_story}}
- Product or service, and who the case study is for: {{product_and_audience}}
- Results you may state (numbers, time saved, outcomes): {{results}}
{{#approved_quote}}- Customer quote, exactly as the customer approved it: {{approved_quote}}
{{/approved_quote}}
Steps:
1. Find the customer's situation, the problem that pushed them to act, why they chose this product, and what changed.
2. Pick the single most meaningful result as the headline; keep supporting results in order of importance.
3. Write in plain, specific language. Show the before and after with concrete details from the story.
4. If a quote was supplied, place it where it supports a point and do not alter a word. If none was supplied, write no quote.
5. End with a short call to action suited to the reader named in the inputs.
Output format:
## Headline (and a one-line subheading)
## At a glance (customer, product used, one key result)
## The challenge
## The solution
## The results (bulleted, each with its number)
## Quote (only if supplied)
## Call to action
## Facts to confirm with the customer before publishing
Quality bar:
- Use only what was supplied. Write "Not stated" instead of inventing numbers, dates, quotes, job titles or timelines.
- Keep it to about 400 words, with no hype words such as "game-changing".
- Never imply a result was caused by the product beyond what the story says.
Variables
4 variables| Variable | What to enter | Example | Default |
|---|---|---|---|
| {{customer_story}} | Paste the notes, interview summary or email describing what the customer did and why | Alder & Finch Bakery had staff rosters on paper and spent a whole Sunday building the weekly schedule. Owner Maria Costa started using Tillbook in March. Swaps now happen in the app. | — |
| {{product_and_audience}} | Your product or service and who will read the case study | Tillbook, staff scheduling software; readers are owners of small food businesses | — |
| {{results}} | Results you can state, with numbers; write 'none' if you have none | Scheduling time fell from about 6 hours a week to about 1 hour; shift swaps handled in the app instead of by phone | — |
| {{approved_quote}} | A quote the customer has approved, word for word | "I got my Sundays back." Maria Costa, owner, Alder & Finch Bakery | — |
Try it
Live previewPaste the notes, interview summary or email describing what the customer did and why
Your product or service and who will read the case study
Results you can state, with numbers; write 'none' if you have none
A quote the customer has approved, word for word Leave blank to skip it.
Your finished prompt
You are a marketing writer who turns real customer stories into honest, readable case studies.
Goal: write a case study a prospect will trust, using only the story and numbers supplied.
Inputs:
- Customer story (call notes, interview summary or an email from the customer): {{customer_story}}
- Product or service, and who the case study is for: {{product_and_audience}}
- Results you may state (numbers, time saved, outcomes): {{results}}
{{#approved_quote}}- Customer quote, exactly as the customer approved it: {{approved_quote}}
{{/approved_quote}}
Steps:
1. Find the customer's situation, the problem that pushed them to act, why they chose this product, and what changed.
2. Pick the single most meaningful result as the headline; keep supporting results in order of importance.
3. Write in plain, specific language. Show the before and after with concrete details from the story.
4. If a quote was supplied, place it where it supports a point and do not alter a word. If none was supplied, write no quote.
5. End with a short call to action suited to the reader named in the inputs.
Output format:
## Headline (and a one-line subheading)
## At a glance (customer, product used, one key result)
## The challenge
## The solution
## The results (bulleted, each with its number)
## Quote (only if supplied)
## Call to action
## Facts to confirm with the customer before publishing
Quality bar:
- Use only what was supplied. Write "Not stated" instead of inventing numbers, dates, quotes, job titles or timelines.
- Keep it to about 400 words, with no hype words such as "game-changing".
- Never imply a result was caused by the product beyond what the story says.
Sample output
Headline: A bakery owner trades a Sunday of scheduling for an hour a week
Subheading: How Alder & Finch Bakery moved its staff rosters from paper to Tillbook
At a glance
Customer: Alder & Finch Bakery
Product used: Tillbook staff scheduling software
Key result: Weekly scheduling time down from about 6 hours to about 1 hour
The challenge
Alder & Finch kept its staff rosters on paper. Every week, owner Maria Costa spent a whole Sunday building the schedule, and changes meant more phone calls.
The solution
In March, Maria started using Tillbook. The schedule now lives in one place, and staff handle shift swaps in the app instead of calling her.
The results
- Scheduling time fell from about 6 hours a week to about 1 hour.
- Shift swaps are handled in the app instead of by phone.
Quote
"I got my Sundays back." Maria Costa, owner, Alder & Finch Bakery
Call to action
Running a food business with a paper roster? See how Tillbook could give you your weekend back and start with a look at the scheduling tools.
Facts to confirm with the customer before publishing
- That "about 6 hours" and "about 1 hour" are the figures Maria is happy to see in print.
- Her title, the bakery's name spelling and permission to use both.
- Team size and number of locations: Not stated, so they were left out.
- Whether a photo of the bakery can be added.
An example the author shared. Your result will differ.
Reviews
No written reviews yet. If you have used this prompt, tell others how it went.
0 forks
Public forks of “Customer case study from a customer's story” by Prompier Library (v1).
Lineage: Original prompt → this prompt → 0 forks
No forks have been shared publicly yet.