---
name: engage-with-social-comments
description: "Give useful replies to real questions. Track what needs help and what can become a new topic."
category: Content Factory — Promote
stage: Promote
definitive_article: GAP — to be written
status: needs-work
---

# Engage with social comments

People may ask good questions under your posts. This guide helps you reply with care and keep track of what needs more help. Start with the full thread so your answer fits what the person asked.

**The path:** Real thread → factual reply → scoped action → topic or handoff.

**Use this when:** An authorized comment review is due or a specific comment needs attention on a channel in scope.

## Inputs
- Access to the exact approved channels/posts and their complete comment threads, including existing replies.
- The owner’s factual voice guidance, approved offer/support information and scope for replies or moderation.
- Current support/escalation owner, moderation rules and a tracker for unresolved comments, useful questions and possible proof reuse.

## First-run prompt

> Review these exact comment threads, check for existing replies and prepare or post only responses already in scope. Answer from verified facts and the owner’s permitted voice. Keep private details out of public replies, preserve honest criticism and route unresolved issues to the real owner. Log questions without turning praise into an unapproved testimonial.

## Steps
1. Review only the named channels and recent/boosted posts in scope. Read the whole thread and check whether another worker already answered. Do not assume the source’s historical named group or every social account belongs in this job.
2. Classify each item: answerable question, useful feedback, support issue, abuse/spam or no reply needed. The source’s daily review and 24-hour response aim can guide an agreed service standard, but not every short comment needs an artificial question in return.
3. Use verified facts to answer the actual question in the owner’s permitted voice. Do not invent first-person experience, prices, delivery promises or relationships. A needed follow-up question should resolve the person’s need, not prolong the thread solely for engagement.
4. Post within existing reply authority and read back the exact comment. If approval or a source fact is genuinely missing, save the draft and name that narrow gap; do not demand approval again for already authorized routine replies.
5. Handle support details through the approved path without exposing customer records or requesting sensitive data publicly. Preserve honest criticism. Apply hiding/reporting/removal only under the actual moderation rule and authority, and record the reason.
6. Like or pin only when supported by the channel and appropriate within scope. These actions are not mandatory proof of a successful reply. Do not claim comment activity guarantees lower ad costs.
7. Capture recurring questions as topic ideas with source links. Treat praise as possible evidence requiring permission/context for reuse; a screenshot of a comment is not blanket permission to publish a testimonial everywhere.
8. Log what was answered, what remains open, response timing and the real next owner. Keep observed replies, referrals and ad metrics separate; do not attribute cost changes to the conversation without supporting evidence.

## Definition of done (QA checklist)

- [ ] Every reviewed item has the correct thread and duplicate check.
- [ ] Replies are factual, useful and within the owner’s existing voice/action scope.
- [ ] Private details and honest criticism are handled under the real support/moderation policy.
- [ ] Posted actions have read-back; unanswered items have a reason and next owner.
- [ ] Topic/proof ideas remain distinct from approved reuse and claimed paid results.

## Example(s)

**Fictional teaching example:** A viewer asks whether the seat-fix tip applies to a carbon frame. The operator checks the approved technical source and replies that the frame maker’s torque guidance matters; no guessed number is supplied. A second comment reports a missed appointment, so the reply uses the existing support route without exposing the booking details. A third says “great tip” and needs no forced question. The log records one new video topic and a support handoff, not a guaranteed drop in ad cost.

## Handoff and Content Factory context

Send recurring questions to [map out one minute video topics using topic wheel](https://local-service-spotlight.github.io/task-library/?task=map-out-one-minute-video-topics-using-topic-wheel#task-map-out-one-minute-video-topics-using-topic-wheel). A verified gratitude moment can go to [create and send thank you machine videos](https://local-service-spotlight.github.io/task-library/?task=create-and-send-thank-you-machine-videos#task-create-and-send-thank-you-machine-videos) for a separately scoped acknowledgment. Support issues go to the actual service owner.

This task is in Promote within the [Content Factory](https://blitzmetrics.com/content-factory/). Produce gathers real source material; Process makes useful assets; Post places and checks them; Promote distributes suitable work within its own scope. Use the proof and checked posts from earlier stages; a Promote task does not automatically redo all four stages. Use the actual next step above; catalog neighbors are not prerequisites.

## When this runs

Use the channels and daily/24-hour target only when agreed for the job. A recurring sweep needs a real trigger, access and shared state; this file does not watch every channel indefinitely.

## First-run setup and continuity

Open the supplied task file and its linked source. Verify the project’s real inputs, account, access and output folder before work. This Markdown file is a guide; it does not install an app, connect an account, supply a subscription or create a schedule. Carry out work already authorized; do not ask for the same approval again. Keep any unsupplied destination or new action outside that scope clearly pending.

Save source IDs, versions, decisions, checked outputs and next owner in the project tracker. Before a retry, check the saved state and other workers’ changes. A model name does not guarantee memory or a running timer. Repeated work needs an actual configured trigger and durable state; one-off work can be started by the prompt above.

Keep agent media muted with volume zero before playback. If mute cannot be verified, use captions, metadata or still frames. State the limit: silent visual checks do not prove spoken-word accuracy or audio quality. Do not start sound through the user’s speakers unless explicitly asked.

## Write up the real run

For every actual attempt, [write its meta article](https://blitzmetrics.com/meta-article-prompt/) with this recipe and revision, trigger, steps performed, output evidence, measured result, gaps and next owner. Failed, blocked and partial attempts also get a written record. A draft can satisfy writing; publishing it follows the existing job scope.

Keep one stable execution ID across retries and edits. A separately scoped child task may have its own ID linked to its parent. Writing the parent’s meta record is part of that run, not an endless new chain. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains this distinction. Teaching examples are not real executions and must not enter the run count.


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

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

- **Phase:** Promote
- **Importance:** 5/5 `●●●●●` — frequency 4, revenue 5, gating 3 (runs every factory cycle or weekly; ads/revenue path)
- **Suggested previous station:** `run-twitter-x-promotion-for-thought-leader-threads`
- **Suggested next station:** `apply-metrics-decomposition`
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

- Dedicated canonical article: not mapped in this source record. Use the maintained owned training below until that article gap is reviewed.
- Exact task: [Engage with social comments](https://local-service-spotlight.github.io/task-library/?task=engage-with-social-comments#task-engage-with-social-comments)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [One-minute video guide](https://blitzmetrics.com/one-minute-video-guide/)
- [Content Factory](https://blitzmetrics.com/content-factory/)
- [Metrics, Analysis, and Action](https://blitzmetrics.com/maa/)

## Review and evidence still needed

The source contributor status is preserved. It is not certification of this draft or proof of account access, completed work or a live outcome. The worked example teaches the method and is explicitly fictional.
- The source still has no dedicated definitive comment-engagement article.
- The real channels, response authority and support facts must come from the job; the guide supplies none.