Customer Objection Mining Prompt

Analyze the supplied customer evidence to identify, validate, and prioritize objections affecting the purchase decision for [Offer and audience]. Use the findings to recommend messaging and proof—not to invent customer consensus or publish copy.

Research objective: [Research objective]
Evidence corpus: [Evidence corpus]
Source context: [Source context]
Messaging constraints: [Messaging constraints]

## Input requirements
Blocking inputs:
- A clear description of the offer and intended audience.
- Primary customer evidence such as review text, interview or call transcripts, open-text survey responses, support conversations, loss notes, or sales notes.
- A research objective identifying the decision, funnel stage, page, campaign, or sales motion the analysis should inform.

Useful context:
- Source dates, channels, customer segments, win/loss status, product version, geography, and collection method.
- Existing claims, positioning, proof assets, compliance restrictions, brand guidance, and known exclusions.

If the offer, audience, objective, or usable evidence is missing, ask only the questions required to proceed. If nonblocking metadata is absent, continue with an explicit unknowns list and avoid unsupported segmentation. If the corpus is too large for the current ChatGPT context, propose a batch plan and analyze only the text actually available; do not imply complete-corpus coverage.

## Evidence and action rules
- Treat supplied records as observations, not as proof of market-wide prevalence.
- Assign stable source IDs to records or preserve existing IDs. Every reported objection theme must cite its supporting source IDs and include brief verbatim excerpts where permitted.
- Keep verbatim customer language separate from paraphrases, interpretations, hypotheses, and proposed copy.
- Distinguish objections from questions, complaints, feature requests, usability problems, preferences, negotiation tactics, and general negative sentiment. Explain ambiguous classifications.
- Report counts with a denominator and unit, such as records, respondents, calls, or mentions. Do not treat multiple mentions by one person as multiple customers. Flag duplicates, syndicated reviews, repeated scripts, and sampling bias.
- Do not infer demographics, health status, financial condition, or other sensitive traits unless explicitly supplied, necessary, and lawful. Redact direct identifiers and unnecessary personal or confidential information from excerpts.
- Do not fabricate quotations, source details, customer segments, statistics, product capabilities, guarantees, testimonials, or proof. Mark conflicting evidence and unknowns rather than resolving them by assumption.
- Frequency is only one signal. Consider intensity, purchase proximity, segment relevance, recurrence across independent sources, answerability, and available proof. Explain any weighting used.
- Identify unsupported or regulated claims that require legal, compliance, product, or subject-matter review. Do not recommend deceptive urgency, concealment of material limitations, manipulation of vulnerable people, or dismissal of legitimate concerns.
- ChatGPT may inspect only the content supplied in this conversation, organize findings, calculate transparent counts from that content, and propose messaging or experiments. It cannot access omitted files, validate external facts, contact customers, change campaigns, approve claims, or publish content.
- All copy, claim, targeting, and publication decisions remain proposed until an authorized human reviews the evidence, proof, privacy implications, and applicable policy or legal requirements.

## Analysis workflow
1. Define the analytical unit and scope: record type, included sources, time range, audience, funnel stage, and objective. Record exclusions and unresolved scope conflicts.
2. Build a corpus ledger. Assign source IDs; note channel, date or date range, segment metadata, purchase status when supplied, and usability. Identify empty, truncated, duplicate, irrelevant, or potentially synthetic records without silently deleting them.
3. Extract atomic objection expressions. Preserve a brief customer-language excerpt, its source ID, context, and whether it is explicit or inferred. Split records containing materially different concerns.
4. Classify each expression by:
   - objection category, such as price or value, trust or credibility, fit, need or priority, switching cost, implementation effort, usability, risk, timing, authority, compatibility, support, or competitive alternative;
   - underlying concern;
   - funnel or decision stage when evidenced;
   - type: objection, question, complaint, feature request, preference, negotiation, or unclear;
   - evidence strength and uncertainty.
   Create a corpus-derived category when the standard categories do not fit.
5. Cluster semantically related expressions without erasing meaningful differences. Keep distinct themes separate when their root concern, segment, stage, or required response differs. Surface minority and contradictory themes rather than forcing consensus.
6. Quantify each theme using transparent record-level and, when possible, unique-customer counts. State denominators, missing metadata, duplicate treatment, and whether cross-source recurrence is present. Never convert the supplied sample into an unsupported market percentage.
7. Prioritize themes with a documented rubric covering evidence volume, intensity, purchase relevance, cross-source recurrence, strategic fit, answerability, and proof readiness. Show component judgments; label close or fragile rankings.
8. Map each priority objection to a messaging job, response angle, appropriate proof, likely channel or funnel location, and claims risk. Preserve legitimate limitations instead of arguing every objection away.
9. Draft concise copy hypotheses in customer-relevant language. Label them as proposals, avoid presenting customer excerpts as endorsements, and do not convert unverified interpretations into factual claims.
10. Identify proof gaps, including missing demonstrations, comparisons, pricing clarity, implementation details, policies, case evidence, technical validation, or product confirmation. Name the owner or review function needed when it can be inferred; otherwise mark it unassigned.
11. Design validation tests appropriate to the decision, such as message testing, moderated interviews, sales-call coding, landing-page experiments, or follow-up surveys. Specify the hypothesis, audience, channel, primary measure, guardrail, minimum decision rule if supplied, and what result would refute the hypothesis. Do not claim tests were run.
12. Reconcile the analysis before delivery: verify source traceability, counts, denominators, duplicate handling, classification consistency, contradictory evidence, privacy redaction, and the distinction between observed findings and proposed actions.

## Required output
### 1. Scope and evidence status
State the objective, offer, audience, analytical unit, included and excluded sources, coverage limitations, blocking issues, assumptions, unknowns, and conflicts. Label the analysis as complete for supplied evidence, partial, or blocked.

### 2. Corpus ledger
Provide a table with: source ID or range, source type, supplied date or range, supplied segment, record count, usable count, exclusion count and reason, duplicate treatment, and material caveats.

### 3. Prioritized objection map
Provide a table with:
- rank;
- objection theme and underlying concern;
- classification;
- brief verbatim evidence excerpts;
- source IDs;
- unique-record or unique-customer count;
- denominator and unit;
- segments and decision stages evidenced;
- intensity and purchase relevance;
- cross-source recurrence;
- contradictory or disconfirming evidence;
- confidence level with rationale;
- priority rationale.

### 4. Customer-language bank
Group short, privacy-safe excerpts by theme. For each excerpt include its source ID, relevant context, and whether it is representative, unusually intense, or an outlier. Do not silently polish quotation wording.

### 5. Messaging response matrix
For each priority theme provide: messaging job, response angle, proposed copy hypothesis, recommended channel or funnel location, required proof, proof currently supplied, unsupported-claim risk, reviewer needed, and status as ready for review, proof blocked, or research blocked.

### 6. Proof-gap register
List each missing proof asset or unresolved product fact, the objection it affects, why it matters, evidence supporting the need, proposed owner or review function, risk if ignored, and minimum resolution required before publication.

### 7. Validation plan
Provide a sequenced test table with: hypothesis, audience, method, variant or stimulus, primary metric, guardrail metric, decision rule, evidence required, likely confounders, and owner or approval point. Clearly mark all tests as proposed unless execution evidence was supplied.

### 8. Verification and acceptance report
Report expected requirement, actual observation, evidence, and status for each check:
- Every priority theme has at least one traceable source ID and excerpt.
- Theme counts reconcile with the stated analytical unit and denominator.
- Duplicate and multi-mention handling is documented.
- Findings are separated from assumptions, interpretations, and copy hypotheses.
- Minority, conflicting, and disconfirming evidence is visible.
- Segment conclusions use only supplied segment data.
- Proposed factual claims are supported or marked as proof blocked.
- Excerpts are privacy-safe and retain their original meaning.
- Corpus coverage and ChatGPT context limitations are disclosed.
- Recommendations map to the stated objective and constraints.

Do not mark a check verified unless the supporting evidence is present. Record failed, partial, unavailable, and not-applicable checks separately, with the remediation needed.

### 9. Decision handoff
Summarize which objections should be addressed first, which should not yet drive messaging, which claims require approval, and the smallest safe next action. Keep researched, proposed, approved, tested, and published states distinct. Never state that messaging was approved, tested, implemented, sent, or published unless corresponding execution evidence was supplied.