When Something Goes Wrong: How to Talk to Members Through Outages, Heat Waves and Mistakes

Sooner or later, something will go wrong. A cooling unit will fail on the hottest day of the year. The power will go out for longer than expected. A bottle will be put in the wrong bin. A batch of invoices will go out with an error. None of this makes you a bad operator. Equipment fails and people make mistakes in every business.

What members remember is not usually the problem itself. It is how they found out about it and how you handled it. A problem communicated early, honestly and clearly often leaves members trusting you more than before. The same problem discovered by accident, or explained vaguely, can undo years of goodwill in an afternoon.

The worst time to work out how to communicate is in the middle of a problem. Prepare now. Decide who speaks for the business when something goes wrong, so members hear one consistent voice. Draft short templates for the situations you are most likely to face: a temperature excursion, a power outage, severe weather, a misplaced bottle and a billing error.

Check your contact records while things are calm. When you need to reach every member within an hour, you do not want to discover that dozens of email addresses are missing or out of date. Any system you use to message members should show you clearly who can’t be reached, so you can fix those records long before they matter.

The first principle is speed. If a problem could affect members’ wine, tell them before they learn about it from the news, a neighbor or a social media post. A heat wave that knocks out power across your area will be on local news within hours, and members will immediately wonder about their collections. A short message from you, arriving before they have to ask, is enormously reassuring.

You don’t need every answer before you speak. It is fine to say that you are still assessing the situation. What matters is that members hear from you first, that they know you are aware, and that they know when to expect the next update.

Members care about one thing above all: is my wine all right? Answer that question directly and honestly. If there was a temperature excursion, say how high the temperature rose and for how long. Explain in plain terms what that means. A brief rise of a few degrees for a few hours is very different from a sustained period of real heat, and members deserve to understand which one occurred.

Avoid both extremes. Don’t minimize a serious problem to avoid worry, because members will find out and never trust your reassurances again. Equally, don’t dramatize a minor one out of excessive caution. Accurate, calm specifics are the most reassuring thing you can offer, because they show that you actually know what happened.

After explaining what happened and what it means, explain what you are doing. Repairs underway, backup power running, additional monitoring in place, an engineer on site. Then say when you will update them next and keep that promise even if there is little new to report. A message saying “no change, the repair team is still on site, next update at six” is far better than silence.

When the problem is resolved, close the loop with a final message. Explain what was fixed and what you are changing to reduce the chance of it happening again. That last message is what turns a frightening day into a demonstration of competence.

Not every problem is dramatic. The most common one is a bottle that isn’t where it should be, discovered when a member requests it. The instinct is to guess or to promise it will turn up. Resist both. Tell the member honestly that you are checking, and give them a time by which you will call back.

Then use your records. When every bottle carries a logged history of each movement, from intake onward, you can usually trace where it went and when. Most missing bottles turn out to be in a neighboring bin or already set aside for a pull. Call the member as soon as you know, explain what happened and apologize for the delay. A clear answer delivered quickly turns an anxious moment into proof that your records work.

If invoices go out with an error, fix it first and communicate second, ideally on the same day. Tell affected members plainly what went wrong, confirm that it has been corrected and explain whether they need to do anything. If they were overcharged, refund or credit promptly without making them ask.

Keep the apology proportionate and sincere. One clear apology, a quick fix and a simple explanation of how you will avoid a repeat is enough. Long, defensive explanations tend to make a small problem feel larger than it was.

When something affects the whole facility, you need to reach every member quickly, but a message that looks like a mass announcement can feel cold at exactly the wrong moment. A note sent to each member individually, by name, from a person they recognize, feels very different from a bulletin.

In Best Cellar Club, the same Member Updates tool used for monthly statements can send a plain personal note with every figure section switched off. Each member receives their own copy addressed to them, replies come back to your own inbox, and the tool lists anyone who couldn’t be reached, so you know exactly who still needs a phone call.

A good first message is short and follows a simple order. For example: “I want to let you know that the power went out across our area at two o’clock this afternoon. Our backup generator started immediately and the vault has held its temperature throughout. Your wine is safe. We are watching conditions closely and I will update you again at eight this evening, or sooner if anything changes. If you have any questions at all, reply to this email or call me directly.”

It says what happened, what it means for their wine, what you are doing and when they will hear from you again, all in a few sentences. It is signed by a person. It invites questions. Keep a version of this ready for each situation you might face, so that on a difficult day you are editing a draft rather than writing from nothing.

Once the problem is over and members have been updated, sit down with your team and go through what happened. What caused it, how quickly did you know, how quickly did members hear from you, and what would you do differently next time? Write the answers down and change what needs changing, whether that is equipment, procedures or contact details.

That review is worth sharing, briefly, with members when it is appropriate. A short note explaining what you learned and what you have improved shows that you take their trust seriously and treat problems as reasons to get better.

Operators often fear that admitting a problem will drive members away. In practice, the opposite is usually true. Members understand that equipment fails and people make mistakes. What they cannot accept is feeling kept in the dark about their own property.

Handle a bad day with speed, honesty and specifics, and many members will come away more loyal than before, because they have seen first hand that you tell them the truth and look after their wine when it matters most.