---
name: tag-the-person-on-social-media
description: "Tag the right person in a thank-you post. Use this when the post is ready to share."
category: Thank You Machine
stage: Post
definitive_article: /thank-you-machine
status: complete
---

# Tag the Right Person in a Thank-You Post

A tag can help the right person find your thank-you post. This guide helps your team avoid tagging the wrong person or sharing a private story. Start with a checked post. Finish with the right tag and proof of the post’s state.

**The path:** Checked public post → confirm profile → check the saved post.

**Use this when:** public posting is within scope and naming or tagging the person is appropriate for this story.

## Inputs

- The checked media, caption and source note.
- The authorized account, intended channel and verified profile for the person.
- The person’s stated preferences and any limits on public sharing.

## First-run prompt

> Check this thank-you post and the person’s profile. Add the correct tag if the story can be shared. Carry out the already authorized posting step, then check the saved post. If posting is not in scope, save the exact draft and missing decision.

## Steps

1. Confirm that the content is intended for public use. Remove private details and respect a request not to be named or tagged; omit a tag if no suitable profile is confirmed.
2. Open the profile from a known link or verify its name, photo and relevant role against the project source. Do not select a similar name from search without evidence.
3. Use the platform’s actual tag or mention control on the intended posting account. A typed name is not proof that a clickable tag exists.
4. Read the full caption with the tag. Keep the thank-you specific and free of sales pressure. Do not promise that tagging will notify everyone, force a reshare or reach the person’s audience.
5. Preview the correct media and captions. Check that the tag does not cover a face or important text and that the destination account is the intended one.
6. Publish when already authorized. Otherwise save the concrete draft and the one decision needed. Never label a draft as posted.
7. For a posted item, reopen its normal permalink from the correct account. Check the visible media, caption and profile destination. Save the permalink, time and actual state; a platform’s notification delivery may remain unknown.

## Definition of done (QA checklist)

- [ ] Public sharing and the correct posting account are established.
- [ ] The person’s profile and tag destination are verified or the tag is deliberately omitted.
- [ ] The caption keeps the real meaning and excludes private facts.
- [ ] The exact saved post or draft is checked.
- [ ] No reshare, endorsement, audience reach or notification delivery is inferred from a tag.

## Example(s)

**Fictional teaching example — no client result or completed run.** Two profiles share Jordan’s name. The project’s known profile link resolves the right account. The owner authorizes the post, which is then reopened and checked. The record says “posted,” with no claim that Jordan saw or shared it.

## Handoff and Content Factory context

Save the checked permalink in the gratitude log. If a paid test is useful and authorized, hand the actual post and goal to [Test a Thank-You Post With a Small Ad](https://local-service-spotlight.github.io/task-library/?task=boost-with-dollar-a-day#task-boost-with-dollar-a-day). Otherwise the posted or private result is enough.

This fits the [Content Factory](https://blitzmetrics.com/content-factory/): Produce a true story, Process it into useful files, Post only in the agreed places, and Promote a suitable post when its test has a budget. Each stage passes its checked files and next owner forward.

## When this runs

Run for each intended public thank-you post. Do not repeatedly tag the same event to force attention.

## First-run setup and continuity

Use the files and accounts this task actually needs. A skill is a written recipe; the [AI worker](https://blitzmetrics.com/build-agents/) needs suitable tools and access to follow it. This file does not install an app, connect an account or start a timer. Follow the [setup guide](https://localservicespotlight.com/install/) for the chosen app. Carry out work already covered by the user's instructions; ask only for an exact missing item or a new action outside that scope.

Save the source, current state, checked result and next owner in the project files. Check that record before retrying or handing work to another person. Configure a repeat only when requested, with its time zone, actual runtime and first successful firing. An app or model name does not prove persistence, memory or a schedule.

Keep every agent media check muted with volume zero before playback. If that cannot be verified, use captions, metadata or still frames and record the limit. Do not play sound through the user's speakers without their current request.

## Write up the real run

For each real attempt, [write the meta article](https://blitzmetrics.com/meta-article-prompt/): its task and source revision, starting point, work done, evidence, measured result, gaps and next handoff. Save one execution ID across retries and edits. Partial, blocked and failed work also gets a record. A saved draft satisfies writing while any public release is pending. Writing does not grant publication authority.

A teaching example is not a real execution. Do not count it, a repeated check or a revision as another run. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains the link between reusable instructions and actual work.


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

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

- **Phase:** Post
- **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:** Draft URL or WP post ID, slug, author user ID, featured-image media ID. Promote reads the live URL, not the draft.

## 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

- Exact task: [Tag the Right Person in a Thank-You Post](https://local-service-spotlight.github.io/task-library/?task=tag-the-person-on-social-media#task-tag-the-person-on-social-media)
- [One-minute video guide](https://blitzmetrics.com/one-minute-video-guide/) — how to record one clear point.
- [Content Factory](https://blitzmetrics.com/content-factory/) — how the source becomes checked posts.
- [Dollar-a-Day guide](https://blitzmetrics.com/dollar-a-day/) — the paid test method; current platform controls still need checking.

## Review and evidence still needed

The original contributor state is preserved. Instruction review, article certification, account access and completed work are separate states.

- Source mapping needs repair: on September 6, 2026, the recorded /thank-you-machine/ hub redirected to /face-socks/, a gift-ordering guide. That live gift recipe does not certify this video workflow. Keep the task ID and contributor state; use the relevant video and process guides below until the owner resolves the canonical video hub.
- Add a dated, real execution record with the actual checked output. The example below does not fill that gap.