---
name: record-one-minute-videos-answering-customer-questions
description: "Film one short clip to help your clients."
category: Personal Branding
stage: Produce
definitive_article: /personal-brand
status: needs-work
---

# Record one-minute videos answering customer questions

Film one short clip to help your clients. This guide helps you give clear answers in your own words. Start with a real question and a true story that helps explain your point.

**The path:** Real question → Clear answer → Saved take → Checked source handoff

**Start when:** The person has real knowledge to share and the content plan needs new source recordings.

## Inputs

- Actual customer questions from permitted calls, notes or messages, with private details removed.
- The person’s relevant experience, source facts, phone or camera and consent for the recording.
- [Topic Wheel, the map of your offer, topics and real stories](https://blitzmetrics.com/topic-wheel/) coverage plan and an accessible content-library destination with a receiving editor.

## Steps

1. Collect real questions and record their context without exposing private messages or client data. Choose the question because it serves an actual customer need. A proposed AI topic is a suggestion, not evidence that customers asked it.
2. Use the Topic Wheel correctly: WHAT offer at the center, HOW teaching topics in the middle and WHY people/stories outside. Map the selected question to its useful topic; not every short recording has to cover all three parts of the wheel.
3. Prepare a brief prompt and source reminders instead of a fabricated first-person script. Follow the [one-minute video method](https://blitzmetrics.com/one-minute-video-guide/): lead with the point, give a useful answer or true example, and end with an appropriate next step. About a minute is the target, not a reason to cut away needed meaning.
4. Check light, stable framing and the intended microphone before the session. The person records their own answer. During agent QA, keep any playback muted at zero volume; use waveform, captions, transcript or a separate authorized human listening check for sound quality.
5. Record one complete idea per take. Redo a factual mistake or unusable take rather than patching together a misleading quote. A batch can be useful, but its size comes from the real questions and available time, not a forced count of videos.
6. Name and save each real file with question, speaker, date and take identifier in the accepted library. Record rights, source facts, rough transcript and selected/rejected state. Verify that the editor can read the actual file; a pasted inaccessible link is an incomplete handoff.
7. Pass selected takes with exact timestamps and any remaining sound or fact checks to the editor. Keep planned, recorded, usable and published states distinct. The recording itself does not prove later captions, posts or business results.

## Definition of done (QA checklist)

Quality assurance (QA) means checking the actual result against its agreed requirements. Follow the [Article Guidelines](https://localservicespotlight.com/article-guidelines/).

- [ ] Each selected take answers a real scoped question with the speaker’s own supported knowledge.
- [ ] Files, rights, identities and actual usability checks are saved in the accepted library.
- [ ] The editor can access the selected source and sees any still-unverified audio or factual issue.
- [ ] The exact output, source revision, reviewer evidence and remaining owner action are saved.
- [ ] For any reader-facing output, the short grade-five opening states the reader’s useful outcome and supporting method or proof. The body delivers that promise; a useful authentic visual appears in the first screen. Retain exact text and quoted reviewer evidence.

## Example(s)

**Fictional teaching example. This is not a client result or proof of a completed run.**

A fictional electrician records an answer about a tripping breaker. The first take omits an important safety limit, so she records a clearer second take. The library keeps both files but marks only the second selected. The editor receives the actual answer and its context, with any unheard audio check still assigned.

## Handoff and Content Factory context

[Turn the source into an article](https://local-service-spotlight.github.io/task-library/?task=repurpose-videos-into-blog-posts-via-content-factory#task-repurpose-videos-into-blog-posts-via-content-factory) and [Prepare social clips](https://local-service-spotlight.github.io/task-library/?task=create-social-content-from-video-clips#task-create-social-content-from-video-clips) receive the selected source files and their actual acceptance checks.

The source places this task in Produce within the [Content Factory: Produce, Process, Post and Promote](https://blitzmetrics.com/content-factory/). Produce captures real sources, Process makes the selected useful assets, Post releases approved work, and Promote distributes proven work. The actual handoff above determines what this task must supply.

## Start with an agent

Give the [AI worker](https://blitzmetrics.com/build-agents/) this recipe, the real inputs, desired result and actions already authorized. Ask for the saved output, sources, checks and next owner. A [skill is a written recipe](https://localservicespotlight.com/plugin/); loading one does not prove account access or perform the task. Use the [installation guide](https://localservicespotlight.com/install/) if reusable setup is needed. A ZIP is a source snapshot, not an access grant or automatic update.

Use the app’s actual supported tools and verified file/account access. Keep a missing human verification step with its real owner. Recurring work needs its own configured job, trigger, timezone and observed result; this guide creates no schedule. Before any media playback, mute the player and set its volume to zero. If silence cannot be verified first, use captions, frames, metadata or another silent check.

## Record the real execution

Open the run record when work begins. Keep one execution ID, starting recipe revision, real inputs and current state. Write the [meta article, the record of this execution](https://blitzmetrics.com/meta-article-prompt/) with actual steps, results, checks, failures and next owner. Writing is required; public release follows existing authority. Link it to this recipe and the [Task Library](https://local-service-spotlight.github.io/task-library/).

Reuse the same execution ID for internal checks, revisions, retries and meta writing. A blocked run stays open with its dependency and owner, without an invented finish time. Dated public examples and distinct verified execution counts remain separate. Propose the smallest source-backed recipe improvement when the actual evidence reveals a defect.


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

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

- **Phase:** Produce
- **Importance:** 3/5 `●●●○○` — frequency 3, revenue 3, gating 2 (supporting)
- **Suggested previous station:** —
- **Suggested next station:** —
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

- [Maintained source guide](https://blitzmetrics.com/personal-brand/)
- [This task in the Task Library](https://local-service-spotlight.github.io/task-library/?task=record-one-minute-videos-answering-customer-questions#task-record-one-minute-videos-answering-customer-questions)
- [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Definitive article and task recipe standard](https://blitzmetrics.com/definitive-article-guide/)
- [How recipes and run records fit together](https://localservicespotlight.com/meta-articles/)

## Review and evidence still needed

The inherited contributor status is `needs-work`. It is preserved, not promoted by this rewrite. That label alone does not prove document readiness, account access, an actual execution or a client result.

The fictional example teaches the method and does not fill a real-run evidence gap. A named semantic reviewer must check the actual opening, full method, sources and handoff. Check the useful opening visual in the normal rendered guide at the current required desktop and mobile sizes, including 1280 × 800 and 390 × 844. Source readability checks do not prove public presentation or task execution.