WEIMI INSIGHTS / SERVICE SUPPORT
A concise incident record helps the service team separate a one-off transaction problem from a recurring equipment issue.
IDENTITY
Name the exact machine and configuration.
SEQUENCE
Record the order of events.
EVIDENCE
Include relevant details without private data.
Send support a short factual timeline, the exact displayed message and the checks already completed under the approved procedure, then keep further updates in the same incident record.
01 / BUYER NOTES
Include the machine identifier, model and location reference used by your service team. Where relevant, add the software version visible through the approved interface and the affected payment or dispensing component. A site nickname alone can be confusing when several cabinets share a location.
State whether the machine is available for customers, partly unavailable or taken out of service under your procedure. Support needs to understand the current operating state as well as the original complaint. Record any stock or customer issues that still need separate attention.
02 / BUYER NOTES
Describe what the customer or operator did, what appeared on screen and what happened next. Separate direct observations from assumptions. “Payment approved, selection did not deliver, message displayed” is more useful than simply declaring that the motor is broken.
Use timestamps with the relevant time zone and include the transaction reference where appropriate. Explain whether the issue happened once or repeatedly and whether it affects one selection or the whole machine. These details help support choose the next diagnostic step.
03 / BUYER NOTES
Record actions taken under the manual or support instructions and the result of each. If the machine was restarted through an approved procedure, note when and what changed afterwards. Repeating an undocumented action can make the event harder to understand.
Do not open restricted areas, bypass interlocks or alter settings just to gather more evidence. Ask the service team for the next authorised step when the documented checks are exhausted. Preserve the relevant visible information before it is lost, where doing so is permitted and safe.
04 / BUYER NOTES
Use one incident reference for follow-up messages, replacement parts and service visits. Add new observations without rewriting the original sequence. If another shift takes over, it should be able to see what remains unresolved and who owns the next action.
Close the report with the confirmed repair or adjustment, the verification performed and any remaining limitations. If the cause was not established, say so. A clear unresolved or monitored status is more useful than an unsupported explanation recorded as fact.
Add: Which function is affected and the current service state.
Example: One selection fails while other purchases complete.
Add: Exact screen message and transaction reference.
Example: Approval appeared, followed by a delivery exception.
Add: Each approved check and its result.
Example: The documented restart completed, but the same symptom remains.
PRACTICAL ANSWERS
No. Clear observations are valuable even when the cause is unknown. Avoid presenting a guess as a confirmed diagnosis.
Only include necessary, permitted information. Mask unrelated personal or payment data and use the provider’s appropriate support channel.
When the outcome, verification and any remaining actions are documented. A part being shipped or a restart being attempted is not by itself a confirmed resolution.
YOUR NEXT STEP
Ask the supplier which machine references and visible evidence are useful for service requests. Give staff a short template so incidents remain understandable across shifts.
Explore equipment →Discuss your requirements →