| name | customer-voice |
| description | Synthesize customer voice; never infer protected traits. |
| metadata | {"short-description":"Synthesize customer language and themes"} |
Customer Voice
Outcome
A traceable view of what customers are saying, how themes are changing, and what requires action.
CRM-neutral operating contract
- Discover available CRM, communication, calendar, knowledge, and file capabilities before choosing a retrieval plan. If no live CRM is available, use user-supplied exports when that still satisfies the request; never imply a live write is possible.
- Map records by meaning, not vendor labels: organization, person, lead, opportunity, activity, product, service record, user or team, and knowledge item. Inspect schemas and custom fields, preserve native IDs, stages, currencies, timezones, and fiscal periods.
- Keep observed facts, derived conclusions, and missing information distinct. Anchor consequential claims to record IDs, fields, timestamps, or named sources, and state access or freshness limits.
- Start read-only. Before creating, updating, assigning, sending, or scheduling, show the exact proposed action and obtain confirmation unless the current request already authorized that exact mutation.
- Obey connected-system permissions, resolve ambiguous records or people instead of guessing, check for duplicates before creation, and report partial failures without repeated retries.
Workflow
- Resolve the user, target records, requested scope, reporting window, timezone, and business objective. Ask only for missing details that materially change the result.
- Retrieve the minimum authorized evidence needed from the following inputs: Calls, transcripts, emails, notes, surveys, cases, meeting summaries, and relevant account or opportunity context.
- Normalize relevant entities and fields while retaining native record identifiers and source timestamps.
- Apply the analysis rules below. When evidence conflicts, show the conflict rather than averaging it away.
- Deliver the required output in a compact form suited to the scope. Put urgent or decision-relevant items first.
Analysis rules
- Define the customer set, period, channel coverage, and question before synthesizing.
- Group themes without erasing meaningful differences by account, role, stage, or channel.
- Use short attributed excerpts only when they materially support a theme and access permits it.
- Distinguish explicit sentiment from inferred tone, quantify only with a clear denominator, and flag sample bias.
Required output
- Theme summary
- Needs and desired outcomes
- Objections and friction
- Requests and commitments
- Representative evidence
- Recommended actions
Actions and boundaries
Remain read-only unless the user asks to create specific follow-up tasks after review.
