A sales call prep AI agent template is a reusable set of instructions that tells an agent which upcoming meetings to prepare, what to read about each account, and what the brief should contain. The five below cover first discovery calls, follow-up meetings, stakeholder gaps, demo prep, and briefs for a leader joining a call. Each one is ready to paste, with its trigger, inputs, and what good output looks like.
If your reps still prep by scrolling through last month’s call notes in the five minutes before a meeting, you are not alone. The context exists. It is spread across recordings, email threads, and CRM fields that nobody has time to reread before every call.
Why does call prep get skipped?
Call prep gets skipped because it competes with everything else on a rep’s calendar, and it is the one task nobody checks. Salesforce’s 2024 State of Sales report, a survey of 5,500 sales professionals, found that reps spend 70 percent of their time on non-selling tasks. Prep for the next call is usually what gives way.
The cost shows up in the meeting. A rep who walks in without the last recap asks questions the buyer already answered, misses a promise made two calls ago, and treats a new attendee as a stranger. Buying groups now run from five to 16 people across as many as four functions, according to Gartner, so every meeting tends to bring someone new into the room.
An agent does not need to find time. Give it a schedule, a clear scope, required evidence, and a fixed brief format, and it prepares every meeting on the calendar. The structure is the same one behind our sales AI agent templates for open deals. The five below apply it before the call instead of after it.
Template 1: How do you prep for a first discovery call with AI?
What it does. Writes a short brief before a first meeting with a new account, so the rep opens with a relevant question instead of a company overview they read on the website.
When it runs. Every weekday morning, for every first external meeting booked that day.
Instructions.
For each first meeting booked today with an account that has no previous calls, write a discovery brief:
1. What the account does and how it makes money, in two sentences.
2. How the meeting was booked: the inbound form, outbound email thread, or referral, with any pain the contact already named. Quote it and give the date.
3. Each attendee: title, likely role in a buying decision, and any past contact with our company.
4. Two hypotheses about why they might buy now, each tied to something you can point to.
5. Four discovery questions that test those hypotheses.
Mark anything you are inferring as "inferred". Keep it under 300 words.Inputs. The calendar invite and attendees, the CRM account and contact records, the email or form history that booked the meeting, and public information about the company.
Good output. The rep can skip the first ten minutes of “tell me about your business” and go straight to the problem. The “inferred” label matters most, because it keeps a guess from turning into a fact the rep repeats on the call. The Prepsheet Builder agent profile covers more of what a prep sheet can hold.
Template 2: How do you recap the last call before a follow-up meeting?
What it does. Rebuilds the thread of the deal before a returning meeting: what was said, what was promised, and what is still unanswered.
When it runs. Every weekday morning, for every meeting booked today with an account that has at least one previous call.
Instructions.
For each meeting today with an account we have spoken to before, read the last three calls, the email thread since the last call, and the deal's CRM fields. Write a brief with:
1. The goal of today's meeting, based on the agreed next step from the last call.
2. What the buyer told us last time that matters for today, with a short quote and the date.
3. Open commitments on both sides: what we promised to send or do, what they promised, and whether each one happened.
4. Questions the buyer asked that we have not answered yet.
5. Anything in the CRM that contradicts the calls, such as a close date or stage that no longer fits.
Skip sections that have nothing to report. Keep it under 250 words.Inputs. Call transcripts and summaries, email history, and CRM fields for stage, close date, and next step.
Good output. The rep opens with “last time you mentioned” and closes out a promise before the buyer has to chase it. Item five doubles as light CRM hygiene, because a mismatch flagged in a brief tends to get fixed the same day.
Template 3: How do you spot stakeholder gaps before a key meeting?
What it does. Checks who is coming to the meeting against who has shaped the deal so far, and flags the roles that are missing.
When it runs. Every weekday morning, for meetings today on deals past the discovery stage.
Instructions.
For each meeting today on a deal past discovery, compare today's attendees with everyone who has appeared on calls or emails for this deal. Report:
1. New attendees we have not met, with title and a suggested reason they are joining.
2. People who were active earlier but have not appeared in 30 days.
3. Roles we have not engaged at all: economic buyer, technical evaluator, procurement, legal, or security.
4. Whether only one buyer contact has been active in the last 30 days.
For each gap, suggest one question or ask the rep can make in this meeting. Skip deals with no gaps.Inputs. Calendar attendees, call attendees and transcripts, email participants, and contact roles from the CRM.
Good output. A short list of names and asks, not a full stakeholder map. The single-contact check matters most, because one active contact means one departure can stall the deal. If you want a standing map rather than a per-meeting check, the Stakeholder Mapper profile shows how teams track it over the whole cycle.
Template 4: How do you tailor a sales demo to what the buyer said in discovery?
What it does. Turns discovery calls into a demo plan, so the demo follows the buyer’s problems in their order instead of the standard click path.
When it runs. Every weekday morning, for meetings today whose title or calendar description mentions a demo.
Instructions.
For each demo meeting today, read every discovery call and email on the deal. Write a demo plan with:
1. The buyer's top three problems, in their words, with the call and date each came from.
2. For each problem, the part of our product that addresses it, and the outcome to show.
3. What to leave out, because nobody on the buyer's side has asked about it.
4. Objections or concerns raised so far, and where in the demo to address each one.
5. The success criteria the buyer described, so the rep can close by checking against them.
Keep the plan to one screen.Inputs. Discovery call transcripts, email history, the attendee list, and a short description of your product areas.
Good output. A demo that opens on the buyer’s biggest problem and ends on their own success criteria. A demo that tours features nobody asked about spends the buyer’s attention on the wrong things, which is why item three tells the rep what to cut.
Template 5: How do you brief a manager who is joining a sales call?
What it does. Writes a one-page brief for a sales manager or executive joining a call, so they arrive knowing the deal and their role in the meeting.
When it runs. Every weekday morning, for meetings today where a manager or executive from your team is on the invite.
Instructions.
For each meeting today that includes a manager or executive from our team, write a one-page brief for that person:
1. Why this buyer is looking, in one sentence, with a quote.
2. Where the deal stands: stage, close date, and the agreed next step.
3. Who will be in the room on the buyer's side and what each person cares about.
4. The top two risks, each with evidence and a date.
5. The one thing the rep needs from the leader in this meeting, based on the deal notes. If it is not clear, say so.
Write for someone who has never seen this deal. Keep it under 250 words.Inputs. The calendar invite, call transcripts and attendees, email history, CRM deal fields, and your user list so the agent knows who counts as a manager or executive.
Good output. The leader joins as a planned part of the deal, not a surprise guest. Item five matters most. If the brief says the ask is unclear, the rep and the leader have a reason to talk for five minutes before the call, which is the conversation most ride-alongs skip.
How do you roll out call prep agents without flooding inboxes?
Start with Template 2. Follow-up meetings make up most of a rep’s calendar, the output is easy to judge, and reps feel the difference on their next call. Read the first week of briefs with two or three reps and tighten the instructions wherever the agent missed a promise or quoted the wrong call.
Deliver each brief to the rep who owns the meeting, not a shared channel. A brief only helps the person walking into the room, and a channel full of other people’s prep trains everyone to ignore it. Send early runs to an in-app history, then route them to email or Slack once the format is stable.
Then check the inputs. A stakeholder gap check cannot work without contact roles in the CRM, and a follow-up recap is only as good as the share of calls you record. If your team also wants briefs for live customers, the customer success AI agent templates include one for QBR prep.
Where Airspeed fits
Every template above runs as written in Airspeed Agents. Airspeed already captures your calls, transcripts, emails, and CRM fields, so each brief starts from the full history of the account instead of a blank context window. You pick the trigger (a schedule, a finished call, a deal stage change, or a web trigger), paste the instructions, and send the output to Slack, email, or in-app history, scoped to each owner’s own accounts. If you would rather not write prompts at all, Airspeed Call Prep builds a briefing before each call on a schedule, with the context shaped for the role you are meeting.
If you want to see these briefs running on your own calendar and calls, book a demo.
Frequently asked questions
How do you prep for a sales call with AI?
Give an AI agent access to the account's past calls, emails, and CRM fields, then have it write a short brief on a schedule before each meeting. A useful brief recaps what the buyer said last time, lists open commitments on both sides, names who is attending and what each person cares about, and suggests a few questions. The rep reads it in two minutes instead of rebuilding context from memory.
What should a sales call prep brief include?
The goal of the meeting, a recap of the last conversation with quotes and dates, open action items and who owns them, the attendees with their role and past involvement, gaps in what you know about the deal, and three or four questions to close those gaps. Anything the brief claims should point back to a call, email, or CRM field so the rep can trust it.
When should a call prep agent run?
Run it on a schedule early in the working day for every external meeting booked that day, or a set time before each meeting. Morning runs suit most teams because the brief is waiting before the first call, and the rep can follow up on gaps, such as an unknown attendee, before the meeting rather than during it.
Can an AI agent prep a manager who is joining a sales call?
Yes. A ride-along brief gives a manager or executive a one-page view of the deal before they join, covering why the buyer is looking, where the deal stands, who will be in the room, the risks, and the one thing the rep needs them to do. It saves the internal prep meeting that usually happens in the hallway five minutes before the call.
What data does a call prep agent need?
Recorded calls with transcripts and attendees, the email history with the account, and CRM fields such as stage, close date, owner, and contact roles. Calendar data tells the agent which meetings are coming up. Without recorded calls the brief can only repeat CRM fields, which are usually the least current source of what the buyer said.
