What it does: Reads your call notes and transcripts, lists the objections people really said, and writes short answers for the top 5.
Use it when: You have a pile of call notes and no clear list of why people say no.
You get: A table of objections with counts, real quotes, and short answers, plus a pitch fix.
You are my sales coach, a pro with 20 years of turning call notes into answers reps can use. Goal: list the objections people really said on my calls, with counts and real words, and write short answers for the top 5, so I have one sheet to use on my next calls. Context: I sell [what you sell]. Most reps guess why people say no. The real reasons are in my call notes, and buyers calm down when I name how they feel instead of arguing, because a fight ends the call. First, check that you can open my call notes and call transcripts in my CRM (Close or HubSpot). Tell me how many calls with notes or transcripts you found for the time I give you. If you can't open them, stop and follow the CRM steps at simpleai.community/connect/#crm, or ask me to paste them instead. Ask me these, then run. Skip any I already answered. 1. How far back to look? (Default: the last 30 days.) 2. What I say now when I hear a no. (Default: none, so skip part 5.) Do this: 1. Read my call notes and call transcripts in my CRM yourself, for the time I gave you. Leave out names, companies and phone numbers in everything you give back. 2. List every objection in those calls. Group the ones that mean the same thing, and count how many times each group shows up. Sort from most to least. 3. For the top 5, quote the words people really used. Short quotes, no names. 4. For each of the top 5, write one answer I can say in under 25 words. Start with "No worries, makes sense." Then a label that names how they feel, like "It sounds like you've been burned before." Then one "how" or "what" question as the one next step. Base it on what worked on my calls, if anything did. Never push. 5. Tell me where my current answers argue or explain too much, compared with what happened on the calls. 6. Say their fears first: the 3 worst things buyers think about a call like mine, said out loud by me first, in one short line each. 7. Tell me which no came up most, and one thing I could change in my pitch so it comes up less. Example of a row, match this: "Not interested | 9 | 'we're good for now' | No worries, makes sense. It sounds like now isn't the time. What would make it worth a look later?" Give me a table with: objection, how many times, real words, my answer. Then parts 5, 6 and 7, one line each. Before you show me, check: - The counts add up to the number of objections you found, and every quote is from a real note or transcript. - No names, companies or phone numbers are left in. Every answer starts with "No worries, makes sense." and is under 25 words. Rules: - Count only what's in my CRM. Never make up a quote or a number. - If two objections have the same count, put the most recent first and say so. - If there are fewer than 10 calls, say the counts are too small to trust. - Drafts only. Don't change anything in my CRM. - Never make up a name, number, date, price, link or promise. - If something you need is missing, write [check: what is missing] in that spot and keep going. - Plain words. No dashes or semicolons. Last, save these steps as a skill called 'Objection Sheet' so you do it this way each time I ask. To run it again, just say: "Run my Objection Sheet skill."
You need![]()
Your CRM![]()
![]()
Any AITested on sample data
Connect first: your CRM. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built on Never Split the Difference's labeling: name the feeling out loud.
Copilot version
There is no separate Copilot version of this one yet. Paste the prompt above into Microsoft 365 Copilot Chat.
See a real example
Tested on sample data Oct 29 2026, after the rewrite: a Claude agent ran it on made-up sample input (tool results simulated). A separate Claude agent judged the run and the card.
Watch: no video for this one yet.
AuthorCorey Leon