A Vending Fault Returns After the Case Closes: Reconnect the History
When a vending fault appears again after a service case has closed, the previous record is useful evidence. Contact support with the old reference and explain what has happened since the machine returned to use. Do not assume the earlier repair failed, but do not describe the new event as unrelated without mentioning the history. A clear timeline helps the service team decide whether the symptoms are connected.
Describe the return of the symptom
Write down when the machine last worked normally and when the problem was observed again. Describe what the customer or operator saw, including any displayed message, affected selection or payment step. Use the actual observation rather than a diagnosis. For example, saying a product did not reach collection is more useful than naming a component that has not been inspected.
State whether the new symptom is identical to the previous one or only similar. A payment problem and a product-delivery problem may both be described casually as the machine not working, yet require different information. Mention any normal purchases between the two events. Do not erase that period from the account simply because the latest incident is frustrating.
Connect the records without duplicating them
Give the earlier case reference, machine identity and site location. Ask whether support wants to reopen the existing case or create a linked follow-up. Follow that process so several colleagues do not unintentionally create disconnected reports. If another person has already contacted support, add their reference rather than asking everyone to start again from the beginning.
Keep the previous visit note or closure message available. Record what it said was checked or completed, without adding assumptions about work that is not documented. If the closure was based on a remote check rather than a visit, make that distinction. The purpose is to preserve useful context, not to turn a short service note into a stronger claim than it supports.
Explain what changed after the case closed
Tell support about relevant changes such as replenishment, a different product pack, building work or an interruption to normal access. These details may or may not matter, but the team can assess them. Do not conceal an ordinary change because you worry it will distract from the fault. Equally, avoid listing every unrelated event that happened in the building.
Ask for the appropriate interim instructions and communicate them to the named site contact. Do not repeatedly test a troublesome selection with customers’ money or attempt unapproved resets. If use needs to be restricted, make the status clear through the agreed process. Keep purchase complaints linked to the service history while allowing each customer to follow the correct transaction-support route.
Agree the next update and review
The fully managed service provides a support route for logging issues, with technical attendance arranged under the service terms. Logging a recurrence does not by itself establish an arrival time or a particular remedy. Ask what information is still required and when the next update will be provided. Record that commitment accurately for colleagues.
After the next action, note the checks completed and the agreed return to normal use. Keep the old and new references together even if the underlying causes prove different. A short, factual sequence makes a later service review more useful than a general statement that the machine always breaks. When discussing vending support requirements, bring that sequence so the conversation starts with evidence.
Related guidance: A Vending Service Visit Finds No Fault: Keep the Original Symptoms on Record.
Planning or reviewing vending at your site? Contact the team with your location, equipment details and the question you would like to resolve.