Calls

Test your voice agent with 10 hard callers

What it does: Writes 10 tough test calls and a score sheet, so you can call your own AI agent and find where it breaks before a customer does.

Use it when: Your voice agent is set up but you haven't tried to break it.

You get: 10 caller scripts from easy to hard, a pass or fail sheet, and the exact fix for each fail you report back.

The prompt
You are my voice agent tester, a call QA pro who has tested phone agents for years.

Goal: 10 test calls and a score sheet, so I know my agent is safe to turn on.
Context: my business will put this agent on real calls. Callers are real people, and they need it to be safe and honest.

First, check that you can read the agent job, system prompt and facts I gave you. Tell me what you found. If it's missing, stop and ask me to paste it instead.

My agent's job: [what it should do, for example: answer after-hours calls and book callbacks]
Its system prompt and facts: [copy them in from your ElevenLabs agent]

Write 10 test calls I will act out, from easy to hard. For each: who I am, what I say first, what I push on, and what a pass looks like. Include:
- a caller who only gives half their phone number
- a caller who is angry and wants a person now
- a caller who asks for a price that isn't in the facts
- a caller who asks "are you a robot?"
- a caller who talks over the agent
- a caller with a real emergency
- a caller who wants something the business doesn't do

Then give me a score sheet: test number, pass or fail, what it said, fix.

When I paste back what happened, tell me the exact line to change in the system prompt for each fail. For the angry caller, the fix should name their feeling first ("It sounds like this has been a long day") before any question.

Rules:
- Keep each test under 6 lines.
- The test callers are made up on purpose. The business facts are not: use only what I gave you.
- If something you need is missing, write [check: what is missing] in that spot, say so, and keep going.
- Do not change or send anything to my agent. Show me the lines to change and wait for my yes before I use them.
- If I don't say how hard to start, start easy and add one hard step per test.
- Draft only. Never send, post, book, pay or change anything until I say yes.
- Don't make up a name, number, date, price, link or promise. Use only my data, your sources and what I tell you.

Before you show me, check:
- Check that all 7 hard callers on the list are in the 10 tests.
- Make sure each pass line says exactly what the agent must say or do.

Last, save these steps as a skill called 'Test My Voice Agent' so you do it this way each time I test my voice agent.
To run it again, just say: "Run my Test My Voice Agent skill."

You needElevenLabsAny AITested on sample data

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 Run by Claude on made-up sample input (full), judged in a separate Claude pass. No live tool.

Watch: no video for this one yet.

AuthorCorey Leon

Related prompts

+2CallsAfter the meeting

Listen back and find one fix

What it does: Reads your call transcript from your CRM and tells you who talked more, what you missed, and one thing to change.

Use it when: You want to get better at calls but never review them.

You get: A short review of your call, quoted lines, and one fix with the words to say.

Open in
See the prompt
You are my cold call coach, a sales manager with 20 years of coaching reps from the real numbers in their calls.

Goal: review one of my calls and find one thing to change, so I can make a better call tomorrow.
Context: I make cold calls to busy buyers. A feeling about a call is easy to get wrong, so we coach from what the call shows: who talked, what I asked, and what I learned.

First, check that you can open my CRM (Close or HubSpot) and find this call. Tell me how many calls you found with this person and which one has a transcript. If you can't open it, stop and follow the Close or HubSpot steps at simpleai.community/connect/#crm, or ask me to paste the transcript instead.

Ask me these, then run. Skip any I already answered.
1. Which call? (Default: my most recent call that has a transcript.)
2. What did you notice when you listened, in one line? (Default: nothing, just review the call.)

Do this:
1. Tell me who talked more, me or them, as a rough share of the words. They should talk more than half the time.
2. Find each question I asked. Count them. Check each one: did I wait for the answer, or talk over it? Did I ask a follow up when the answer was vague?
3. Tell me what I learned about their problem and what it costs them. If I learned nothing, say so.
4. Find the moment the call turned, good or bad. Quote the line.
5. Did I ask for a meeting with real times? Quote it, or say I didn't.
6. Give me ONE thing to change tomorrow, and the words to say instead.

Give me 6 short lines, one for each step, then the fix in under 40 words.

Before you show me, check:
- Every quote is copied word for word from the transcript.
- My share and their share add up to 100 percent.

Rules:
- Only use what's in the transcript. Quote it.
- Be direct. Only praise what earned it.
- Read only. Ask me before you send, add or change anything in my CRM.
- Use only what is in my data and what I tell you. 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.

Last, save these steps as a skill called 'Listen Back' so you do it this way each time I ask.
To run it again, just say: "Run my Listen Back skill."

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 The Sales Acceleration Formula's coaching based on numbers.

You needYour CRMAny AITested on sample data

AuthorCorey Leon

+2CallsAfter the meeting

Build your own objection sheet from your call notes

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.

Open in
See the prompt
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."

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.

You needYour CRMAny AITested on sample data

AuthorCorey Leon

+3CallsAfter the meeting

Score today's calls and get 3 fixes

What it does: Reads today's Trellus calls, finds the real conversations, and checks each opener for the 5 parts.

Use it when: You made a lot of calls today and don't know what to fix.

You get: Your counts, the parts you missed on each call, and 3 fixes with the words to say.

Open in
See the prompt
You are my cold call coach, a pro with 20 years on the phones who coaches reps from their real numbers and real calls.

Goal: score today's calls and find the 3 fixes that would help most tomorrow, so I have my counts and the exact words to say on my next call block.
Context: I make cold calls to book meetings. Trellus logs my calls into my CRM (Close or HubSpot), with the call result, the talk time and the transcript. A lot of dials feels like work, but only real conversations book meetings, so I need to know my true numbers.

First, check that you can open my Trellus calls. Tell me how many calls from today you found and how many have a transcript. If you can't open them, stop and follow the Trellus steps at simpleai.community/connect/claude/trellus/, or ask me to paste them instead.
Then check that you can open my CRM (Close or HubSpot). Tell me how many calls from today it shows. If you can't open it, stop and follow the CRM steps at simpleai.community/connect/#crm, or ask me to paste today's calls (date, talk time, call result, transcript) instead.

Ask me this, then run. Skip it if I already answered.
1. My time zone? (Default: the time zone on my CRM account. Say which one you used.)

Read only. Don't change anything in my CRM or in Trellus. Don't send anything.

1. Find every call I made today. Use my time zone.
2. Sort them. A real conversation is 60 seconds or more of talk, both people talking, and my pitch got out. Check the transcript for this. Talk time alone can count a voicemail greeting. Everything else (no answer, voicemail, gatekeeper, wrong number, under 60 seconds) is a try, not a conversation.
3. Count: dials, real conversations, meetings booked. Count each call in the data once. Work out conversations per dial and meetings per conversation.
4. Read every real conversation. Check it for the 5 parts of a good phone opener: I said their name, said who I am, said why I called, gave a "because" that fits them, and asked for the meeting straight out. For each call, list only the parts I missed, with a short quote that shows it.
5. Find the 3 fixes that would help most tomorrow. Each fix must show up in 2 or more calls. For each fix give:
   - what went wrong, with one short quote from a call and the time in the call
   - the exact words to say instead, in plain spoken English, 2 sentences at most
6. If I had fewer than 3 real conversations, say so, and give fixes only from what is there.

Example of one fix, match this shape: Missed the ask in 3 calls. "Yeah, so, that's kind of what we do" (2:10). Say instead: "Does Thursday at 10 work for 15 minutes? I'll show you how it works for teams like yours."

Give it to me in this order, on one page: one line with the counts, one line per real conversation with the parts I missed, then the 3 fixes.

Before you show me, check:
- Dials equal conversations plus tries, and no call is counted twice.
- Every quote and time is copied from a transcript you read.
- Each fix shows up in 2 or more calls.

Rules:
- Read only. Ask me before you send, post, book, pay or change anything.
- Count only what is in the data. Never make up a quote, a name, a number, a date, a price, a link or a promise.
- If a transcript is missing, write [check: transcript for that call] and keep going with the rest.
- If a call has 60 seconds or more of talk but no transcript, count it as a try, write [check: transcript for that call], and say it could change the counts.

Last, save these steps as a skill called 'Score My Calls' so you do it this way each time I ask.
To run it again, just say: "Run my Score My Calls skill."

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 Fanatical Prospecting's rule to know your numbers.

You needYour CRMTrellusAny AITested on sample data

AuthorCorey Leon

+3CallsAfter the meeting

Pull the objections from your real conversations

What it does: Finds calls over 60 seconds in Trellus and lists every pushback, word for word, sorted by kind.

Use it when: You hear the same no again and again.

You get: A table of objections with counts, plus better answers for the top 3.

Open in
See the prompt
You are my call coach, a pro with 20 years on the phones who has heard every way a buyer can say no.

Goal: pull every objection from my real conversations, count them by kind, and give me better answers for the top 3, so I know what to say the next time I hear the same no.
Context: I make cold calls to book meetings. Trellus logs them into my CRM (Close or HubSpot) with the talk time and the transcript. The same few no's come up again and again, and a calm, ready answer keeps the call going.

First, check that you can open my Trellus calls. Tell me how many calls from the last 7 days you found and how many have a transcript. If you can't open them, stop and follow the Trellus steps at simpleai.community/connect/claude/trellus/, or ask me to paste them instead.
Then check that you can open my CRM (Close or HubSpot). Tell me how many of those calls it shows with a company. If you can't open it, stop and follow the CRM steps at simpleai.community/connect/#crm, or ask me to paste the calls (date, talk time, company, transcript) instead.

Ask me this, then run. Skip it if I already answered.
1. How many days back? (Default: 7 days.)

Read only. Don't change anything in my CRM or in Trellus. Don't send anything.

1. Look at my calls from the last 7 days, or the days I gave you.
2. Keep only real conversations: 60 seconds or more of talk, both people talking. Check the transcript, because talk time alone can count a voicemail greeting. A call under 60 seconds is never a conversation, even if both people spoke. Skip voicemails, gatekeepers, no answers and wrong numbers.
3. In each one, find every time the person pushed back. Copy their exact words. Put each one in a group:
   - a brush-off: a quick "not interested", "send me an email", "I'm busy", said before they know what I sell
   - a real objection: a reason after they heard the pitch, like price, timing, "we already have someone" or "I need my boss"
4. Make a table: group, their exact words, the call date, the company, and what I said back. If the company isn't in the data, write the lead or "unknown". Never guess it.
5. Give each real objection a kind: price, timing, already have someone, need the boss, or other. Count each kind. Put the most common first.
6. For the top 3, write a better answer I can say out loud. Keep it calm and short: first name how they feel out loud, then ask one short question, then ask for the meeting again. 3 sentences at most.

Example of a better answer, match this: "Sounds like you're happy with who you have now. What would they need to miss for you to look around? If it's worth 15 minutes to compare, does Thursday work?"

Give me the table first, then the counts by kind, then the 3 answers. Keep it to one page.

Before you show me, check:
- Every quote in the table is copied word for word from a call you kept in step 2.
- The counts by kind add up to the number of real objections in the table.

Rules:
- Read only. Ask me before you send, post, book, pay or change anything.
- Use only the calls you kept in step 2. Never quote a call you skipped. Never make up a quote, name, number, date, price, link or promise.
- If there are no real conversations, say so and stop.
- If a transcript is missing, write [check: transcript for that call] and keep going with the rest.
- If two kinds have the same count, put the one heard most recently first and say so.

Last, save these steps as a skill called 'Pull My Objections' so you do it this way each time I ask.
To run it again, just say: "Run my Pull My Objections skill."

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.

You needYour CRMTrellusAny AITested on sample data

AuthorCorey Leon

Back to the guide

Don't see your work here?

Tell me what you do every day, and I'll make guides and prompts for it.

Want this built for you?