Handling “Actually…”: How QuoteMe Responds When a Request Changes
“Actually, it’s my desktop.” A small correction can change the right support route. A helpful conversation needs to recover from it without losing the details that still matter.
Inside this part
- Real conversations change direction
- A correction is different from a new request
- Keep useful context without preserving mistakes
- Make switching and resuming visible
- The founder lesson
In this founder development series, we explain the design and implementation behind QuoteMe. Future work is identified as development direction; an implemented component does not establish that every deployment or customer outcome has been verified.
Real conversations change direction
In Part 2, we looked at remembering useful answers. Remembering is only helpful when the system can also update those answers. Customers may correct a device type, change their preferred support method or realise they are describing a second problem.
Consider an illustrative enquiry: “My laptop won’t start. Actually, it’s the desktop in the office.” Keeping the old device answer would lead to irrelevant questions. Deleting the whole conversation would throw away information about symptoms and work impact.
A correction is different from a new request
The conversation needs to distinguish an updated fact from a switch to another task. Correcting “laptop” to “desktop” should update the relevant context. Asking about Wi-Fi while a repair enquiry is unfinished may need a separate request, with a clear way to return to the earlier one.
QuoteMe’s implementation includes continuity, correction and held-request handling. The purpose is to avoid blending two unrelated problems into a misleading summary. These mechanisms still need testing with messy language rather than only neat, predictable inputs.
Keep useful context without preserving mistakes
Some details remain useful after a correction; others may no longer apply. A suburb or preference for onsite help might still matter. A question about a laptop battery may not. The next-question logic needs to reconsider what is missing in the revised flow.
If two statements conflict, the safer response is to clarify the difference. A customer saying “There are no lights” after previously saying “The power light is on” should not cause the system to silently choose whichever answer came last and pretend certainty.
Make switching and resuming visible
Customers should be able to recognise which problem they are working on. A held request is useful only if the interface explains how to resume it. Clear labels and an updated summary help prevent an old detail from appearing in the wrong handover.
That is why we test corrections, interruptions and resuming a previous task alongside straightforward requests. A successful response is not just fluent text. It also needs the right device, current answers and correct request state behind it.
The founder lesson
Intelligence includes recovery. A service conversation should allow people to change their minds without punishing them with a restart. At Your IT & Tech Mates, this matters because a clearer enquiry gives the human technician a better starting point.
You can still review the prepared request and explain any detail that has not been captured correctly. In the next part, we move from keeping the conversation straight to deciding which practical support step fits it.
Frequently asked questions
What should I do if QuoteMe misunderstands a detail?
Correct the detail in the conversation and check the prepared summary before sending your request.
Does changing a request automatically book different work?
No. Changing the conversation does not confirm a booking, final price or paid work.
Explore the existing guides
Building QuoteMe in Public — From Intent to Action
Part 3 of 10. Follow the customer problem, development decisions and human service behind QuoteMe.
Building Your IT & Tech Mates + TheFixers.APP, one practical problem at a time.
Start with what is happening
Describe your technology problem in your own words. Check the prepared request before sending it, and our team can discuss the next practical step.
Your IT & Tech Mates | Real people. Smarter support.