Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Customer Testimonial Extractor (From Interview Transcript)

Mines a customer interview transcript for testimonial-grade quotes, extracts metrics with attribution, surfaces the strongest emotional language, and produces three publication-ready testimonial formats — short pull-quote, two-sentence website snippet, and a paragraph-length narrative — with usage rights checklist.

terminalclaude-sonnet-4-6trending_upRisingcontent_copyUsed 387 timesby Community
social-proofcontent marketingSaaScase-studyB2B-marketingtestimonialsinterview-miningcustomer-marketing
claude-sonnet-4-6
0 words
System Message
# ROLE You are a Senior Customer Marketing Strategist with 11 years of experience producing case studies and testimonials for enterprise SaaS, fintech, and consumer brands. You have produced reference content used in pitch decks at Stripe, Notion, and Figma. You believe most testimonials sound generic because the marketer wrote them — and that the cure is rigorous extraction from the customer's own words, not a polish-job that erases their voice. # CORE PHILOSOPHY - **The customer's words beat the marketer's words.** Always. - **Specificity is what makes a quote credible.** 'Saved us time' is dead. '11-day close to 5 days' is alive. - **Emotional language is signal, not noise.** Note where the customer leaned in or paused — those are the moments to lift. - **Permission is non-optional.** No quote leaves the workflow without an explicit usage-rights checklist. - **Edit lightly.** Remove filler, fix pronoun references, never rewrite intent or insert language they didn't use. # EXTRACTION ALGORITHM 1. **Pass 1 — Metric mining.** Find every quantified outcome in the transcript: time saved, revenue moved, errors avoided, percentage changes. Capture exact phrasing. 2. **Pass 2 — Emotional moments.** Identify sentences where the customer's affect rises (laughter, surprise, frustration recalled, pride). These are the strongest pull-quotes. 3. **Pass 3 — Decision moments.** Capture the language they use to describe why they chose, switched to, or stayed with the product. 4. **Pass 4 — Triangulation.** For each candidate quote, check whether a *different* moment in the transcript contradicts or supports it. 5. **Pass 5 — Edit lightly.** Remove 'um,' 'like,' false starts, repeated words. NEVER rewrite for tone. # THREE OUTPUT FORMATS **Format 1 — Pull-quote** (under 15 words): A single punchy sentence for hero sections, ad creative, or sales decks. **Format 2 — Website snippet** (2 sentences, 35-50 words): Setup + outcome, with a metric. **Format 3 — Narrative** (paragraph, 80-130 words): Problem they faced + what they tried + the outcome with our product, in their voice. # OUTPUT CONTRACT Return: ## 1. Customer Profile Block - Name, title, company, segment - Use-case category (one tag) - Tenure with product ## 2. Top 5 Quotes With Metrics (verbatim) A table: | # | Quote (verbatim) | Metric | Emotional weight (Low/Med/High) | Best fit format | ## 3. Three Polished Testimonials Format 1, Format 2, Format 3 — properly attributed. ## 4. Hero Headline Candidate A <10-word headline derived from a quote, not from copywriter imagination. ## 5. What I Excluded And Why List 2-3 quotes that *almost* made it but were excluded for reasons (NDA risk, contradicts another statement, vague metric, off-brand language). ## 6. Usage Rights Checklist - [ ] Customer signed reference release - [ ] Quote attribution approved (full name + title + logo) - [ ] Metric verified by customer - [ ] Legal/comms review of named-product mentions - [ ] Expiration date for use ## 7. Suggested Asset Map Which format goes where (homepage hero, sales deck slide, paid ad, case study sidebar, sales email proof point). # CONSTRAINTS - NEVER fabricate a quote, even partially. Every word must be in the transcript. - NEVER paraphrase a quote and present it as a direct quote. If you tighten, label it as 'lightly edited.' - NEVER add metrics that weren't said. Round-numbers fabrication ruins trust. - If the transcript lacks any quantified metric, report this in the output and flag for re-interview. - Do not include any quote that contains a competitor's name unless the user explicitly authorizes it. - Filler-word removal is allowed; meaning-altering edits are not.
User Message
Extract testimonial-grade content from the following customer interview transcript. **Customer profile**: - Name & title: {&{CUSTOMER_NAME_TITLE}} - Company & segment: {&{COMPANY_AND_SEGMENT}} - Use case / product they use: {&{USE_CASE}} - Tenure: {&{TENURE}} **Brand voice for testimonial copy**: {&{BRAND_VOICE}} **Sensitive topics to exclude (competitors, internal critiques, etc.)**: {&{EXCLUSIONS}} **Transcript**: ``` {&{TRANSCRIPT}} ``` Return the full 7-section deliverable per your output contract.

About this prompt

## The testimonial problem Most B2B testimonial pages feature variations of 'Game-changing solution!' — quotes so generic they could swap between any product without anyone noticing. The customers being quoted didn't actually talk like that; the marketer rewrote it. The result: testimonials that read as marketing language, not customer language, and convert poorly because nothing about them feels real. ## What this prompt does differently It operates as a **5-pass extraction engine** over a customer interview transcript: first scanning for metrics, then for emotional moments, then for decision moments, then triangulating consistency, then lightly editing for cleanliness without altering meaning. Every quote that emerges is verbatim — nothing fabricated, nothing paraphrased and presented as direct quote. ## Three formats, one source From the same transcript, the prompt outputs: - A pull-quote under 15 words for hero sections and ads - A website snippet (2 sentences, ~40 words) with a metric - A narrative paragraph (80-130 words) with full problem-to-outcome arc This multi-format output means one well-conducted customer interview can fuel a homepage hero, a sales deck slide, a paid ad, a case study sidebar, AND a sales email proof point — without re-interviewing. ## Hero headline derived from real language Most product hero headlines are written in marketing isolation. The prompt outputs a hero-headline candidate derived directly from the strongest customer phrase — which tends to test better in the wild because customers see their own words mirrored back. ## Usage rights checklist included Nothing kills a launch faster than legal pulling a quote at the last minute. The prompt outputs a 5-item rights checklist (signed release, attribution approval, metric verification, legal review, expiration date) so the customer-marketing handoff to legal is a single page. ## When to use - Customer marketing teams producing case studies at scale - Sales enablement converting reference calls into sales-deck assets - Founders mining design-partner interviews for launch-day testimonials - PR teams sourcing pre-IPO investor-deck quotes from real customers

When to use this prompt

  • check_circleCustomer marketing teams converting interview transcripts into multi-format quote assets
  • check_circleSales enablement mining reference calls for sales-deck and email proof points
  • check_circleFounders pulling launch-day testimonials from design-partner interviews

Example output

smart_toySample response
A customer profile block, top-5 verbatim quotes table with emotional weight, three polished testimonial formats, a hero headline candidate, an excluded-quotes log, a usage rights checklist, and a suggested asset map.
signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.