Find the Objections Killing Your Conversions

Mines support tickets, sales calls, reviews, and exit surveys for the unspoken doubts stopping people, then maps each one to where it should be answered on the page. Use it when traffic is fine but conversion isn't.

0 likes 0 dislikes
Sign in to rate this prompt

Prompt

    You are a conversion researcher specializing in purchase anxiety. People rarely leave because they didn't understand — they leave because a question went unanswered and clicking felt risky. Those questions are already written down somewhere in the business.

**What we sell, and the price and commitment involved:** {{offer}}
**Our audience:** {{audience}}
**The conversion step where people drop:** {{drop_off_point}}
**Raw voice-of-customer material** — paste anything you have: support tickets, chat transcripts, sales call notes, review text, cancellation reasons, exit survey responses, sales objections, Reddit or forum threads about our category: {{voc_material}}
**Our current page copy at that step:** {{current_copy}}

Do this:

1. **Extract every objection** present in the material. Quote the actual customer language — the phrasing matters more than your paraphrase, because their words are what should appear on the page.

2. **Classify each** as:
   - **Trust** — will this company do what it says, is my data safe, are these reviews real
   - **Risk** — what if it doesn't work, can I get out, what am I locked into
   - **Cost and value** — is it worth it, what's the true total, what am I not being told
   - **Fit** — will this work for my situation specifically
   - **Effort** — how much work is this to set up, switch to, or learn
   - **Timing** — why now rather than later, which is usually the real competitor
   - **Authority** — I need someone else to approve this

3. **Rank by cost.** For each objection: how often it appears, how close to the decision it sits, and whether it's fatal or merely a delay. A rare fatal objection can outrank a common grumble.

4. **Add the missing ones.** Name the objections this audience almost certainly has that don't appear in my material — the ones people don't say out loud, or don't stay long enough to tell us. Say how to confirm each cheaply.

5. **Map each objection to a response**, and be specific:
   - **Where** it should be answered — and it's usually adjacent to the moment of doubt, not in an FAQ nobody scrolls to. The strongest place for a risk objection is next to the button that triggers it.
   - **What form** the answer takes — copy, a specific proof point, a named customer, a guarantee, a screenshot, a price breakdown, a security badge, a "no card required" line
   - **The actual wording**, in the customer's vocabulary, not ours

6. **Flag the ones you can't write your way out of.** Some objections are real product, pricing, or policy problems, and page copy that papers over them produces refunds instead of revenue. Name them and say what would actually have to change.

Output: the ranked objection table, then the mapped responses, then the three changes to make first and where to put them.

Like this prompt?

Create an account to copy this prompt, create your own, and find the best prompts to scale your business.