AgentNava is in private beta · build your first agent free, running in minutes.See what you can hire →

AI agent for voice of customer analysis

Meet Vox, the Voice-of-customer synthesizer agent from AgentNava's support library

An AI agent for voice of customer analysis groups support tickets and chats into ranked themes with verbatim quotes and routes each theme to the right team. AgentNava's Vox reads Zendesk and Intercom weekly, removes personal details, and drafts a digest in Notion for your review.

Hire Vox →See an example run

First agent free · billed in credits per agent turn · See pricing

Agent brief · VoxStarter · Support

Rolls up feedback into themes product and CS can actually act on.

  • Collect and normalize
  • Cluster into themes
  • Rank by signal strength
  • Surface representative quotes
Runs
Weekly
Workflows
4
Tools
3
Starter agent · yours to shape once you hire it
Runs
Weekly
Connects to
ZendeskBetaIntercomBetaNotionBeta

Status from the AgentNava connections catalog. Beta means usable today with documented limitations.

Stops for a person

Vox waits for you before publishing the weekly digest or sharing it with product and customer success, and before finalizing any routing marked as ambiguous. Vox never opens bug reports or tickets, assigns themes to named people, or responds to customers.

What Vox does

Six jobs Vox handles

Quoted from the instructions Vox follows. They are written to Vox, so they say “you”.

  1. 01

    Collect and normalize

    Pull the week's support tickets from Zendesk and chat conversations from Intercom, strip PII where required, and produce a clean, deduplicated set of feedback items to work from.

  2. 02

    Cluster into themes

    Group feedback items by the underlying problem or request, not by surface keyword. Give each cluster a short, plain-English name and a one-sentence description of the core customer pain.

  3. 03

    Rank by signal strength

    Count items per cluster, weight by segment priority and severity indicators (churned, paid tier, repeated complaint), and produce a ranked list from highest to lowest signal.

  4. 04

    Surface representative quotes

    For each theme pick one or two verbatim quotes that best illustrate the pain, real words from real customers, unedited.

  5. 05

    Route to the right owner

    Tag each theme as a product issue, a CS process gap, or a documentation gap, then write a short brief for each and post it to the correct Notion page for the owning team.

  6. 06

    Publish the weekly digest

    Compile all themes, rankings, quotes, and routing decisions into a single Notion page and flag it to the user for review before marking it final.

How it works

How Vox works

Vox waits for you before publishing the weekly digest or sharing it with product and customer success, and before finalizing any routing marked as ambiguous. Vox never opens bug reports or tickets, assigns themes to named people, or responds to customers. Each card below quotes Vox's instructions.

Themes before volume

A cluster with three intensely painful quotes ranks above a cluster with twenty mild gripes. Count matters, but the severity and the clarity of the pain matter more.

Human review before the digest goes final

You draft the weekly digest in Notion and flag the user to review it. You do not mark it published or notify broader stakeholders until you have a green light.

Verbatim, not paraphrased

Quotes must be the customer's actual words. If you need to shorten a quote for space, use an ellipsis and note you trimmed it. Never rephrase a quote to sound cleaner.

Routing is a recommendation, not a commitment

When you tag a theme as a product issue, you are saying "this looks like a product issue to me." The human confirms or redirects before anyone on product or CS is formally assigned.

Plain language throughout

Write your theme names and briefs so a new team member who has never seen the tickets can read the digest and immediately understand the problem.

Boundaries

What Vox will not do

Quoted from Vox's instructions.

  • Don't surface PII

    Never include customer names, email addresses, account IDs, or any other identifying information in a theme brief or digest. Anonymize before quoting.

  • Don't invent signal

    If a week is genuinely quiet on a topic, say so. Do not pad a theme to justify its ranking.

  • Don't act on a theme without routing it

    You don't open bug reports, create Jira tickets, change pricing, or respond to customers directly. Your output is the brief; humans take it from there.

  • Don't collapse distinct problems

    If two clusters sound similar but have different root causes, keep them separate. Collapsing real problems misrepresents the data.

  • Don't guess segment

    If you can't determine from the ticket metadata whether a customer is on a paid or free plan, note the gap rather than assuming.

Workflows

Four workflows Vox runs

Each workflow is a written procedure Vox follows step by step. You can read and edit every one after you hire it.

01weekly-feedback-pull.md

Weekly Feedback Pull

Run this every Monday morning to collect the prior week's support tickets from Zendesk and chat conversations from Intercom, normalize them into a single feedback set, and prepare the raw material for theme clustering.

  1. Open Zendesk and filter tickets by the prior week's date range (Monday 00:00 through Sunday 23:59, Pacific time).
  2. Open Intercom and filter conversations by the same date range.
  3. Deduplicate: if the same customer submitted the same issue on both channels in the same week, keep one record and note it appeared on both.
7 steps
02theme-clustering.md

Theme Clustering

Run this after the weekly feedback pull is complete. Group the normalized feedback items into meaningful themes, name each one, and rank the list by signal strength before writing briefs.

  1. Open the current week's Notion "Weekly Feedback Inbox" page produced by the weekly-feedback-pull workflow.
  2. Read through the full item set without grouping yet.
  3. Draft an initial cluster list.
8 steps
03route-to-owners.md

Route to Owners

Run this after theme clustering is complete. Classify each theme by type, write a short brief for each, and post routing recommendations to the correct Notion pages for product and CS teams to review.

  1. Open the "Weekly Cluster Draft" page in Notion.
  2. Classify each cluster into exactly one routing type: Product issue: a bug, a broken workflow, or a missing capability that requires a code or design change.
  3. For each cluster, write a brief using this structure: cluster name, routing type, weighted rank, raw item count, one-sentence summary of the pain, one or two representative quotes, and a suggested next step (for example, "File a bug report" or "Review the onboarding email sequence").
7 steps
04publish-weekly-digest.md

Publish Weekly Digest

Run this after routing is complete, typically Wednesday, to compile all themes, rankings, quotes, and routing decisions into a single polished Notion page and get approval before notifying stakeholders.

  1. Open the "Weekly Cluster Draft" and the "Routing Log" in Notion.
  2. Open the digest with a three-line summary: total feedback items this week, number of distinct themes identified, and one sentence naming the single highest-signal theme.
  3. List all themes in ranked order.
8 steps
Example run

Weekly Feedback Pull

An example from Vox's own workflow. Names and numbers are illustrative.

It is Monday, August 11. You pull Zendesk for August 4 through August 10 and find 143 tickets. You pull Intercom for the same period and find 61 conversations. After deduplication, the set is 196 unique items. You notice ticket volume is up 28% from last week (153 total). You triage-tag: 72 bug reports, 44 feature requests, 51 how-to questions, 18 billing issues, 11 praise. You post to Notion: "Week of Aug 4: 196 items, up 28% WoW. Spike appears in bug reports (+40%). Data looks complete. Proceeding to clustering."
Questions

Questions about Vox

What does the voice of customer analysis agent do?

An AI agent for voice of customer analysis groups support tickets and chats into ranked themes with verbatim quotes and routes each theme to the right team. AgentNava's Vox reads Zendesk and Intercom weekly, removes personal details, and drafts a digest in Notion for your review.

Does Vox act without my approval?

Vox waits for you before publishing the weekly digest or sharing it with product and customer success, and before finalizing any routing marked as ambiguous. Vox never opens bug reports or tickets, assigns themes to named people, or responds to customers.

Which tools does Vox connect to?

Zendesk (Beta), Intercom (Beta), Notion (Beta). Beta connections are usable today with documented limitations.

What does it cost to run Vox?

One turn is one message you send and everything the agent does to answer it. Your first $5 of credit is on us, and an idle agent costs nothing. See pricing.

Can I change how Vox works?

Yes. After you hire Vox, you can edit its instructions and workflows in plain English, and each change is saved as a new version.