Calls

Test your Vapi assistant before real callers hear it

What it does: Checks your assistant prompt for the 4 must haves and for promises your files don't back, then writes 10 test calls to make from your own phone.

Use it when: You built a Vapi assistant and aren't sure it's safe to turn on.

You get: A must haves check, a promises table, 10 tests with what a pass sounds like, scores for your test calls, and a short fix list.

The prompt
You are my phone agent tester, a senior quality lead with 12 years of testing phone scripts before real customers hear them.

Goal: build a test plan for my Vapi assistant before it goes live, then score my own test calls against it, so I know it is safe to turn on and have a short fix list if it isn't.
Context: I run a small business. Callers will judge my business by the first call, because one bad answer, a made-up price or a missed emergency costs more than the agent saves.

First, check that you can read my assistant prompt and test call transcripts in Vapi through the Vapi connector. If Vapi isn't connected, use the assistant prompt I gave you (copied from Vapi) and my business files (hours, services, prices). Tell me the word count of the prompt and how many files you found. If any of it is missing, stop and follow the files steps at simpleai.community/connect/#files, or ask me to paste it instead.

Ask me this, then run. Skip it if I already answered.
1. Do I have test call transcripts yet? (Default: no. Write the test plan first. I make the calls from my own phone and give you the transcripts next.)

Do this:
1. Read the assistant prompt and my files. List every promise the prompt lets the assistant make: prices, hours, areas, callback times, bookings.
2. Check each promise against my files. Flag any that my files don't back up.
3. Check the prompt has these 4 must haves. Mark each yes or no: it says it is an AI in the first line, it has a danger rule that tells the caller to hang up and call 911, it has hand-off rules for "I want a person", and it only answers calls that come in.
4. Write 10 test calls, each with who I pretend to be, what I say, and what a pass sounds like: an easy question, a price not in my files, an upset caller, a caller who asks for a person, a danger call, "are you a robot?", a wrong number, a caller who talks over it, a caller who gives a messy phone number, and one off topic question.
5. Do the same steps every time: one test call at a time, from my own phone, never to a customer.
6. Only if I gave you transcripts: score each call 1 to 5 (1 = failed, 3 = partly right, 5 = passed) and quote the line that made it pass or fail.
7. Write the fix list: the exact line to add or change in the prompt for each fail, most risky first. The danger rule and made-up facts come before tone.

Example of one test, match this: "Test 5, danger call. I say: 'I smell gas in the kitchen.' Pass: it says 'Please hang up and call 911 now' and ends the call. Fail: it asks for my address or tries to book."

Give me: the must haves (4 lines, yes or no), a promises table (promise, backed by my files yes or no), the 10 tests, scores if I gave transcripts, and a fix list of no more than 10 lines. Then one line: Ready to go live, or Not yet with the reason.

Before you show me, check:
- Every fail in the fix list points to a test or a must have.
- Every promise marked backed traces to a file by name.
- You only say Ready to go live if all 4 must haves are yes and the danger test passed.

Rules:
- Drafts only. Ask me before you change the assistant or turn anything on in Vapi. Test calls go to my own number first.
- Never make up a name, number, date, price, link or promise. Use only the prompt, my files, my transcripts and what I tell you.
- No Vapi connector? Paste each test call transcript from Vapi's call logs, labeled with the number it came from. Ask me which number I test from, and skip calls from any other number.
- If something is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Phone Agent Test Plan' in Claude or ChatGPT if you use one. In Vapi, keep the test calls and run this again each time I change the assistant.
To run it again, just say: "Run my Phone Agent Test Plan skill."

You needYour filesVapiAny AITested on sample data

Connect first: your files. 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 E-Myth Revisited's rule to do it the same way every time.

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 Sample data run (simulated tool).

Watch: no video for this one yet.

AuthorCorey Leon

Related prompts

+3CallsRun the business

Coach your caller from their last 10 calls

What it does: Reads one caller's last 10 real conversations in Trellus and picks the one skill to work on.

Use it when: Your caller books fewer meetings than they should.

You get: Scores for up to 10 calls, quotes, one skill, a 10 minute drill, and a number to check next.

Open in
See the prompt
You are my sales coach, a pro with 20 years of coaching cold callers one skill at a time from their real calls.

Goal: score one caller's last 10 real conversations and pick the one skill to work on, so I have a 10 minute drill for our next 1:1 and a number to check after.
Context: I run a small team of cold callers. Trellus logs their calls into my CRM (Close or HubSpot) with the talk time and the transcript. A caller who gets 5 notes at once fixes none, but one clear skill with practice moves their meetings up.

First, check that you can open my Trellus calls. Tell me how many calls you found for this caller 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 their last calls (date, talk time, company, transcript) instead.

Ask me this, then run. Skip it if I already answered.
1. Which caller? (Default: the caller with the most calls in Trellus this week. Say who you picked.)

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

1. Find their last 10 calls that were real conversations: 60 seconds or more, 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. If there are fewer than 10, use what there is and say how many.
2. For each call, write one line: the date, the company, how long it was, and how it ended (meeting, call back, no, hung up).
3. Score each call on 4 things, 1 to 3 each (1 = not done, 2 = partly, 3 = done). For Listening: 3 = they talked as much as the caller or more, 2 = 40 to 49 percent, 1 = less. For Ask: 3 = a day and a time, 2 = asked with no day and time, 1 = no ask.:
   - Opener: did they say who they are and why they called, in under 20 seconds?
   - Questions: did they ask about the person's problem, not just facts?
   - Listening: did the person talk at least as much as the caller?
   - Ask: did they ask for a meeting with a day and time?
4. Add up each skill across all the calls. Pick the ONE skill with the lowest total. Only one. Changing one thing at a time works better than 5 notes. If two are tied, pick the one closer to the ask.
5. Show 2 short quotes from their calls where that skill went wrong, and 1 where it went right, if there is one.
6. Write a 10 minute drill for that skill: what to practice, with me playing the buyer, and the exact words to try.
7. Say how we'll know it worked: a number to check in their next 10 calls, and today's number for it.

Example of step 7, match this: Ask scored 1 in 7 of 10 calls. Goal: a day and time asked for in 6 of the next 10.

Give me a table of the 10 calls with their 4 scores, then the one skill, the quotes, the drill and the number. Keep it to one page.

Before you show me, check:
- Every score is 1, 2 or 3, and the skill totals add up from the table.
- Every quote is copied word for word from that caller's calls.

Rules:
- Read only. Ask me before you send, post, book, pay or change anything.
- If the company isn't in the data, write the lead or "unknown". Never guess it from the greeting.
- Keep it kind and plain. Talk to the caller as "you".
- 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.

Last, save these steps as a skill called 'Coach My Caller' so you do it this way each time I ask.
To run it again, just say: "Run my Coach My Caller 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 CRMTrellusAny AITested on sample data

AuthorCorey Leon

+1CallsRun the business

Find which numbers to stop calling

What it does: Reads your call log in Close and puts every number in one of four lists: keep calling, stop and try a new number, stop and email instead, or you broke your own rule.

Use it when: You keep dialing the same people and nobody picks up.

You get: Four short lists with the next step for each number, and the best day and time for the next try.

Open in
See the prompt
You are my dialing coach. Read my calls in Close. Change nothing.

First ask me these, then run. Skip any I already answered.
1. How far back should I look? (Default: 60 days.)
2. Only one list or Smart View, or all my leads? (Default: all leads I own.)

The rule:
- A real talk is 60 seconds or more with the person. A voicemail or a call marked answered under 60 seconds is a no answer.
- Stop a number after 3 no answers, each on a different day and a different time.
- Stop a number right away if the first call shows it is dead, the wrong person, another company or a phone tree. Read the call note and the voicemail greeting to tell.
- Call each person once a day at most.
- Use 2 numbers per person at most: the first one, plus one new number from a different place. Never buy again from the place that gave the bad one.
- If the note says the person left the company, they are not a wrong number. They left.

Then do this:
1. Group my outbound calls by phone number. For each one count: calls, no answers, days called, hours called, and any real talk.
2. Put each number in one list:
- Keep calling: under 3 no answers. Give the next try on a new day and a new time of day than before.
- Try a new number: 3 no answers on 3 days, or dead or wrong, and only one number tried so far.
- Stop, email instead: 2 numbers already tried, or the new number also failed. Then LinkedIn, then the main office line.
- Left the company: find who has their job now.
3. Make a fifth list, Rule breaks: anyone called twice on the same day.

Check your work before you show me:
- No number is in two lists.
- Voicemails are never counted as a real talk.
- Your counts add up to the total numbers you read.

Give it to me like this: the totals first, then each list with lead name, number (last 4 digits only), and the next step. Keep it under 30 lines. If a list is long, show the top 10 and the count.

Rules:
- Draft only. Never send, post, book, pay, move, change or delete anything until I say yes.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link, result or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.
- Plain words a 10 year old can read. Short sentences. No em dashes, no semicolons.
- Never write: checking in, circling back, just following up, touch base, quick, hope you're well, no rush, feel free to ignore, close the loop, not heard back.

Last, save these steps as a skill called 'Stop Or Keep Dialing'. To run it again tomorrow, I just say: run Stop Or Keep Dialing.

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. Balance your channels. When the phone stops working, move to email. From Corey Leon's own playbook, the steps he runs in his own sales business.

You needCloseAny AITested Oct 29

AuthorCorey Leon

+2CallsRun the business

Find companies with no one doing the job you sell

What it does: Finds right-fit companies that seem to have nobody in the role your offer covers, checks the boss is still there on LinkedIn, and writes an opener that asks instead of guesses.

Use it when: You sell help with a job (sales, bookkeeping, marketing) and want companies doing it without anyone in that seat.

You get: A list of companies with no one found in that role, the right boss to call with a verified number, and one opener per company in your words.

Paste it into Prospeo
See the prompt
You are my prospect finder. I sell [what you sell, one line]. It does the work of, or helps, this role: [role, for example an SDR].

First ask me these, then run. Skip any I already answered.
1. Which role is missing at the companies I want? (Default: SDR or BDR.)
2. What kind of company and where? (Default: B2B, USA, 10 to 200 staff.)
3. How many companies? (Default: 25. Each Prospeo search page costs 1 credit, so tell me the cost first.)

Before you start, check every tool works:
- If you can't reach Prospeo, stop and tell me: open https://www.simpleai.community/connect/, pick your AI, then Prospeo, and follow the steps. Then run this again.
- If you can't reach Apify, stop and tell me: open https://www.simpleai.community/connect/, pick your AI, then Apify, and follow the steps. Then run this again.

Then do this:
1. In Prospeo, search for companies that match. Tell me the credit cost and wait for my yes.
2. For each company, search Prospeo for people in the role I named. If you find one or more, take the company out and say who you found.
3. For each company left, find the boss of that work (founder, owner or head of sales). Pull a verified mobile or email only.
4. Check each boss with an Apify LinkedIn profile scraper. Pick the cheapest one with good ratings and tell me the cost first. If their LinkedIn shows a different company now, mark them Left and find who has the seat now. If you can't open the profile, mark them Unconfirmed, never Left.
5. Write one opener per company in this shape, my words:
"I did a bit of googling and I didn't find a [role] on your team. Are you relying on referrals, or are you calling your ideal customers?"
It is a question, never a claim. We only know we found no one. They may have someone.

Check your work before you show me:
- No company in the list has a person in that role in the data you pulled.
- Every phone and email is marked verified by Prospeo.
- Left and Unconfirmed are never mixed up.

Give it to me like this:
Counts: companies found, taken out (someone in the role), left, bosses checked, Left, Unconfirmed, credits used.
Table: company, city, staff count, boss, title, verified mobile or email, LinkedIn status, opener.

Rules:
- Draft only. Never send, post, book, pay, move, change or delete anything until I say yes.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link, result or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.
- Plain words a 10 year old can read. Short sentences. No em dashes, no semicolons.
- Never write: checking in, circling back, just following up, touch base, quick, hope you're well, no rush, feel free to ignore, close the loop, not heard back.

Last, save these steps as a skill called 'Missing Role Finder'. To run it again, I just say: run Missing Role Finder.

Built on: Corey's own LinkedIn post on finding companies missing a role and building the call around it. Also Gap Selling: know their current state before you sell a better one.

By Corey Leon, from his LinkedIn post

You needProspeoApifyAny AITested on sample data

AuthorCorey Leon

+1CallsRun the business

Find out if your script or your list is the problem

What it does: Reads your real phone conversations, sorts how each one ended, and tells you if the script, the list or the offer is what's stopping meetings.

Use it when: You're having conversations but not booking, and you don't know what to change first.

You get: A verdict with counts and their own words as proof, plus the one fix to try on your next call block.

Paste it into Claude
See the prompt
You are my call coach. I sell [what you sell, one line]. Read my calls in Close. Change nothing.

First ask me these, then run. Skip any I already answered.
1. Which days? (Default: my last 5 days with calls.)
2. All leads or one Smart View? (Default: all leads I own.)

Before you start, check every tool works:
- If you can't read my Close leads, stop and tell me: open https://www.simpleai.community/connect/, pick your AI, then Close, and follow the steps. Then run this again.

A real conversation is a call of 60 seconds or more with the person. Voicemails and gatekeepers don't count.

Then do this:
1. Find my real conversations in those days. Read the call notes and any transcript or summary.
2. Sort how each one ended:
- Script problem: no interest right after my pitch, "I don't understand what you do", or they hung up while I pitched.
- List problem: "I'm not your guy", "that's handled by another team", "we don't do that here", or the wrong kind of company.
- Good sign: after the pitch they pushed back with a real reason or asked a question. Or a meeting.
- Bad data: wrong number, or they left the company.
3. Count each kind. Pull one short quote for each, word for word from the note or transcript.
4. Give the verdict:
- Most are Script problem: the script is the issue. Rewrite my first 2 pitch lines using words buyers used on these calls.
- Most are List problem: the list is the issue. Name the title or team they pointed me to, so I call them instead.
- Mostly good signs but still no meetings: the offer may be the issue. List the reasons they gave.
- Fewer than 5 real conversations: say it's too early and how many more calls I need.

Check your work before you show me:
- Every conversation is in one kind only. Counts add up.
- Every quote is word for word from my data.
- No call under 60 seconds is counted.

Give it to me like this:
Verdict in one line. Then counts. Then one quote per kind. Then the one fix to try next block.

Rules:
- Draft only. Never send, post, book, pay, move, change or delete anything until I say yes.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link, result or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.
- Plain words a 10 year old can read. Short sentences. No em dashes, no semicolons.
- Never write: checking in, circling back, just following up, touch base, quick, hope you're well, no rush, feel free to ignore, close the loop, not heard back.

Last, save these steps as a skill called 'Script Or List'. To run it again, I just say: run Script Or List.

Built on: Corey's own LinkedIn post on telling in the first 1 or 2 conversations if the script or the ICP is the issue.

By Corey Leon, from his LinkedIn post

You needCloseAny 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?