mcpField
V
voice-of-customer

voice-of-customer

github.com/gtmagentsMarketing & growth42885 installsUpdated 30w ago
Repository

About voice-of-customer

A marketing skill for designing Voice of Customer research and turning findings into prioritized journey actions. It covers research planning, signal analysis, insight presentation, and follow-through.

Key features

  1. 01Research program design
  2. 02Qualitative and quantitative channel selection
  3. 03Insight tagging by segment and impact
  4. 04Journey-mapped insight artifacts
  5. 05Insight-to-action tracking

Use cases

  1. 01Planning customer journey discovery
  2. 02Validating customer hypotheses
  3. 03Building continuous feedback loops
  4. 04Prioritizing journey improvements

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill voice-of-customer

After installing, type/voice-of-customerin Claude Code to confirm it loaded.

Details

From the project README

Voice of Customer System Skill

When to Use

  • Planning journey discovery projects or validating hypotheses.
  • Building continuous feedback loops (surveys, interviews, community, support mining).
  • Translating VOC findings into prioritized journey actions.

Framework

  1. Program Design – define objectives, personas, touchpoints, sample size, and incentives.
  2. Channel Mix – select qualitative (interviews, live sessions) and quantitative (NPS, CES, product usage) data sources per stage.
  3. Signal Processing – tag insights by emotion, friction type, segment, and impact.
  4. Insight Packaging – create artifacts (quote boards, heatmaps, KPI overlays) mapped to journey maps.
  5. Action Loop – pair each insight with a recommended experiment, owner, and expected metric lift.

Templates

  • VOC research brief (question, method, sample, timeline, owner).
  • Insight tagging spreadsheet with stage/persona labels.
  • Signal-to-action tracker (insight → priority → owner → status).

Tips

  • Rotate participants quarterly to avoid bias; maintain consent logs.
  • Combine VOC with telemetry to validate scale of issues.
  • Share short audio/video snippets to humanize data for stakeholders.

Comments

Markdown supported