Objection handling role play: how to write the scenario

Short answer

An objection role-play scenario is written in five parts: the surface words of the objection, the real reason behind it, the moment in the conversation it appears (the trigger), how the customer reacts to a good and a weak answer, and a description of a good answer. Without these five, the AI customer simply repeats the objection and the employee memorises a stock line — no skill is built.

This article is for the manager or enablement specialist preparing training. How a seller answers an objection is a separate topic; here we show how the scenario itself is built.

Why an objection list is not enough

In many companies objections are documented like this: "too expensive" in the left column, a stock answer in the right. That table is useful for knowledge, not for practice. When a real customer says "too expensive" they mean different things: the budget is short, they do not see the value, they have another offer, or they are simply testing for a discount. A stock answer fits only one of these.

The purpose of the scenario is to train the employee to ask a clarifying question, not to recite an answer. So the reason behind the objection should be hidden in the scenario and revealed only after the right question.

The five parts of a scenario

1. 11. Surface wordsWhat the customer says first: "too expensive", "no time", "we don't need it", "send me an email".
2. 22. Real reasonWhat sits behind the words: "a bad experience with another supplier last year", "I'm not the one who decides", "the budget is closed this quarter". The AI customer says this only after a clarifying question.
3. 33. TriggerWhen the objection appears: when the price is mentioned, when a meeting is proposed, in the first 20 seconds. The trigger lets the employee see what provokes the objection.
4. 44. Reaction ruleWhat the customer does after a good answer (softens, reveals the reason, moves on) and after a weak one (repeats the objection, hardens, ends the conversation).
5. 55. Description of a good answerNot a stock line but behaviour: acknowledge, ask for the reason, answer the reason, check it is resolved. Scoring relies on this description.

Intensity levels

The same objection can be written at different difficulty. Three levels are enough:

• Soft: the customer objects once and reveals the reason after the first clarifying question.
• Medium: the customer objects twice, reveals the reason only after a second good question, and hardens once after a weak answer.
• Hard: two different objections come in sequence (price, then timing, say), the customer creates time pressure, and ends the conversation after a weak answer.

A template

The scenario below is illustrative. Adapt it to your product.

• Profile: owner of a small logistics company looking for a CRM.
• Surface words: "We don't need it yet, we work in spreadsheets".
• Real reason: they installed a system last year and the team never used it; they are afraid of wasting money again.
• Trigger: when the employee starts listing the system's features.
• Reaction to a good answer: if the employee asks "what works well in your spreadsheets now, and what causes trouble?", the customer talks about the previous experience.
• Reaction to a weak answer: if the employee keeps listing features, the customer says "send me an email" and ends.
• Description of a good answer: acknowledge the objection; ask about the current process; uncover the failed past experience; answer the concern about team adoption (a narrow start, for example); agree a short demo or pilot with a date.

Linking the scenario to the profile

A scenario lives inside a profile. Of the eight fields described in the AI customer profile article, "objections", "knowledge", "end condition" and "good-conversation standard" are the core of the scenario. You can write two or three objections into one profile, but for the first sessions it is better to start with one main objection — the employee knows clearly what they are practising.

Testing the scenario

1. 1Test with a weak answerGive the stock answer immediately and ask nothing. The AI customer should not reveal the reason.
2. 2Test with a good answerAsk a clarifying question. The customer should reveal the reason and the conversation should move forward.
3. 3Look at the scoringIs the difference between the two conversations' scores clear? If not, the description of a good answer is not precise enough.
4. 4A second pair of eyesAsk an experienced seller: does this objection, and its reason, happen like this in real life?

Common mistakes

• Leaving out the reason — the customer just repeats "too expensive".
• Writing a stock line instead of a good answer — scoring compares words, not behaviour.
• A scenario where the customer gives in too easily — the employee always wins and learns nothing.
• A scenario where the customer is artificially harsh — no answer works and the employee loses heart.
• Five objections in one scenario — the point of the practice gets lost.

Illustrative example: insurance

This is not a real customer case. An insurance manager writes a scenario for the "I already have insurance" objection. In the first version no reason is given, and the AI customer repeats the same sentence every time; the team memorises a stock answer. In the second version a reason is added: the customer's existing policy covers only the mandatory part, and they do not know it. Now only an employee who asks "what does your current policy cover?" can move the conversation forward. The manager sees in the reports that half the team did not ask it in the first week — and the next meeting's topic is set.

Limitations

A scenario does not cover every variation of a real customer; it isolates one skill for practice. The AI customer can sometimes stray from the scenario — revealing the reason too early, for example, or inventing an extra objection. So test a new scenario before giving it to the team, and collect employees' feedback.

Scenarios in Vexvon AI Training

In Vexvon AI Training the parts of a scenario map onto the customer profile's fields: customer behaviour, the objection list, sales notes (the scenario's context) and the good call script (the standard). After the conversation, objection handling is scored as its own criterion with an explanation, and a better version of a weak reply is shown. The company can change the list of criteria and their weights to match its own sales approach.

Next step

Take the objection your team hears most and write the five parts for it — especially the "real reason" line. More articles are in customer simulation and scenarios; to review your scenario together, contact us.

Further reading on this topic: objection handling training, price objection sales training.