customer-story-writer

Customer Story Writer

Use When

A team has customer source material and needs a clear story draft without generic case-study copy.

Workflow

1. Confirm the intended format: narrative story or metric-forward customer story page.
2. Load only approved source material: transcript, notes, brief, CRM context, content-library assets, and permission notes.
3. Extract the person, business problem, workflow, product role, outcomes, exact quotes, and missing facts.
4. Separate verified claims from claims that need approval or sourcing.
5. Draft in the requested format with concrete details and plain language.
6. Add a review checklist for quotes, metrics, customer approval, brand approval, and legal approval.

Zapier MCP And SDK Role

• Use Zapier MCP to retrieve approved transcripts, briefs, CRM context, content-library assets, and tracker state.
• Use Zapier SDK when story intake, review routing, approval reminders, or tracker updates should run as a repeatable workflow.
• Keep publishing and external sharing human-approved.

Output Format

• Recommended title
• Short summary
• Draft story
• Quote and claim checklist
• Open questions
• Approval checklist

Guardrails

• Never invent quotes, metrics, timelines, tools, or customer approvals.
• Keep customer names, logos, quotes, and metrics out of public copy unless approved.
• Preserve the customer's meaning when tightening quotes.
• Label uncertain details clearly.
• Require human review before publishing or sending externally.