# Voc Dispatch > Generate the actual deliverables from routed VoC items — case-study outreach emails, landing-page copy briefs, PM one-pagers with verbatim quotes, testimonial snippets, and the executive memo. This is the step that produces work product rather than analysis. Trigger on /voc-dispatch, "generate the artifacts", "draft the outreach", "write the exec memo". - Skill: `aatirar/voc-dispatch` (Agent Skill) - Install (CLI): `npx skillmds@latest add aatirar/voc-dispatch` - Raw SKILL.md: https://api.skillmd.com/api/skills/aatirar/voc-dispatch/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: aatirar (https://skillmd.com/u/aatirar) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/aatirar/voc-dispatch --- # /voc-dispatch — Produce the Artifacts `/voc-route` decides who needs to know. This skill writes the thing they receive. Every artifact must be openable on its own and make sense to someone who never read the synthesis. ## Requires | What | Value | |---|---| | Input | `outputs/voc/routed/*.md` | | Config | `context/product-context.md` for voice constraints and team names | | Cost | Free. | **Nothing here sends anything.** Every artifact is a draft on disk. Sending is a human decision. --- ## A. Case-study outreach email For each entry in `case-study-leads.md`: - 80-120 words, from a named human, not "the marketing team" - **Opens by referencing the specific outcome they described, in their words.** This is the whole reason the pipeline preserved verbatim quotes through four stages. - Asks for 30 minutes. One ask. - No adjectives about your own product. They already bought it. - If the routing entry has no specific outcome, **hold the email and say so.** Do not write a generic request and do not invent a result they did not claim. → `outputs/voc/dispatched/case-study-emails/-.md` ## B. Landing-page copy brief For each objection in `objection-map.md`: - The objection in prospect language, with mention count and channel spread - The page or pages it should be addressed on - **Where on the page**: hero, an FAQ entry, a comparison block, a dedicated section. An objection answered in the wrong place is answered too late. - Two or three drafted options for the copy that addresses it - What evidence the page needs to make it credible — a number, a customer name, a screenshot Copy constraints, applied to everything drafted here: no em dashes, no "it's not X, it's Y", no more than two consecutive negations, no *robust / seamless / powerful / enterprise-grade / best-in-class / effortless / game-changing*. Write the benefit first and the feature second. → `outputs/voc/dispatched/copy-briefs/-.md` ## C. PM one-pager For each capability area in `product-feedback.md`: - Capability area and mention count - **The weighted account list** — company, tier, revenue band, and whether any mention was flagged as blocking a deal. This is what turns a request into a prioritization input. - **3-5 verbatim quotes, unedited, with attribution.** Do not summarize them. Do not lead with your interpretation of what the customer "really means." - One suggested next step, framed as a question for the PM rather than a demand → `outputs/voc/dispatched/pm-onepagers/-.md` ## D. Executive memo One page synthesizing `exec-memo.md`: - Five to seven observations, each tied to a revenue, segment or competitive implication - Each observation states its evidence base inline: how many channels, how many accounts - Closes with a specific ask — a decision, a resource, or an explicit "no action needed, awareness only" - Tone: factual and short. No marketing flourish, no build-up, no restating the company strategy This is the only artifact that is allowed to synthesize rather than preserve. Everything else carries the raw quotes. → `outputs/voc/dispatched/exec-memo-.md` ## E. Testimonial snippets For each entry in `testimonial-queue.md`: - Verbatim quote, customer name, title, company - Suggested channels - **Approval status: always `NOT APPROVED` from this skill.** A human obtains permission. Record who and when in the file once they have. - Source link, so anyone can verify the quote is real before it goes on a page → `outputs/voc/dispatched/testimonials.md` (single rolling file) --- ## Execution Read each routing file, generate its artifacts using the preserved quotes, write to disk, and print what was produced with paths. Then state plainly what was **held** and why. ``` Dispatch — 2026-04-26 Case-study emails 2 drafted 1 held (no specific outcome in the source) Copy briefs 3 drafted covering 5 pages PM one-pagers 4 generated Executive memo 1 Testimonial snippets 2 added both NOT APPROVED, pending customer permission outputs/voc/dispatched/ ``` --- ## Rules that are not negotiable - **Verbatim quotes are never rewritten.** Not for grammar, not for length, not for tone. The entire pipeline exists to get a customer's actual words in front of someone who can act, and every rewrite is a small lie that compounds. - **No fabricated metrics.** If a customer said "much faster," write "much faster." Do not render it as "40% faster" because that reads better in a case study. - **No artifact claims customer approval.** Ever. - **Every artifact stands alone.** Assume the recipient will not open the synthesis, the routing file, or the source transcript. --- ## What this gets wrong - **A good brief is not a good page.** Copy briefs give a writer direction and evidence; they do not replace the writer. - **Outreach written from a quote can feel surveilling.** "I saw you said X on your G2 review" lands badly. Reference the outcome, not the fact that you were monitoring them. - **The exec memo compresses, and compression loses the edge cases** that were often the most useful part. Link the synthesis from the memo. - **Volume is not value.** A week that produces twelve artifacts is usually a week where the routing bar slipped, not a week with unusual signal.