Guides
How to run a mock sales call that actually trains reps: a seven-step setup, six scenarios with buyer briefs, an example exchange, and a scoring rubric.
Published
A mock sales call is a timed practice conversation in which a rep runs a real sales call from start to finish against someone playing the buyer, then gets scored against a rubric that was written before the call started. Done well, it is the closest thing to a live call that costs nothing when it goes wrong. Done badly, it is a manager reading lines off a page while the rep performs for an audience. The difference comes down to three things: a believable buyer brief, a rubric with observable behaviors, and a debrief that ends with one thing to change on the next attempt.
This guide is for sales managers and enablement leaders who want mock sales calls to be a repeatable exercise rather than an occasional event. It covers how to run one, six example scenarios with buyer briefs, a short example exchange with scoring notes, and a five-skill scoring rubric you can copy.
A mock sales call tests whether a rep can do the job in conversation, not whether they know the material. Thoughtly's glossary defines sales role-play as a practice conversation in which a seller rehearses a sales situation with someone acting as a buyer. A mock call is the most structured version of that: one full call, one buyer, one goal, one score.
That makes it different from the neighbors it often gets confused with:
Our recommendation: treat the mock sales call as a measurement, not a performance. If the rep knows exactly what they will be scored on and still cannot do it, you have learned something specific. If they are guessing at the standard, you have only learned how comfortable they are on stage.

Most mock calls go wrong before anyone speaks. The buyer is improvised, the standard is invented afterward, and the call runs long because nobody set a limit. Fix the setup and the call takes care of itself.
The single most useful habit here is step 7. A mock call that happens once is a quiz. A mock call that repeats until the standard is met is training.
A good mock sales call has three roles, even if one person covers two of them.
When a manager plays the buyer and scores at the same time, the scoring suffers. If you only have two people, record the call where your policies allow it and score from the recording afterward.
Use these as starting points and rewrite each brief with your own product, buyer, and competitors. Each one lists the setup, the buyer brief, and what a passing call looks like. For full scripts and more situations, see the sales role play scripts guide.
Setup: an inbound lead booked a call after downloading a guide. Buyer brief: operations manager at a mid-sized company, curious but not urgent, uses a patchwork of spreadsheets and an older tool, will share details freely if asked open questions. Hidden fact: their team missed a target last quarter because of the problem your product solves. A passing call: the rep uncovers the missed target through follow-up questions, connects it to a cost, and agrees a next step with a date. Start new reps here, and pull questions from our sales discovery questions guide.
Setup: a cold callback the buyer did not plan for. Buyer brief: "I have one minute. Why should I care?" Busy, polite, will hang up if the rep launches into a feature list. A passing call: the rep gives a one-sentence reason grounded in the buyer's role, asks permission for one question, and either earns a longer meeting or exits gracefully with a specific follow-up.
Setup: a second call after a demo that went well. Buyer brief: "We like it. But it's over budget," and "Our current provider costs less. Why switch?" The buyer has real budget pressure but also a real problem with the current provider. A passing call: the rep does not discount in the first answer, asks what is taking more work than it should today, and reframes the conversation around the cost of the status quo. Our guide on how to handle sales objections has more responses to practice.
Setup: a senior leader joins late in the deal. Buyer brief: "What would actually change for us?" Skeptical of vendors, short on time, has seen similar tools fail before. Will interrupt a long pitch. A passing call: the rep summarizes what they have learned from the team in two sentences, ties it to an outcome the executive owns, and asks what would make this a priority for them.
Setup: an existing customer hears about a new product or feature. Buyer brief: "How is this different from what we use now?" Happy with the current setup and wary of change. A passing call: the rep asks how the buyer works today before explaining anything, then describes the difference in the buyer's terms rather than the release notes.
Setup: a champion who was enthusiastic three weeks ago has gone quiet. Buyer brief: still likes the product, but a new priority landed from above and they are not sure the deal survives it. Will not volunteer this unless the rep asks directly and makes it safe to answer. A passing call: the rep names the silence without blame, finds out what changed, and agrees a realistic next step, even if that step is a later date.
Here is a brief excerpt from scenario 3, the price objection, with the kind of notes an observer should write.
Buyer: "Honestly, our current provider costs less. Why would we switch?"
Rep: "That's fair, and switching has a cost of its own. Before I answer, can I ask what is taking more work than it should with your current setup?"
Buyer: "Reporting, mostly. My team rebuilds the same spreadsheet every Monday."
Rep: "How long does that take, and who does it?"
Buyer: "Two people, most of the morning."
Observer notes: the rep acknowledged the concern without arguing, asked a relevant question instead of defending the price, and followed up for a number. Score on handling objections: strong. Missed opportunity: the rep did not confirm whether the Monday rebuild had ever caused a mistake or a delay, which is where the real cost usually sits. Next attempt: ask one more question about the consequence before moving to value.
Notice what the notes do. They quote what was said, tie it to a rubric skill, and end with one concrete change. That is the whole job of an observer.
The constraint on mock sales calls is rarely the format. It is people. Every mock call needs someone to play the buyer, and the best buyers are usually your strongest reps and managers, who are also the people with the least free time. Lira's sales training management page puts it plainly: track participation and completion "rather than relying on a calendar of mock calls."

Lira is an AI roleplay platform built for that gap. Reps hold a spoken conversation in the browser with an AI buyer that responds to what they say, get feedback, and try again. Based on its current product pages and help center:
Lira does not need a CRM integrationCRM integrationA CRM integration connects an agent or communications platform with a CRM so the systems can exchange records, events, and actions. or past call recordings to get started. It is a practice product, not a dialer or call recorder, and it does not replace the manager: Lira's own pages note that AI feedback can be imperfect and that managers can review shared results and add their own coaching. Thoughtly gets your leads ready for your reps. Lira gets your reps ready for your leads.
See how Lira runs mock sales calls at scale
A rubric only works if two different managers would give the same call roughly the same score. That means describing behaviors, not qualities. "Asks about the buyer's current workflowWorkflowA workflow is a defined sequence of steps, decisions, actions, delays, and outcomes used to complete a business process. and its impact" can be scored. "Great discovery" cannot.
Here is a five-skill rubric that fits most first and second calls. Score each skill from 1 to 5, using the anchors for 1, 3, and 5.
| Skill | Weight | 1: Not yet | 3: Developing | 5: Ready |
|---|---|---|---|---|
| --- | --- | --- | --- | --- |
| Opening and agenda | 15% | Launches into a pitch with no reason for the call | States a purpose but does not confirm the buyer's time or goals | Sets a clear purpose, confirms time, and invites the buyer to add to the agenda |
| Discovery | 30% | Asks closed or scripted questions and moves on | Asks open questions but rarely follows up | Follows up for specifics and consequences, and summarizes what was learned |
| Objection handling | 20% | Argues, discounts, or ignores the concern | Acknowledges the concern but answers before understanding it | Acknowledges, asks a clarifying question, then responds to the real concern |
| Value and positioning | 20% | Lists features unrelated to anything the buyer said | Links some features to the buyer's situation | Ties the product to a specific problem and cost the buyer described |
| Next step | 15% | Ends with "I'll send something over" | Proposes a next step without a date or the right people | Agrees a specific next step, date, and attendees with the buyer |
Discovery carries the most weight because it drives everything else: a rep who learns the real problem will position better and handle objections better. Adjust the weights for the call you are practicing. A late-stage negotiation scenario should weight objection handlingObjection handlingObjection handling is the process of understanding and responding to a buyer's concern during a sales conversation. more heavily, and a cold callback should weight the opening.
Set a passing bar before the cohort starts. A reasonable starting point is an average of 3.5 or higher with no skill below 3, and the goal of the call achieved. Require it in one attempt, not stitched together from good moments across several calls.
Score every rep against the same rubric with Lira
The fastest way to lose reps' trust in mock calls is inconsistent scoring. If one manager passes a call that another would fail, reps learn to game the scorer instead of improving the skill.
Run a short calibration before you use a new rubric across teams. Have three or four managers score the same recorded call independently, compare scores skill by skill, and talk through any gap of more than one point. Usually the disagreement is about what a word in the rubric means, and the fix is a sharper anchor. Repeat calibration whenever you add a new scenario or a new manager joins.

A few rules keep scoring honest:
The debrief is where the improvement actually happens, and it is the part most often skipped when calendars get tight. Keep it short and structured so it survives a busy week.

One change per debrief is the rule that matters most. A list of seven things to fix produces a rep who fixes none of them. Save the rest for the next attempt, when the first change has stuck.
Use this before every mock call:
Give every rep more mock calls without more manager hours
Ten to fifteen minutes covers most first calls, discovery calls, and objection scenarios. Longer calls make sense for full demos or late-stage negotiations, but set a limit either way. The debrief should take about 10 minutes on top of that.
New reps benefit from several short attempts a week during onboarding, ideally repeating the same scenario until they pass it. Tenured reps get more value from targeted mock calls before a product launch, a pricing change, or a high-stakes meeting than from a fixed weekly schedule.
Sales role-playSales role-playSales role-play is a practice conversation in which a seller rehearses a sales situation with someone acting as a buyer. is the broad practice of rehearsing a sales situation with someone playing the buyer. A mock sales call is a structured form of role-play: one complete call, one buyer brief, a time limit, and a score against a rubric written in advance.
Yes. With a platform like Lira, a rep speaks with an AI buyer built from a scenario you define, at a difficulty you choose, and gets feedback against your rubric. AI feedback can be imperfect, so managers should still review shared attempts and add their own coaching. AI practice adds repetitions; it does not replace the manager.
No. Teams can start Lira with their product knowledge and training goals. A CRM integration, past call recordings, or Thoughtly's lead-facing agents are not required to begin.
A mock sales call is only as good as its setup. Pick one real conversation, give the buyer a brief worth playing, write the rubric before anyone speaks, keep the debrief to one change, and repeat the scenario until the rep meets the standard in a single attempt. The constraint is usually not willingness but buyers to practice against, which is the part Lira takes off your managers' calendars.