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/<date>-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.