# Voc Route > Take confirmed VoC themes and route each to its destination — testimonial queue, case-study leads, marketing objection map mapped to specific website pages, product feedback intake, or executive memo. Every routing decision carries the verbatim quotes and account context with it. Trigger on /voc-route, "route these findings", "who needs to see this". - Skill: `aatirs-vault/voc-route` (Agent Skill) - Install (CLI): `npx skillmds@latest add aatirs-vault/voc-route` - Raw SKILL.md: https://api.skillmd.com/api/skills/aatirs-vault/voc-route/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Marketing & Growth - Author: Aatirs-Vault (https://skillmd.com/u/aatirs-vault) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/aatirs-vault/voc-route --- # /voc-route — Send Findings Where They Get Acted On A synthesis report is intelligence. Nobody acts on intelligence; they act on a thing that landed on their desk with their name on it. This skill decides where each confirmed theme goes and carries the evidence along, so the receiving team never has to redo the analysis to trust it. ## Requires | What | Value | |---|---| | Input | `outputs/voc/synthesis/-confirmed.json` | | Config | `context/product-context.md` → `routing_overrides`, `page_map` | | Cost | Free. No external calls unless you enable a push destination. | --- ## The five destinations ### 1. Testimonial queue **Route when:** praise is specific, attributable, and about a concrete outcome. The account is CRM-matched at tier A or B. The language would survive being put on a landing page. **Do not route** generic praise. "Great product, easy to use" is worthless as a testimonial and using it signals you had nothing better. **Carries:** verbatim quote, customer name and title, account context, suggested channels, and an explicit **approval-required** flag. Public use of a customer quote generally needs written permission regardless of where you found it — a G2 review is public, but re-publishing it in an ad with their logo is a different act. Never mark a quote approved from this skill. ### 2. Case-study leads **Route when:** the customer described a before-and-after — a transformation, a measurable outcome, or a switching story. Active customer, tier A preferred. **Carries:** the outcome arc in their own words, why this story is interesting, and a proposed angle. The draft outreach email is generated by `/voc-dispatch`, not here. ### 3. Marketing objection map **Route when:** a recurring prospect objection appears. This is the highest-leverage destination and the most commonly skipped. **Carries:** the objection in prospect language, mention count, and **the specific pages where it should be addressed** — resolved from `page_map` in your context file. An objection routed without a page is a note; an objection routed to `/pricing` and `/security` is a task. Flag separately any objection that **recurred after a rep handled it well**. That is a messaging failure, not a sales failure, and it belongs to marketing. ### 4. Product feedback **Route when:** feature requests or friction points, especially recurring ones. **Carries:** capability area, mention count, the **weighted account list** so a PM can see the revenue concentration behind it, and 3-5 verbatim quotes. PMs read raw quotes far more carefully than summaries — preserve them and do not lead with your interpretation. Mark whether any mention was flagged `blocking_deal`. A request tied to a lost deal is a different object than a nice-to-have with the same mention count. ### 5. Executive memo **Route when:** the signal is organization-level. Category shifts, segment-level changes, competitive moves with revenue implications, pricing-position erosion. **Not** "we got three complaints about onboarding." The test: would this change a decision someone makes this quarter? If not, it belongs in one of the four queues above. A theme can route to several destinations. Praise about a specific capability belongs in both the testimonial queue and product feedback — the PM should see what is landing, not only what is broken. --- ## Execution 1. **Read** the latest `*-confirmed.json`. Parse the structured file, not the markdown report. 2. **Classify** each theme against the triggers above. Multiple labels allowed. 3. **Attach evidence** — pull quotes and account context from the confirmed JSON. Never regenerate or re-word them. 4. **Resolve pages** for objection-map entries using `page_map`. If a page cannot be resolved, say `page: unresolved` rather than guessing a URL. 5. **Append** to the destination files under `outputs/voc/routed/`. Append, never overwrite — these files are meant to compound, and their value is the accumulated record. Use a dated section header per run. 6. **Hold** anything you cannot confidently place. `outputs/voc/routed/_held.md`, with a note on what would resolve it. Forcing a theme into a queue to avoid an empty section is how these files become noise nobody reads. Print a summary: ``` Routing — 2026-04-26 · 7 confirmed themes in Testimonial queue +2 Case-study leads +1 Objection map +3 (covering 5 pages) Product feedback +4 Executive memo +1 Held for next week 1 (needs a second channel) Multi-routed: 3 themes went to more than one destination ``` --- ## Push destinations By default every destination is a markdown file. `routing_overrides` in your context file can send them elsewhere: | Destination | Override | |---|---| | Linear / Jira | product feedback becomes an issue | | Notion | objection map becomes a database row | | Chat | executive memo posts to a channel | | Email | memo becomes a draft, never an auto-send | **Never configure an override that sends externally without a human in the loop.** A pipeline that emails customers on its own is one hallucinated quote away from a serious problem. --- ## What this gets wrong - **Routing rules are judgment encoded as triggers.** A theme that fits two destinations badly will land in one of them confidently. - **The objection-to-page map goes stale.** Pages get renamed and consolidated. Re-check `page_map` quarterly or you will route real objections to dead URLs. - **Compounding files decay without pruning.** After a few months these accumulate resolved items. Schedule a review, or the signal-to-noise ratio inverts and people stop opening them. - **Executive memo is the easiest to abuse.** Everything feels strategic to the person who found it. If more than two themes route there in a week, your bar has slipped.