Indecisive buyer role play: practising "I'll think about it"

Short answer

Practice with a customer who says "I'll think about it" targets three skills: politely uncovering the real reason for the hesitation, answering that reason without pressure, and ending the conversation with a concrete, dated next step. "OK, have a think, I'll call you later" is the most common reply and the least productive — neither the customer nor the employee knows where the conversation stands.

Indecision is different from an objection: the customer is not saying "no"; they are postponing the decision. So practice profiles should be built around the different reasons for hesitating.

What sits behind "I'll think about it"

1. 1Missing informationThe customer has not understood something but is embarrassed to ask, or does not know what to ask.
2. 2Someone else decidesA spouse, a director, the finance team. The customer cannot commit before talking to them.
3. 3ComparingWaiting for another offer, or has not looked at it yet.
4. 4Fear of riskAfraid of the wrong choice, of wasting money, of repeating a past bad experience.
5. 5A polite "no"No interest, but not wanting to say so openly.

The employee's job is to work out which of these five it is with one or two questions. Each reason has a different answer: explanation when information is missing, bringing in the decision-maker, giving criteria for a comparison, a risk-reducing term when risk is the fear, and an honest close for a polite "no".

Uncovering without pressure

Uncovering the reason needs questions that help the customer think, not an interrogation. Examples:

• "Of course. As you think it over, what is the most important question for you?"
• "Are you deciding on your own, or will you talk it through with someone?"
• "Are you looking at other options too? Which criterion matters most for comparing?"
• "What concerns you most — price, timing, or the result?"

A dated next step

With a hesitant customer the most important outcome of the conversation is not a sale but a clear next step. "I'll call you later" is not a step. A step sounds like: "Shall I call on Thursday at 11, after you've spoken to your spouse, to answer any questions?" It has a date, a time and a purpose.

The quality of that later call — whether it continues the previous conversation — is a separate topic; see follow-up call quality.

Weak and good answers side by side

The dialogue fragments below are illustrative. Customer: "The offer is interesting, but let me think a little."

• Weak answer: "Of course, no rush. Call me whenever you decide." No reason is uncovered, the next step is in the customer's hands, and the employee does not know where the conversation stands.
• Pressure answer: "This price is only valid this week, then it goes up." If untrue, it destroys trust; even if true, it does not address the reason.
• Good answer: "Of course. As you think it over, what's on your mind most — the price, or whether you'll see the result?" Once the customer names the reason, the employee answers it and asks: "Shall I give you a short call on Wednesday so we can close the remaining questions together?"

The difference is not elegant wording: in the good answer the reason is asked for and the conversation ends at a specific time. These are exactly the two behaviours the practice scores.

Four practice profiles

• "I need to talk to my spouse": hidden reason — someone else decides. A good conversation ends by inviting the second person to the next conversation.
• "I'm still looking elsewhere": hidden reason — comparison. In a good conversation the employee sets the comparison criteria together with the customer.
• "Let me think a little": hidden reason — fear of risk, a past bad experience. In a good conversation the employee asks about the experience and offers a real risk-reducing term (a trial, a warranty, a phased start) — only if it actually exists.
• "Interesting, I'll get back to you": hidden reason — a polite no. A good conversation ends with an honest question and respect for the customer's time.

The profile structure follows the eight fields in the AI customer profile; the "end condition" matters most here — after which answer the customer agrees to a dated step.

What to look at when scoring

1. 1Was the reason uncoveredDid the employee identify the reason for hesitation, or agree immediately?
2. 2Does the answer fit the reasonDid they explain when information was missing, bring in the decision-maker when someone else decides?
3. 3Was there pressureFalse urgency, excessive insistence, or interrupting the customer?
4. 4Is the step concreteDid the conversation end with a date, a time and a purpose?

Illustrative example: a renovation company

This is not a real customer case. Managers at a flat-renovation company often hear "let me talk to my spouse" and end with "fine, I'll wait". The manager builds a profile for this situation: the customer decides jointly, and the spouse is worried about the budget. The standard has one requirement: the conversation must end with a dated meeting or call the second person will join. In the first week the reports show that more than half the managers skip this step; at the team meeting two sentences are practised: "What question will your spouse most likely have?" and "Which day suits you both to talk together?"

Common mistakes

• Taking "I'll think about it" as agreement and ending the conversation.
• Offering a discount straight away without asking the reason.
• Creating false urgency.
• Telling the customer to "explain it to them" instead of bringing the decision-maker in.
• An undated "I'll call you later".

Limitations

Some customers genuinely need time, and that is normal; the aim of practice is not to turn every hesitation into a sale but to end the conversation in a clear state. The AI customer may sometimes reveal the hidden reason too early or too late — test the profile's end condition. A practice result does not on its own prove that behaviour has changed in real conversations.

This profile in Vexvon AI Training

On the Vexvon AI Training product page, the customer "who cannot decide" is one of the sample profiles. The company builds the profile for its own customer type, and the employee practises in a Telegram chat or on a test call. Needs discovery and next step are separate scoring criteria; the report ties a weak reply to a specific message and shows a better version.

Next step

Sort your last ten "I'll think about it" conversations by the five reasons and write a profile for the most common. Other scenarios are in customer simulation and scenarios; the price objection, for example, often arrives together with hesitation. To build your profile together, contact us.

Further reading on this topic: sales closing training, objection handling role play.