---
name: email-and-dm-client-about-published-article
description: "Tell the client their article is live. Send the right links and one clear next step."
category: Content Factory — Post
stage: Post
definitive_article: https://localservicespotlight.com/article-guidelines/
status: complete
---

# Email and DM client about published article

Your client should not have to hunt for their new article. This guide helps you send the live link and one useful next step. First, check the page and the client’s real contact details.

**The path:** Live page → Right person → Email and short note → Saved follow-through.

**Use this when:** The article is publicly visible and the job includes telling the client it is live. A DM is a direct message in the chat channel you both use.

## Inputs
- The checked public article, title, source context, and any social posts that are actually live.
- The exact client email/thread and normal direct-message channel from the project record. Check identity rather than guessing from search order.
- Existing authority to send on those channels, the approved sending account, and the requested ask. Carry forward permission already given for the job.
- The tracker, current notification history, next owner, and any agreed follow-up cadence.

## First-run prompt

> Use the checked article and exact client thread I provide. Draft a short email and a message with one useful ask. Carry out sends already authorized for this job, then verify each sent copy and log it. Check existing messages before follow-up. Do not claim a send, share, reply, or ad launch without evidence.

## Steps
1. Open the canonical article as a visitor. Confirm the correct title, source, and visible content. A saved WordPress response alone does not prove it is live. Check each social link before including it.
2. Read the exact client thread and tracker. Confirm the recipient and current channel. Check whether another worker already sent this notification; do not create a duplicate.
3. Write an email with a clear subject such as “Your article is live: [title].” Include the article link, two short lines on the useful point, and one specific ask. State only distribution or promotion that actually happened.
4. Prepare a short note for the client’s normal direct-message channel. Link the article or the relevant social post and use a personal, factual sentence. Do not claim a screenshot was taken or praise received unless that is true.
5. Send the email and message when these sends are already in scope. If the job covers only a draft or one channel, finish that authorized work and label the task result draft or partial rather than sent. Do not request duplicate approval for an authorized send.
6. Read back the sent copy in each exact thread. Log date, channel, recipient, sent-message reference, links, and the ask. A composed draft or a send-button click without confirmation is not a sent receipt. A sent-folder copy proves dispatch, not delivery: record a bounce, failed DM, or rejected destination as failed or pending with its next owner.
7. Follow the project’s existing cadence. The source proposes one follow-up after 48 hours with no reply; use it only when that follow-up is part of the agreed job. Check for a real reply and another worker’s recent message before following up.
8. If a reply arrives, record it accurately. A positive private reply can inform a later [Thank You Machine](https://blitzmetrics.com/thank-you-machine/) task; it is not automatically public testimonial permission. Handoff or close the remaining follow-up with its true state.

## Definition of done (QA checklist)

- [ ] The canonical article and included social links are actually live.
- [ ] Each in-scope message is confirmed sent to the intended person and recorded once; draft-only, partial, bounced and failed-delivery states are not called a completed notification.
- [ ] The message gives accurate context and one clear ask, with no invented promotion or response.
- [ ] Follow-up has a real owner/state; no reply is recorded as no reply, not failure of the send.
- [ ] Any quoted response retains its privacy and use limits.

## Example(s)

**Fictional teaching example — no message was sent.** Maple Cycle’s sample article explains how to ask for a repair quote.

**Subject:** Your article is live: How to ask for a bike repair quote

“Hi Alex, your guide is live at `https://maplecycle.example/repair-quote/`. It explains which details help the shop prepare for a visit. Would you share it with the next customer who asks how quotes work?”

The sample DM is: “Your quote guide is ready to share: `https://maplecycle.example/repair-quote/`. The photo checklist is the part I think riders will use most.”

If only the email has a sent receipt, record “email sent; DM still pending.” A client who has not replied has not supplied a testimonial. The `.example` address is an invented teaching URL and must be replaced with the real checked page.

## Handoff and Content Factory context

The project owner receives the send references and any pending follow-up. [Share a lesson in the designated group](https://local-service-spotlight.github.io/task-library/?task=share-in-44k-facebook-group#task-share-in-44k-facebook-group) follows only when that group distribution is in the plan; it is not required to prove the client notification was sent.

This task serves **Post** in the [Content Factory](https://blitzmetrics.com/content-factory/). Produce supplies the source, Process prepares it, Post places and checks it on the agreed channels, and Promote distributes proven work under its own scope. The task’s actual handoff above defines the next step; list order alone does not create a prerequisite.

## When this runs

One notification per published article, with source-recommended same-day timing when feasible. Preserve the project’s actual cadence. A 48-hour follow-up needs an existing authorized timer or a named manual owner; this file cannot wake itself.

## First-run setup and continuity

Use the exact account, source, destination and authority recorded for the job. Carry out publication, messages or repairs already authorized once their required checks pass; do not ask for the same approval again. If an action is outside that scope, finish the authorized work and state the specific remaining need. A login, plugin, or task file does not itself grant new authority.

Keep the latest state, record IDs, revisions and next owner in the project tracker or files. Before a retry, check the current saved/sent/published item to avoid duplicates or overwriting another edit. A model has no guaranteed memory, scheduler or account access just because it is called persistent. A future check needs a configured timer or a named person.

Keep all agent media previews muted with volume zero before playback. If this cannot be verified, use captions, metadata or still frames and state what was not tested. No first-load autoplay is part of these page instructions.

## Write up the real run

For each actual attempt, [write its meta article](https://blitzmetrics.com/meta-article-prompt/) with this exact task, source revision, trigger, work, decisions, evidence, result and next owner. Failed, partial and blocked attempts still get a written record. A private draft is a valid writing outcome; public publication follows the existing scope.

Keep one stable execution ID for the actual task run. Retries, checks and changed artifacts do not add runs. A separately scoped child task may have its own ID linked to its parent; writing the parent’s meta record is part of that same run. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains the distinction. Teaching examples below or above are not execution evidence and must not enter the run count.


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

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

- **Phase:** Post
- **Importance:** 4/5 `●●●●○` — frequency 4, revenue 4, gating 2 (runs every factory cycle or weekly; creates the asset ads amplify)
- **Suggested previous station:** `share-in-44k-facebook-group`
- **Suggested next station:** `identify-signals-worth-amplifying`
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

- Canonical article: https://localservicespotlight.com/article-guidelines/
- Exact Task Library record: [Email and DM client about published article](https://local-service-spotlight.github.io/task-library/?task=email-and-dm-client-about-published-article#task-email-and-dm-client-about-published-article)
- Working writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)

## Review and evidence still needed

The original contributor status in the header is preserved. It does not certify this proposed rewrite or prove that this account, publication, message, player or check has run. Every worked teaching example is explicitly invented; replace it with actual evidence when documenting a real execution.
- The real client thread, send authority, delivery receipts, and any follow-up state require the actual project.