Running the team
Ask three employees the same customer question. Do you get three different answers?
Run a short team exercise to find conflicting sources, unclear permissions and unsupported promises, with three fictional question cards and a worksheet.
In this guide
THE SHORT ANSWER
Give three teammates the same customer scenario and the information they would normally be allowed to use. Have them answer independently, then compare the facts, sources, permissions and next steps behind their answers. Different wording can be fine; different promises need investigation. Resolve the source or policy problem with its owner, then try a changed scenario. Agreement alone does not prove an answer is correct.
One employee says yes. Another says no. A third says, “Usually, but ask the manager.”
Which answer does your customer get? It may depend on who picks up the phone.
Try a small exercise: same customer, same facts, three independent answers. You are looking for the place where guidance, records or authority diverge. Three people is a manageable starting group, not a statistical sample or a special number required for the method.
Think of it as a customer-service game show with the scoreboard removed. The useful prize is one fewer question your business answers by accident.
Different words are fine. Different commitments need checking
“I can check that for you” and “Let me look at the booking” may express the same next step. “You are booked” and “I have requested a booking” do not.
Compare the consequence for the customer:
- Would they travel, pay, cancel an alternative or expect someone to arrive?
- Did the answer preserve a condition, limit or unresolved detail?
- Was the promised action within the person's authority?
- Could the team actually carry out the next step?
In a public account on LinkedIn, customer-service author Jeff Toister describes receiving an incorrect policy answer from a human agent that changed after investigation. It is one reported experience, not a measure of how often this happens. It illustrates why confidence and a familiar-sounding answer are weak substitutes for checking the source.
Set up a useful round
Choose a recurring question, a question with a consequential exception or one whose answer recently changed. Use sanitised material from authorised notes or transcripts, or write a fictional case. Do not surprise the team with recordings of a colleague's difficult call.
Tell participants what you are investigating and share the results as process findings. A short exercise cannot establish someone's overall competence. People may have different system access, responsibilities or information; those differences need to be visible before interpreting an answer.
For a fair comparison, choose people with comparable responsibility for the scenario. If different roles are involved, record their permissions and compare whether each follows the appropriate route, rather than expecting all of them to make the same decision.
Prepare a customer question and a fact sheet. Identify the current approved source, its owner and the expected decision boundary. If the owner cannot settle the rule in advance, mark the case as unresolved and use the session to gather questions. Do not invent an answer key.
Allow the same lookups people could make during a real call. This is an open-book exercise: finding the right source is part of the task.
Answer independently before discussing
Give everyone the same case. Ask them to write down:
- What they would tell the customer.
- What they checked, including the source and version where relevant.
- What they can decide and what needs approval.
- What they would record or do next.
- What they still cannot establish.
Collect the responses before the discussion so the first confident speaker does not become the group's answer key. Then compare the reasoning with the approved source. A manager's recollection is also something to verify.
The downloadable same-question exercise kit contains three fictional cards, facilitator notes, a blank response sheet and a findings log. Give participants the question and facts first; keep the facilitator notes for the discussion. Adapt the business rules before using a card as real staff guidance.
Three fictional rounds to try
These rules are invented to make the decision visible. They are not recommended policies for every business.
Round 1: Does “request received” mean booked?
Customer: “I submitted the Saturday appointment form and got a reference number. Can I tell my family it is booked?”
Facts: The system shows “request received”. The approved process says a slot is reserved only when the status changes to “confirmed”. Staff can check the request and arrange an update; they cannot reserve a slot outside the booking process.
Compare: Does each response distinguish a reference number from a confirmed appointment? Does anyone imply a reservation because the form succeeded? The appropriate next step is to check or progress the request through the booking process, then give an update the team can deliver. A new promise of a specific Saturday slot is unsupported.
Round 2: Does the price include the thing they need?
Customer: “The projector hire is 40 for the day. Does that include a screen?”
Facts: The current approved price sheet lists projector-only hire at 40, including its power cable. Screen hire is a separate option; its price and availability must be checked. An older printed flyer uses the phrase “presentation kit” without listing its contents.
Compare: Does everyone check the current inclusions? Do they disclose the separate screen option without inventing its price or availability? Does someone spot that the old flyer could be causing the confusion?
The discussion should end with an owner for correcting or withdrawing the outdated material and checking where else that wording appears. Telling staff to “remember next time” leaves the conflicting source in circulation.
Round 3: Can they agree to a late collection?
Customer: “You close at five. Can I collect the equipment at 4:55?”
Facts: The approved collection instructions require arrival by 4:30 to complete a handover. A duty supervisor may approve an exception. Front-desk staff may request that decision but may not approve it themselves. The customer has not yet been told the collection cut-off.
Compare: Does the answer explain the handover cut-off, offer to check an exception and avoid promising approval? A flat “we close at five, so yes” ignores the process. A flat “never” invents a stricter rule. If the supervisor cannot be reached, the exception remains unconfirmed; the customer needs to know that before setting off.
The opening hours and collection instructions may both be accurate while their relationship is poorly explained. That is also a candidate for the website answer-finding exercise.
Classify the disagreement before choosing a fix
On a small screen, swipe the table to see all columns.
| What differs? | What to investigate | Who needs to act? |
|---|---|---|
| Wording only | Are the facts, conditions and next step equivalent? | Keep natural wording if the meaning is clear |
| Source | Are people using different versions or records? | The information owner resolves and updates the sources |
| Access | Can everyone in that role see the necessary information? | The system or process owner fixes access |
| Authority | Who can confirm, change or make an exception? | The authorised manager defines the boundary |
| Application | With the same clear rule, do people apply it differently? | The team rehearses the specific decision after checking the rule |
| Unresolved facts | Is the necessary information missing for everyone? | The named owner obtains it or defines an honest interim response |
Do not vote a policy into existence. Three matching answers can all be wrong. Three different responses can all be appropriate if roles or facts differ. Settle correctness against the current policy and operational record, with the person authorised to resolve ambiguity.
Ask people why they chose their answer. “I cannot see that screen” leads to different work from “I thought any reference number meant confirmed”. Keep those explanations alongside the response.
Leave with a decision, an owner and a retest
For each material disagreement, record the evidence, the approved resolution, the person making the change and a review date. If it remains unresolved, record who decides and what staff should say while waiting. Do not let a draft exercise card quietly become policy.
Turn a settled rule into a short staff decision note where useful. The note should cover the source, permission, exception and next step. The staff-training guide explains how to rehearse an individual task once the information is reliable.
Then change one fact and run another round. Suppose the appointment is now marked confirmed, the customer has already paid for a screen, or the supervisor has explicitly approved 4:55 collection. Can people explain why their response changes?
Record whether the material disagreement remains, was resolved, or cannot yet be assessed. Avoid a league table or a percentage based on three people. Check a few suitable later cases with the team to see whether the corrected source is available and used; a successful rehearsal does not prove a business outcome.
Where Call Nerd helps
Call Nerd can surface recurring customer questions and provide transcripts for a person to review. Those can help you choose realistic cases, after checking context and removing customer details. If a question appeared in a call, the transcript still does not establish which information or permissions the employee had.
The team supplies the current rules, checks the answers and resolves disagreements. Call Nerd does not certify a policy or turn this exercise into an employee assessment.
The aim is simple: the next customer should receive an answer supported by the same current facts, with the right person responsible for any exception.