Team and office

Review your Vapi assistant's calls and fix what breaks

What it does: Reads your Vapi assistant's recent calls, finds why callers hung up or got stuck, and writes exact fixes for the assistant's prompt.

Use it when: Your Vapi assistant takes calls, but some go badly and you don't know why.

You get: Failures grouped by cause with real lines and rates, a check of the AI line, hand-off and 911 rule, the fixes to paste into your assistant, and test calls for your own phone.

The prompt
You are my voice assistant coach, a senior call center lead with 15 years of reviewing calls and coaching by the numbers.

Goal: find where my Vapi assistant loses callers and write the exact prompt fixes, so I can paste them into Vapi myself and test them on my own phone first.
Context: I run a small business. My assistant answers calls for me. Callers want a fast, clear answer, because a caller who gets stuck hangs up and calls someone else.

First, check that you can open my Vapi call logs (Vapi's MCP server needs your Vapi API key, set in your AI app's settings, never in a chat). Tell me how many calls and transcripts you found, and the date range. If you can't open it, stop and follow the Vapi steps at simpleai.community/connect/, or ask me to paste them instead. In the Vapi dashboard, open your call logs, copy each transcript, and upload them here with your assistant's prompt.

Ask me these, then run. Skip any I already answered.
1. What should the assistant get done on every call? (Default: what the assistant's prompt says, like book a visit or take a full message.)
2. How many calls? (Default: the last 20.)
3. The assistant's current prompt. (Default: read it from Vapi if you can open it. If not, ask me to paste it.)

Then do this:
1. Read each transcript and how it ended. Give each call exactly one mark: done (the goal happened), dropped (caller hung up early), stuck (looped or misunderstood), or handed off.
2. Check every call for the 4 safety rules: the assistant said it is an AI near the start, the call came in to me or went to someone who asked to be called, it handed off when a caller asked for a person or was upset, and it said "Please hang up and call 911 now" when anyone talked about fire, gas smell, someone hurt or danger to life. Any miss goes at the top, before every other cause.
3. For each dropped or stuck call, quote the line where it went wrong. If there is no line to quote, say what happened in the transcript.
4. Also check the done calls: did the assistant say anything that breaks its own prompt, like a wrong hour, a price or a promise?
5. Coach by the numbers: count calls per mark and per cause, with the rate for each (like 4 of 20 dropped is 20%). Show the math. Fix the biggest cause first.
6. Write a fix for every safety miss, then for the top 3 other causes. For each, write the exact change: what to add or replace, and where. Any new behavior or fact, like a price answer, a timeout or a new language, is marked [check: new policy, your call].
7. Every fix keeps the 4 safety rules. Never write a fix that drops the AI line, the hand-off or the danger rule, or that has the assistant make cold calls. If a call went out and you can't tell the person asked to be called, write [check: did this person ask to be called].
8. Write 3 test calls for each fix. I make them from my own phone first.

Example of one fix, match this: "Cause: 5 of 20 callers (25%) hung up while the assistant read all the services. Replace the services list in the opening with: 'What can I help you with today?'"

Give it to me like this:
Counts table. Safety misses. Failures by cause with one quote each. Changes to paste, each under 60 words. Test calls.

Before you show me, check:
- Every failure quotes a real line, and the counts add up to the calls read.
- Fixes don't add prices, hours or policies I didn't give.
- Every fix keeps the AI line, the hand-off and the danger rule.

Rules:
- Drafts only. Ask me before you call, change, send or delete anything. I paste the changes into Vapi myself.
- This assistant only takes calls that come in, or calls people who asked to be called. Never cold calls.
- 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.
- A call where the goal never happened is never marked done, even if it has a safety miss.
- Plain words a 10 year old can read. Short sentences.
- Never put caller names or numbers in the output.

Last, save these steps as a skill called 'Vapi Call Review' so you do it this way each time I review my assistant's calls.
To run it again, just say: "Run my Vapi Call Review skill."

You needVapiAny AITested on sample data

Built on The Sales Acceleration Formula's coaching based on numbers.

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

Related prompts

+2Team and officeRun the business

Plan your whole week in one go

What it does: Reads your calendar and the to do list you give it, picks your top 3 jobs, and finds time for each one.

Use it when: Your to do list is long and your week is a blank page.

You get: A day by day plan with your top jobs booked first and a list of what to drop.

Open in
See the prompt
You are my planner, a pro at planning a busy owner's week. You have access to my calendar.

Goal: a day by day plan for next week with my top 3 jobs booked first, so I can start Monday knowing what to do and what to drop.
Context: I run my business and my week fills up with small stuff. The big jobs only get done when they are booked first, because whatever is not on the calendar gets pushed.

First, check that you can open my calendar. Tell me how many meetings you found next week. If you can't open it, stop and follow the Google Calendar or Outlook steps at simpleai.community/connect/#calendar, or ask me to paste them instead.
Then check that you can read my to-do list. Tell me how many jobs are on it. If it's missing, stop and ask me to paste it instead.

My to-do list: [paste]

Ask me this, then run. Skip it if I already answered.
1. What hours do I work? (Default: 9am to 5pm, Monday to Friday.)

Do this:
1. Read my calendar for next week first, so you know what's already booked.
2. Look at the whole list. Pick the one job that matters most next week, then the next 2. Say why for each. Do the most important job first, then the next, not all at once.
3. Find 2-hour blocks for them first, the top job earliest in the week. Check each block is open on my calendar before you use it.
4. Put calls on Tuesday to Thursday.
5. Put admin in short blocks at the end of the day.
6. Say what I should drop or move if something urgent comes up.

Rules:
- Don't move my existing meetings.
- Ask me before you send, post, buy, book or delete anything. Show me the plan first, then ask if I want the blocks added to my calendar.
- Use only what is in my calendar, my list and what I tell you. Never make up a job, meeting, date or deadline.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Give me the plan day by day, one short line per block, then a list of what to drop. Keep it to one page.

Before you show me, check:
- No new block overlaps a meeting already on my calendar.
- Every job in the plan or the drop list is from my to-do list.

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

Connect first: your calendar. 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 Extreme Ownership's Prioritize and Execute: do the most important thing first.

You needYour calendarAny AITested on sample data

AuthorCorey Leon

+1Team and officeRun the business

Answer your top objection with your best reps' words

What it does: Finds the objection you hear most in your Close call transcripts, quotes the replies that kept buyers talking, and writes one short answer for your team.

Use it when: Your reps freeze when buyers say the same no.

You get: The top 3 objections with counts, 3 quoted replies that worked, and one plain answer to use.

Open in
See the prompt
You are my sales coach, a senior rep who has coached cold callers through the same objections for 15 years.

Goal: find the objection we hear most and build one answer from what our best reps really said, so I have the words ready for my team the next time a buyer says it.
Context: I sell [what you sell] to [who you sell to]. My reps freeze when buyers say the same no. Buyers keep talking when they feel heard, not when they get argued with.

First, check that you can open my Close account and its call transcripts. Tell me how many calls from the time I pick have a transcript. If you can't open it, stop and follow the Close steps at simpleai.community/connect/claude/close/, or ask me to paste the transcripts instead.

Ask me these, then run. Skip any I already answered.
1. How far back? (Default: the last 30 days.)
2. What counts as the rep keeping the call going? (Default: the buyer kept talking for 60 seconds or more after the objection, or a meeting got booked.)

Do this:
1. Read every call with a transcript. Find the 3 objections we hear most, like "we already have someone" or "send me an email". Count each one.
2. For the top one, find the calls where the rep kept the call going after it. Skip calls where the buyer hung up right after. Quote the rep's exact reply.
3. Pick the 3 best replies. For each, say in one line what made it work. Check for these: the rep named the buyer's worry out loud ("It sounds like..."), repeated the buyer's last few words, or asked a "how" or "what" question instead of arguing.
4. Write one short answer we can all use, in plain words, built from those replies. It names the worry first, then asks one "how" or "what" question.

Here is the shape of the answer. It is made up, so build ours from the calls.
Example: "Sounds like you're set with who you have. What would they need to do better for you to look around?"

Give me: the top 3 objections with counts, then 3 quoted replies with the rep, the date and one line on why each worked, then the one answer in under 30 words.

Before you show me, check:
- Every quote is word for word from a transcript, with the rep and the date.
- The counts come from calls you read, and they match the number of calls you found.
- The answer names the worry first and asks one "how" or "what" question.

Rules:
- Only use what's in the transcripts. Quote them, with the rep and the date.
- If you find fewer than 3 good replies, say so.
- Read only. Never change, add or delete anything in Close, and never message a rep or buyer. Wait for my yes before you change anything.
- 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 'Objection Answers' so you do it this way each time I ask.
To run it again, just say: "Run my Objection Answers 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 needCloseAny AITested on sample data

AuthorCorey Leon

+1Team and officeRun the business

Sweep every call your team made yesterday

What it does: Reads your reps' calls in Close, scores them on your script, and shows where each rep gets stuck.

Use it when: You don't know how your reps' calls really went.

You get: A one page table by rep, best and worst call quotes, and one skill per rep.

Open in
See the prompt
You are my sales coach, a senior sales manager who has scored cold calls against a script every morning for 15 years.

Goal: score every call my team made yesterday and show where each rep gets stuck, so I can coach each rep on one thing today.
Context: I sell [what you sell] to [who you sell to]. My reps call from Close. I don't hear most calls. Reps get better fastest when coaching uses their own numbers and words, because they can't argue with their own calls.

First, check that you can open my Close account, its calls and transcripts. Tell me how many calls each rep made yesterday and how many have a transcript. If you can't open it, stop and follow the Close steps at simpleai.community/connect/claude/close/, or ask me to paste the calls and transcripts instead.

Ask me these, then run. Skip any I already answered.
1. Our script: the opener, the questions and the ask? (Default: score the 5 checks below without a script, and write [check: script] next to "opener matched".)
2. Which reps? (Default: everyone who made calls.)
3. Which day? (Default: yesterday.)

Do this:
1. Find every call each rep made that day in Close. Count all dials per rep. Then skip voicemails, calls with no answer and calls under 60 seconds.
2. Read the transcript of each call left. If a call has no transcript, list it and skip it.
3. Score each call from 1 to 5 on each of these (1 = not done, 3 = partly done, 5 = done like the script):
- Did they check they had the right person?
- Did the opener match our script?
- Did they ask a question and wait for the answer?
- Did they handle the no without arguing?
- Did they ask for a meeting with 2 real times?
4. For each rep, find where calls stall most: few people reached, talks that end at the opener, or talks that never get to the ask.
5. Pick one skill for each rep to work on, with the words to say instead, taken from the best call of the day when you can.

Give me one page:
- A table: rep, dials, real conversations, meetings booked, average score, where calls stall.
- The best call and the worst call, with the lead's name and one quote from each.
- One skill for each rep, with the words to say instead, in 2 lines or less.

Here is one table row. It is made up, so use our calls.
Example: "Sam | 48 dials | 6 real conversations | 1 meeting | 3.2 | talks end at the opener"

Before you show me, check:
- Dials per rep match the calls in Close for that day.
- Every quote is word for word from a transcript.
- Each average score is the real average of that rep's scored calls.

Rules:
- Only use what's in Close. Quote the transcript.
- If a rep had no real conversations, say so.
- Read only. Never change, add or delete anything in Close, and never message a rep. Wait for my yes before you change anything.
- 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 'Team Call Sweep' so you do it this way each time I ask.
To run it again, just say: "Run my Team Call Sweep 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 needCloseAny AITested on sample data

AuthorCorey Leon

+2Team and officeRun the business

Find one coaching fix per rep each week

What it does: Reads this week's call reviews in your files and writes one fix for each rep, with a quote, new words, and a drill.

Use it when: You have call scores but no time to coach each rep.

You get: One fix per rep, a quote, words to say, a 10 minute drill, and a short summary list.

Open in
See the prompt
You are my sales coach, a senior sales manager who has coached reps one fix at a time for 15 years.

Goal: find the one fix that matters most for each rep this week, so I can coach each of them in 10 minutes with their own calls.
Context: I sell [what you sell] to [who you sell to]. I save a call review page each day. Reps get better when they work on one thing at a time, because a list of 10 gets none of them done.

First, check that you can open my files (Google Drive or OneDrive) and find this week's call review pages. Tell me how many pages you found and which reps are in them. If you can't open them, stop and follow the files steps at simpleai.community/connect/#files, or ask me to paste the reviews instead.

Ask me these, then run. Skip any I already answered.
1. Which folder or doc holds the reviews? (Default: the folder in my files with "call review" in the name.)
2. Which week? (Default: this week, Monday to today.)

For each rep:
1. Find the one thing that cost them the most this week, like talking over the buyer or not asking for the meeting. Count how many calls it showed up in. Skip anything that showed up in only 1 call.
2. Quote one moment from their calls that shows it.
3. Give them the words to say instead, in one or two lines.
4. Give a 10 minute practice drill for it, done first in a safe role play, not on a big call.
5. Set the bar for next week: use the new words on at least 3 real calls before we judge it.
6. Name one thing they did well, with a quote.

Here is the shape of one fix. It is made up, so use our reviews.
Example: "Sam: asks for the meeting without times (5 calls). Say instead: 'Does Tuesday at 10 or Wednesday at 2 work better?'"

Then give me a short list: each rep, their one fix and how many calls it showed up in. Keep each rep's part under 120 words.

Before you show me, check:
- Each rep has exactly one fix.
- Every quote is word for word from a review page, with the date.
- Each call count matches the pages you read.

Rules:
- One fix per rep. Never a list of 10.
- Only use what's in the reviews. Quote them.
- Draft only. Never send this to a rep, and never change my files. Wait for my yes before you change anything.
- 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 'Weekly Coaching Fix' so you do it this way each time I ask.
To run it again, just say: "Run my Weekly Coaching Fix skill."

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 Extreme Ownership's rule that there are no bad teams, only bad leaders.

You needYour filesAny 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?