Rehearse difficult customer conversations with AI

What prompted this idea?

What could a small team practise?

Start with a conversation your staff already recognise. It might involve a delayed delivery, an unclear quote or a customer who has received conflicting information. Ask an experienced colleague which question usually reveals what the customer actually needs.

For the event-hire example, the customer needs to know whether to change their setup plans. The staff member should establish the event’s timing, check the latest delivery information and explain when someone will call back. A calm voice helps, but the review also needs to cover the accuracy of what was promised.

Our interpretation is that a short rehearsal could make an unclear procedure easier to spot. If nobody can say who checks with the driver or who may approve a replacement delivery, settle that with the team before asking a new colleague to practise it.

Prepare the situation before opening the tool

Use a made-up booking with a clear starting point. In this example, the chairs were expected at 10 am, guests arrive at midday and the depot has not yet confirmed a revised delivery time. Give the staff member the contact route for the dispatch lead and the follow-up process you want them to use.

Keep the exercise separate from live bookings. Provide fictional names and reference numbers, and use an AI tool your business has approved for staff training. A typed conversation is a reasonable starting point. If the chosen tool supports voice, you can also practise speaking the response.

A trial brief could read as follows.

• Play a customer calling an event-hire company about chairs that have not arrived. You expected them at 10 am and your guests arrive at midday. You are worried about having enough time to set up.
• Wait for the staff member’s response after each short turn. Answer their questions using the scenario facts. If they give an unclear answer, ask a natural follow-up question.
• Keep the conversation within this scenario. Stop when the trainer says to pause. Afterward, show the statements where the staff member promised a time or action so we can review them together.

Review the decisions made during the call

Ask the experienced colleague to check whether the staff member understood the customer’s timing, distinguished confirmed information from an estimate and agreed on a specific next contact. Read any extracted promises against the actual exchange because the AI’s summary also needs checking.

Give feedback on a sentence the person actually used. For example, “I’ll get that there by eleven” needs a different discussion from “I’ll contact dispatch now and call you back in ten minutes.” The second promise still needs to fit a process the team can carry out.

Let the learner try the difficult part again after the feedback. If the AI invents a new booking condition or suddenly accepts an unrealistic promise, pause and reset that turn. Record the issue with the exercise so the next person receives a more consistent scenario.

Use the rehearsal to support coaching. An AI-generated score alone gives a manager little basis for judging how someone will handle real customers. Keep the review focused on observed responses and the business’s agreed procedure.

What can you do this week?

• Choose one recurring customer conversation and ask an experienced staff member to describe where it usually becomes difficult.
• Write a fictional scenario with the facts the customer knows, the facts staff can confirm and the person who can help with an exception.
• Agree on three things to observe, such as clarifying the deadline, checking the current record and making an achievable follow-up promise.
• Run a short rehearsal, pause for specific feedback and repeat the part that needs work. Note any invented facts or unhelpful behaviour from the AI.
• Ask the learner and reviewer whether the exercise was worthwhile. Update the procedure or scenario before deciding whether to try another conversation.

Decide what deserves another rehearsal

After a few sessions, look for repeated questions. If staff keep struggling to explain a delivery window, the website wording or confirmation email may need attention. If the handover is unclear, the team may need an agreed contact route more than another practice session.

Build a small set of scenarios only if people use them. Review the examples when delivery terms, products or responsibilities change. Keep a date and an owner on each exercise so outdated instructions are easy to identify.

How Context Aware can help

We can help document a customer process, identify the information staff need and prepare a small rehearsal around it. We can also review the website messages, forms and notifications that shape the customer’s expectations before they call.

For a first trial, we would scope one conversation and a clear review method with your team. The findings can then inform a process change, a revised customer message or a further training exercise.

Sources and research notes

The university example comes from OpenAI’s 5 November report, reviewed on 8 November. The event-hire scenario, trial brief and business recommendations are our own illustrative interpretation. We have not measured training outcomes from this proposed exercise.

We also reviewed Apple Developer news, Anthropic’s newsroom and Google Search Central’s update log. Hacker News discovery surfaced older discussions about ChatGPT roleplay, which we treated as background. OpenAI’s X profile returned an access error, and a targeted search did not provide an accessible relevant discussion.