---
name: run-thank-you-machine-for-every-interaction
description: "Let people know how their help mattered."
category: Personal Branding
stage: Promote
definitive_article: /thank-you-machine
status: complete
---

# Run Thank You Machine for every interaction

Let people know how their help mattered. This guide turns a real act of help into a specific thank-you in the right place. Start with what the person did and whether the story is safe to share.

**The path:** Real helpful act → Specific thanks → Right private/public route → Checked follow-through

**Start when:** A genuine referral, review, introduction, advice or useful act deserves acknowledgment.

## Inputs

- The actual event or interaction, identity and source facts, without unnecessary private details.
- The relationship context, public-use permission and preferred acknowledgment route.
- Recording or writing tools and actual send, release or spend authority where relevant.

## Steps

1. Read the real interaction and name what deserves thanks. Record the person, act and why it mattered. A routine automated event or inferred relationship is not a reason to fabricate gratitude; make the acknowledgment specific enough to be true.
2. Choose the appropriate route for the person and situation. Some thanks belong in a private note; others may become public content with the right permission. An interaction does not automatically consent to a public story, tag, testimonial or ad.
3. Prepare a short unscripted video or a clear note naming the person, what they did and its real effect. Preserve the speaker’s voice and an authentic human detail. Do not inflate a favor into an endorsement, measured result or durable partnership.
4. If content reuse fits the agreed scope, use [Content Factory: Produce, Process, Post and Promote](https://blitzmetrics.com/content-factory/) to make only the useful approved outputs. Keep the core story and proof intact. A video does not require a blog, testimonial, email and ad in every case, especially when the source is private.
5. Publish or send through the existing authority and correct destination. Verify any social tag identifies the right person and record the actual delivered/live state. A tag does not guarantee that they see or share the post.
6. Consider [Dollar a Day, small paid tests of proven content](https://blitzmetrics.com/dollar-a-day/) only for an appropriate public asset with useful organic evidence, use rights, tracking and a separately approved test budget. Gratitude does not require paid amplification, and a nominal daily budget is not a guarantee of outcome or zero risk.
7. Add an appropriate thank-you check to the existing post-project process and retain the event, draft, release and response. A weekly review may be useful when assigned; an installed skill does not create a schedule. Learn from actual responses without measuring success by forced public posts.

## 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/).

- [ ] The acknowledgment names a real person, helpful act and supported reason it mattered.
- [ ] Private/public use, tags, sends and any paid distribution follow the actual agreed scope.
- [ ] The record distinguishes draft, released, seen and responded states; no reaction is invented.
- [ ] 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 owner receives a private referral from a client. The client prefers to stay unnamed, so the owner prepares a specific private thank-you. No public clip, tag or ad is made. The task still has a useful result: the right person receives genuine thanks through the permitted route, with the actual send recorded.

## Handoff and Content Factory context

The existing relationship owner retains follow-through. [Collect and classify positive mentions](https://local-service-spotlight.github.io/task-library/?task=positive-mentions-harvester#task-positive-mentions-harvester) receives only separately supported public praise; Process or Promote receives optional reuse with its actual rights and authority.

The source places this task in Promote 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:** Promote
- **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:** Organic metrics CSV (or Ads Manager export), pixel ID, creative filenames, kill/scale log. Next week's ranking starts from this file.

## Model routing (same factory, any engine)

- **This task's lane:** `computer` — Logged-in UI (Meta Ads Manager, Descript, GSC, wp-admin when REST is blocked). Requires a supported browser tool and the right account access.
- **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

- [Current mismatched route: opens Face Socks; generic method source pending reconciliation](https://blitzmetrics.com/thank-you-machine/)
- [This task in the Task Library](https://local-service-spotlight.github.io/task-library/?task=run-thank-you-machine-for-every-interaction#task-run-thank-you-machine-for-every-interaction)
- [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/)

### Primary method references

- [Current mismatched Thank You Machine route: opens Face Socks; pending source reconciliation](https://blitzmetrics.com/thank-you-machine/)

## Review and evidence still needed

The inherited contributor status is `complete`. 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.