Office Vending Feedback Arrives Through Several Channels: Combine Reports Without Counting Them Twice
One office vending issue can arrive by email, a survey response and a conversation with reception. If each message is counted as a separate incident, the review may exaggerate how often the problem occurred. Combine the information carefully while preserving every useful detail and ensuring that each person who needs an answer receives one.
Start by distinguishing reports from events. Three messages may describe one empty selection at the same time, or three genuinely separate stockouts on different days. Keep the date, location and nature of the observation wherever available. Do not merge entries solely because they mention the same product or use similar wording.
Create one review record
Choose a simple place to collect feedback and assign a reference to each identifiable issue. Record the channels through which it was reported, without copying unnecessary personal details into a widely shared sheet. The review record should help the responsible team understand the service, not become a directory of employees’ private information.
For office vending, separate product requests, availability reports, payment queries and general comments. These need different responses. A repeated request for a favourite snack is not the same as several failed purchases, and an unresolved payment case should not disappear into an anonymous list of product preferences.
Match duplicates cautiously
Look for an explicit connection: the same case reference, machine, date and described event. If it is unclear whether two messages concern the same incident, mark the uncertainty rather than forcing a match. Ask a focused follow-up question when the distinction changes the action required. Keep the original messages available to the responsible team.
For example, an employee may report an empty drink selection to reception and later mention it in a survey. That can be recorded as one observed stockout with two reporting channels. However, another employee describing the same selection empty the following week adds evidence of a separate event, even if the wording is almost identical.
Preserve the strength of the feedback
Combining duplicate incident reports should not erase the fact that several people were affected. Record the number of known reporters separately from the number of distinct incidents where that information is reliable. Avoid treating either measure as the number of all affected customers, because people who did not report remain outside the evidence.
Likewise, do not assume that a single report is unimportant. A clear description of an access or payment problem may need prompt attention regardless of how many channels repeat it. Prioritise the actual issue and its consequences, then use the combined record to identify patterns over an appropriate period rather than simply counting messages.
Close the communication loop
Assign an owner and next step to the consolidated issue. If support is already handling it, add relevant new information to the existing case instead of opening another one unnecessarily. Tell the people who reported directly how their concern is being addressed, while keeping any personal transaction details within the proper support process.
At the next review, describe the evidence accurately: for example, several reports concerned one event, while other reports identified recurring availability gaps. This gives the operator a fair picture and helps the office choose a useful response. A consistent feedback record should reduce administrative duplication without making staff feel that their experience has been dismissed.
Related guidance: Office Vending Feedback Is All from One Team: Ask Who Has Not Been Heard.
For help assessing your site, contact Vending-Machines.ie.
