By Michail Kolpidis
In September 2026, I travelled to Thessaloniki for the 90th Thessaloniki International Fair, which I attended representing the Kapandriti Technology Institute. My wife and I rented an apartment for the visit. During our stay, she realised that a ring was missing.
We do not know with certainty what happened to it. It may have been misplaced. It may have been taken. We cannot identify who entered the apartment or assign responsibility to the property owner, the management company, a cleaner, a contractor, or anyone else without evidence.
What we can describe is the response.
We contacted the company the day after checkout. At a moment when time mattered, the communication was neither prompt nor constructive. A substantial response came late and became defensive after we posted a public review about a week later.
That experience taught me something larger than the loss of an object: when a customer reports a serious incident, a company reveals whether it is organised to learn or organised to defend itself.
The first duty is to take the report seriously
A constructive response does not require a company to admit fault. It requires the company to recognise the seriousness of the report and begin a credible process.
The first reply could have been simple:
We are sorry to hear this. We will immediately check the apartment, contact the cleaning and access teams, preserve the relevant records, and return to you by a stated time.
That wording would not determine whether theft occurred. It would show that the company understood the difference between an accusation and an incident that deserves examination.
Instead, delay changes the nature of the problem. Memories weaken. Rooms are cleaned and occupied again. Access information becomes harder to reconstruct. A customer begins to wonder whether the absence of a process is itself part of the risk.
Defensiveness is not incident management
Defensiveness often begins with the wrong internal question: How do we prove that this is not our fault?
A learning organisation asks a different question: What can we establish, what should we preserve, and what should we improve?
The difference is practical. A defensive response debates the customer's wording. A constructive response checks who had authorised access, when the property was entered, whether an item was found, who handled the turnover, and whether the facts can still be documented. It assigns one person to communicate and gives the customer a clear time for the next update.
Even if the ring is never recovered and no wrongdoing can be established, the quality of that process matters. It is part of the service for which the customer paid.
A complaint is operational information
Companies often treat complaints as reputational threats. That makes them miss their value as operational evidence.
A report of missing property may reveal weaknesses in key control, cleaner and contractor records, found-property handling, room inspection, escalation, or communication. The correct response is to examine those points. Where lawful and proportionate, a company might improve access logging or add cameras at building entrances and other shared access points while respecting the privacy of guests inside their accommodation. It might introduce a two-person check for found valuables, a time-stamped turnover record, or a formal escalation route for suspected theft.
None of these measures proves what happened in our case. That is exactly why they matter. Good systems reduce uncertainty in the next case.
Public reviews should not be the trigger
A customer should not need to publish a review before an incident receives focused attention. When the serious response arrives only after public criticism, the company teaches customers that visibility matters more than substance.
It also loses the opportunity to resolve the matter privately and professionally. A prompt response might not recover an item, but it can preserve trust. A delayed defensive response can destroy trust even if the company was not responsible for the original loss.
Reputation is protected by a reliable process long before it is protected by a reply beneath a review.
Learning requires ego to step aside
Every organisation makes mistakes, and every organisation faces incidents it did not cause. The dividing line is what happens next.
One company treats the report as a signal. It documents the facts, helps the customer, reviews the weak points, and changes its procedures. Another company treats the report as an insult and spends its energy defending its image.
The first company may become safer because something went wrong. The second may repeat the same failure because admitting uncertainty feels too close to admitting blame.
Our missing ring remains an unresolved personal loss. The organisational lesson is clearer: customer management is tested when the facts are incomplete, the issue is uncomfortable, and there is no easy answer.
A company does not demonstrate maturity by insisting that nothing could have happened. It demonstrates maturity by showing that, when something may have happened, it knows how to respond, investigate, communicate, and learn.