Prompt Details
Model
(claude-4-6-sonnet)
Token size
1,369
Example input
[CASE_STUDY]: Case Study: How TechCo Transformed Their Customer Support with AcmePlatform. The Challenge: TechCo, a fast-growing SaaS company, was facing the challenges that many companies face today. Their support team was struggling to keep up with rising ticket volume, and customer satisfaction was suffering. Like many growing companies, TechCo knew they needed a change. The Solution: That's when they discovered AcmePlatform. With our cutting-edge AI-powered ticket routing and automated response suggestions, TechCo was able to streamline their support operations. The Results: The results speak for themselves. After implementing AcmePlatform, TechCo saw significant improvements across the board, and their team handled more tickets in less time. "AcmePlatform has been a game-changer for our team," said Sarah Chen, VP of Customer Support at TechCo. "We couldn't be happier with the results." Today, TechCo is well-positioned to scale as they continue to grow.
Example output
TechCo Cut Average Ticket Resolution Time From 14 Hours to 3.5 in 4 Months Using AcmePlatform
TechCo (a SaaS company with ~200 employees) reduced average customer support ticket resolution time from 14 hours to 3.5 hours over four months, while ticket volume rose 35%. CSAT moved from 6.8 to 8.4 on a 10-point scale.
Before AcmePlatform, the support team of 12 was triaging tickets manually [SPECIFICS NEEDED: what was the manual triage process, and what was the headcount cost trajectory if volume kept rising?].
The team deployed AcmePlatform's ticket routing (configured against their existing 7 ticket categories) and automated response suggestions for the top-10 most common ticket types. [SPECIFICS NEEDED: deployment timeline — was this a 1-week, 1-month, or 3-month rollout, and what did the team build versus configure?]
"[REPLACE WITH SUBSTANTIVE QUOTE]" — Sarah Chen, VP of Customer Support, TechCo. The current quote ("game-changer," "couldn't be happier") carries no information; ask Sarah for a specific quote naming what is different about her week now versus before.
---
Changes:
- Rewrote the headline to lead with the specific outcome (14 → 3.5 hours in 4 months) instead of "How TechCo Transformed"
- Deleted the "Challenge / Solution / Results" labels (they added nothing beyond the prose)
- Cut "facing the challenges that many companies face today" and "Like many growing companies" (generic framing)
- Cut "cutting-edge AI-powered," "streamline," and "empower their team to deliver better customer experiences" (slop with no specifics)
- Cut "results speak for themselves," "significant improvements across the board," and "skyrocketed" (vague outcome language)
- Flagged the Sarah Chen quote for replacement (generic warmth, no information)
- Deleted the "well-positioned to scale" closer (filler)
- Pulled the available metrics into the lede (200-employee company, team of 12, 35% volume rise)
Substantive content verdict:
- Specific numbers, dates, and a clear before-after delta? Partial
- Missing for credibility: the manual triage process, the deployment timeline, a substantive Sarah Chen quote, and whether any other features (for example, a knowledge-base integration) were used
Word count before → after: 175 → 150
AI/template signal estimate before → after: high → low
Instant access
Commercial use
Money‑backBy purchasing this prompt, you agree to our terms of service
1
Views
CLAUDE-4-6-SONNET
Strips the scaffolding out of a customer case study so the real result leads. Rewrites the "How X Used Y" headline to lead with the specific outcome, deletes the "Challenge / Solution / Results" labels and corporate-warmth filler, and flags generic quotes and vague metrics. Preserves every number, date, name, feature, and verbatim quote. Returns the edited case study, a change list, and a verdict on whether it has enough specifics to be credible. Personal and commercial use permitted.
...more
Added 1 week ago
