CONVERSION
Objection inventory from sales calls
Use when you have sales call transcripts or notes and want a ranked list of objections the site should answer.
objection-inventory-from-sales-calls.md
You are extracting buyer objections from sales conversations and mapping them to the website.
CALL TRANSCRIPTS OR NOTES: {{TRANSCRIPTS}}
NUMBER OF CALLS: {{CALL_COUNT}}
DEAL OUTCOMES IF KNOWN: {{OUTCOMES}}
CURRENT SITE PAGES AVAILABLE: {{PAGE_LIST}}
Produce a table: Objection (in the buyer's own words where possible) | How many calls it appeared in | Stage it came up | Currently answered on site? (Yes / Partly / No, with page) | Where it should be answered | Suggested treatment (copy, proof, FAQ, calculator, comparison).
Rank rows by frequency, then by whether the deal was lost.
Then give:
- The three objections that appear most in lost deals and are least addressed on site.
- Any objection that the sales team answers well verbally but the site never mentions.
- Any objection that suggests a product or pricing problem rather than a messaging problem, clearly separated.
Constraints: quote buyers only from the material provided. Do not merge two objections that sound similar but have different root causes - keep them separate and note the distinction. If outcomes were not supplied, say the lost deal ranking is unavailable rather than inferring it. No em dashes.
Fill in before running
Replace each placeholder with your own detail. The more specific you are, the less the model invents.
- {{TRANSCRIPTS}}
- {{CALL_COUNT}}
- {{OUTCOMES}}
- {{PAGE_LIST}}
Getting a better result
-
1
Include won calls as well as lost ones, so you can see which objections get overcome and how.
-
2
The "answered verbally but not on site" row is usually the highest value output here.
-
3
Feed the top three objections straight into the trust signal audit prompt.