---
name: capture-client-stories-on-phone
description: "Film a client’s own story with clear permission. Save the facts, name, photo, and source files."
category: Content Factory — Produce
stage: Produce
definitive_article: GAP — to be written
status: needs-work
---

# Capture client stories on phone

A happy client can explain your work in their own words. This guide helps you save that story with their name and clear permission. First, ask what changed and where they are happy for the story to appear.

**The path:** Permission → Client’s own story → Facts and files → Review.

**Use this when:** A real client has a specific result and agrees to tell the story on camera.

## Inputs
- A real client, a specific project or change, and evidence for any stated numbers.
- Permission to record and a separate clear record of allowed use of the person’s name, face, words, and company or location. Capture limits and the date.
- A phone, a quiet location, and permission to film the location and supporting shots.
- The approved raw folder, upload access, tracker, and named reviewer who will check facts and permission.

## First-run prompt

> Help me capture a client story from the facts and permission I provide. Draft plain interview questions, an attribution line, and a shot list. Flag claims that lack proof and uses that are not agreed. After capture, check the file package and prepare a factual handoff for review.

## Steps
1. Ask what may be recorded and where it may be used. Explain the intended article or channel. Record the answer in the project’s permission log; do not infer public use from a person agreeing to a private call.
2. Check the person’s full name and the right role, company, or city for the story. For a homeowner, do not invent a job title or company. Let the person confirm the attribution line.
3. Frame the person at eye level in a real setting. Check light, framing, and microphone. Keep private papers, addresses, or other people out of the shot unless cleared.
4. Ask four plain questions: What was the problem? What work was done? What changed? Who would this help? Let the client answer in their own words. Follow up on vague praise with “What is one example?”
5. When the client gives a number, note its source and what period it covers. If it cannot be checked, keep it as a claim for review or omit it from the finished piece. Do not turn a guess into a proven result.
6. Ask the client to confirm their name and attribution on camera when practical. Capture a still photo and about 30–60 seconds of supporting footage, called b-roll, such as the finished work. If consent or the setting prevents a shot, record that gap.
7. Name the video, photo, and supporting footage YYYY-MM-DD-clientname-story with a type or take suffix. Upload to the approved folder and log the links, permission, attribution, result evidence, and reviewer.
8. Send the raw package for review through [Upload the source to Drive and Descript](https://local-service-spotlight.github.io/task-library/?task=step-1-upload-video-to-google-drive-and-descript#task-step-1-upload-video-to-google-drive-and-descript). A missing name, usage permission, or unverified claim stays clearly flagged before any public use.

## Definition of done (QA checklist)

- [ ] The story describes a specific real change in the client’s own words.
- [ ] Full attribution fits the person and is confirmed; permission covers the proposed use.
- [ ] Claims have evidence or are marked unverified. A named quote alone does not prove a number.
- [ ] Video, a still image, and supporting footage are saved, or the exact capture gap is recorded.
- [ ] The reviewer can open the files and see all privacy or publication limits.

## Example(s)

**Fictional teaching example — invented people and shop, not a testimonial to publish.** Morgan, a made-up customer of Maple Cycle, says: “I did not know if the bike was worth fixing. They gave me a written quote before doing the work, so I could choose.”

The teaching attribution is “Morgan Lane, local customer.” The sample story makes no sales or safety claim. Its evidence would be the approved quote and the customer’s confirmation. A shot of the quote would hide contact details and the home address.

The teaching permission note says “website story and shop social posts; no paid ads agreed.” That means an editor could prepare those drafts after a real consent check, but an ad would need its own authority and usage check. Do not copy this invented quote into a real client page.

## Handoff and Content Factory context

The editor receives the files and permission limits. The reviewer uses [Verify testimonials with full attribution](https://local-service-spotlight.github.io/task-library/?task=verify-testimonials-with-full-attribution#task-verify-testimonials-with-full-attribution) before public use. [Upload the source to Drive and Descript](https://local-service-spotlight.github.io/task-library/?task=step-1-upload-video-to-google-drive-and-descript#task-step-1-upload-video-to-google-drive-and-descript) is the source-file handoff; a story is not automatically cleared for ads.

This task serves **Produce** in the [Content Factory](https://blitzmetrics.com/content-factory/). Produce makes or prepares source material. Process edits it, Post puts approved work on a channel, and Promote helps it reach people. Only the steps and handoff above are part of this task.

## When this runs

Run for each willing client story when a real result exists. This task sets no automatic outreach or recurring filming schedule.

## Run with an agent

The agent can prepare the plan, organize allowed files, and check the evidence it can actually access. A person records real stories, supplies permission, or resolves an account step when needed. Save the current state in the project files and tracker. A model name does not create memory, access, a scheduler, or permission to act.

For all agent media checks, keep the player muted and its volume at zero before playback. If that cannot be checked, use captions, metadata, or still frames. Do not claim sound quality was heard when it was not.

## Write up the real run

For every actual attempt, [write the run’s meta article](https://blitzmetrics.com/meta-article-prompt/). Link this exact task and its source revision. State the start, work done, evidence, result, gaps, and next owner. Keep failed, partial, and blocked work visible. Writing the record does not authorize publishing it.

Use one stable execution ID for this task’s actual run. Internal retries, checks, and new versions do not add runs. A separately scoped child task may have its own ID linked to the parent. A teaching example has no real execution ID and must not enter the run count. Follow the [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) for that distinction.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** Produce
- **Importance:** 4/5 `●●●●○` — frequency 4, revenue 3, gating 2 (runs every factory cycle or weekly)
- **Suggested previous station:** `record-one-minute-videos`
- **Suggested next station:** `film-conference-presentations`
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Raw files in Content Library `01-Raw/` plus a tracker row (question, date, speaker). Next skill never needs the chat — it needs the files.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- Dedicated canonical article: not mapped in the current task source. Use the owned teaching references below while that article gap is reviewed.
- Exact task: [Capture client stories on phone](https://local-service-spotlight.github.io/task-library/?task=capture-client-stories-on-phone#task-capture-client-stories-on-phone)
- Publishing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [One-minute video method](https://blitzmetrics.com/one-minute-video-guide/)

## Review and evidence still needed

The contributor status in the source header is preserved. It is not a claim that this draft has been independently accepted or that a real run has passed. The worked example above is for teaching only.
- No dedicated canonical story-capture article is mapped in the source.
- Actual consent, identity and outcome evidence can only come from a real capture.