# Turn customer objections into an evidence-led response map

**trustWF workflow pack** · Marketing

## Outcome
An objection-response map with evidence links or placeholders, escalation triggers, and coaching notes.

## Who this is for
A product marketer or sales enablement lead organizing repeated customer concerns

## What to provide
Required: anonymized objection notes, approved product facts or policies, and intended sales/support context. Optional: audience segment and tone guidance. Remove names, account IDs, and confidential details.

## Steps
1. Group objections by underlying concern while keeping the original customer wording available for verification.
2. Match each concern only to approved evidence, or mark that evidence is missing.
3. Draft an empathetic response and one useful discovery question for each theme.
4. Add escalation rules for issues that need product, legal, safety, or manager review.

## Copy-ready instructions
STAGE 1 — 1. Classify the source notes
When to use: Use before drafting replies.
Prompt: I need an internal objection map based on these anonymized customer notes: [paste notes with labels]. Context: [product/service and sales or support situation]. Approved product facts, policies, and evidence: [paste or “none supplied”]. Group similar objections by underlying concern, but preserve a short exact phrase and source note ID for each. Separate explicit statements from your interpretation. Mark any objection that cannot be mapped confidently.
Expected return: A theme table with concern, example note IDs, exact phrase, and interpretation.
User check: Check that groupings do not erase meaningful differences or expose customer identity.

STAGE 2 — 2. Draft supported responses
When to use: Use once the concern themes are accurate.
Prompt: For each objection theme above, use only the approved facts and policies provided in this chat. Create a table with: customer concern; empathetic opening; concise response; supporting evidence or “evidence needed”; one discovery question; and what not to promise. If no supplied evidence answers the concern, write a transparent response that offers a follow-up instead of improvising.
Expected return: An evidence-linked response map and list of missing proof points.
User check: Verify every factual claim against the approved material and remove unsupported comparisons or guarantees.

STAGE 3 — 3. Add coaching and escalation
When to use: Use after correcting Stage 2.
Prompt: Prepare internal coaching notes for using this map. Identify when to listen and clarify, when to share approved evidence, and when to stop and escalate to [role/team]. Define escalation triggers for safety, legal, privacy, product defects, pricing exceptions, and unresolved claims as relevant. Do not treat the guide as a script that must override customer context.
Expected return: A short coaching guide, escalation table, and version/review owner placeholders.
User check: Have the relevant product, compliance, or support owner approve high-impact responses before team use.

## Review before using
Never dismiss customer concerns or invent product capabilities, guarantees, comparative claims, or policy. Unanswered technical or regulated concerns must be escalated.

---
Use the result as a draft. Review it for accuracy, context and any required approvals.