The Scenario
The client messages in the group chat that evening:
“Take me to Hongqiao tomorrow morning.”
Customer service replies:
“Got it.”
The order is then created in the system as:
Recorded Time
09:00 Departure
But the next morning, the client asks:
“Why isn’t the car here yet? I said 8 o’clock.”
Where’s the Problem?
“Morning” is not an exact time.
It’s a textbook example of:
A natural-language ambiguous field.
Similar expressions include:
- A bit later
- Around noon
- In the afternoon
- After lunch
- Right after the meeting
- About two o’clock
Why Can’t We Guess?
Because everyone’s interpretation of “morning” is different.
Some people mean:
07:00 – 09:00
Others mean:
09:00 – 11:00
Building the order directly
amounts to converting the agent’s interpretation into the client’s instruction.
The Right Action
The moment a fuzzy time appears, confirm immediately:
“What exact time should we depart?”
If the client doesn’t know yet,
the order can be recorded as:
Time Pending
instead of being silently filled in with a guess.
The Rule This Case Produced
These words should be treated by the system as high-risk vocabulary:
morning / noon / afternoon / evening / in a bit / around / about / after the meeting
Whenever they appear, further confirmation is required.
morning / noon / afternoon / evening / in a bit / around / about / after the meeting
Whenever they appear, further confirmation is required.