The wine club conversation in most tasting rooms depends on the guest starting it. A room built that way converts the visitors who arrived intending to join and almost no one else.
It goes missing for a reason that has nothing to do with the quality of the staff. Asking reads as selling, and hosts who take pride in hospitality will avoid anything that sounds like a pitch. What changes that is a host who has something worth saying and the judgment to know when the room will take it. Persuasion training produces neither.
The story has to arrive first
An ask made to a guest who has been handed nothing but tasting notes is an offer of a discount, and discounts get compared to other discounts on the drive home. An ask made to a guest who now knows why a block gets picked at four in the morning, or what the winemaker did with a vintage that went sideways, is an invitation to stay connected to something they just got let into.
That means the club sentence is the last twenty seconds of a longer piece of work. Rooms that train the ask without training the story are asking hosts to close on nothing. Give every host two or three real stories about the wines they pour, sourced from the winemaker or the owner rather than from a fact sheet, and confirm they can tell them without the bottle in their hand. That work is what the Unscripted Hospitality Workshops are built around.
Reading the guest carries the timing
The moment for the ask cannot be assigned to a step in the tasting, because it arrives at a different point with every guest and sometimes it does not arrive at all. What a host can be taught is what to watch for.
The signals that open the door are small and consistent. A guest asks a second question about one wine rather than moving on. They turn the bottle to read the back. They repeat the name to whoever they came with. They put their phone down. Any of those means the guest has stopped tasting and started paying attention, and that is the only condition under which the sentence lands as hospitality.
The signals to hold are equally readable. A guest looking toward the door, a group where one person is clearly deciding for everyone, a table that has gone quiet in a way that has nothing to do with the wine. Hosts need explicit permission to skip the ask on those visits. A room that requires the ask every time trains its staff to stop reading and start reciting, which costs more than the memberships are worth.
Permission that broad turns into avoidance unless the owner defines it. Good grounds are things the guest did or said, and there are five of them. The guest belongs to the club already or said they belong to several. The guest is not drinking, whether driving, pregnant, or cutting back, and has said so. The visit belongs to something other than the wine, a birthday table or a difficult conversation, and the host would be interrupting it. The party is on a fixed schedule the room does not control, such as a bus group or a wedding block. The person who decides is not in the room, and the guest has said they need to talk to someone first, in which case the sheet goes in the bag and the ask goes to a follow-up.
Three reasons do not qualify, and they are the ones that actually stop asks from happening. The host guessed the guest could not afford it. The host assumed a visitor from out of state would never use a membership. The host was busy. Each of those is the host deciding for a guest who never got the chance to decide for themselves, and owners should name all three out loud so nobody can retire behind them.
The harder half of this is knowing when to stop talking. A host who has just told a good story and gets a real reaction will often keep going, and the reaction gets buried under the next three facts. The instruction is to finish the story, stop, and let the guest respond before anything else is said. The pause is where the ask fits.
Move it off the register
An ask made at payment arrives after the guest has settled what the visit will cost them, and it competes with a receipt. The place it belongs is at the wine the guest responded to, immediately after the story that earned the response.
Hosts need permission to stop mid-pour when that happens, and enough familiarity with the lineup to know which wine usually earns it. Both are training items, and both can be installed in a shift.
Event days run the order backward
Passport weekends, wine road weekends, and festivals break every assumption above. There is no visit to read, because guests arrive in waves and leave before a host has learned anything about them. There is no quiet moment for a story. There is often no departure moment either, since people drift off while the next group is already at the pour.
On those days the ask goes first and it goes to everyone. One line at the start of the pour, said plainly as information rather than as a close. Something to the effect that if one of these works for them, the club is how it keeps arriving, and the sign-up is at the table by the door. That framing costs nothing, carries no pressure, and gives the guest the whole rest of the tasting to decide.
Then hand them something that works in a pocket. A card with one fact about the wine on it and a way to sign up on the back, or a code at the pour station, or a named location with a person standing at it. The thing a guest carries out of a festival has to function without the host, because the host will never see them again. A promise to follow up later is not the same instrument and it converts at a fraction of the rate, since the guest has no reason to remember which of eleven tables made it.
Two things have to be true for this to work. The sign-up point needs to be identified by location rather than gestured at, because a guest holding a glass and a map will not go looking. And someone has to own that table for the whole day, which means it comes out of the staffing plan before the event rather than being covered by whoever is free.
The holds described earlier do not apply on event days. There is nothing to read yet, so the line is said to everyone. What does need watching is the week after, when the event cadence tends to follow the staff back into a normal Saturday and hosts keep leading with the club to guests who came for an afternoon.
Give the host the fact and let them word it
Scripts fail because a host delivering someone else's line sounds like a host delivering someone else's line, and a guest who has just been told something true will hear the switch immediately.
Supply the fact and leave the phrasing alone. The last vintage of a wine. A bottling that never leaves the club. A production number small enough to explain why. One per wine is enough. Listen once a shift to confirm hosts are saying it in their own words, and correct the fact when it comes out wrong without touching the delivery.
Settle the line that follows a decline
Most rooms have never decided what happens after no, so the host improvises and the visit cools. Write that line in advance and keep it short enough to say without effort. Acknowledge the answer, return to the wine, keep pouring.
Say plainly to the staff that most guests will decline and that this is the expected outcome. A host who reads a no as failure stops asking by the third one, and that is where the practice usually dies in a room that started well.
Count the asks
Sign-ups are the guest's decision. The ask is the host's, and it is the only part of this the room controls. Counting joins at the end of a shift tells a host they failed at something that was never theirs.
Ask instead how many times it came up, and how many times the host read the room and chose to hold it. A host who made seven asks and held four with a reason for each is doing the job correctly. Self-reported counts stay honest for about three weeks before they drift, which is why the owner should collect them standing in the room. Track joins separately and monthly, and keep the numbers apart.
This puts a room at odds with the evaluation programs many wineries buy, which send an anonymous visitor through the tasting and score the experience against a fixed list of criteria. On those forms an ask that never happened is a miss, and the host loses points for it regardless of what the guest was doing at the time. The programs are useful for the things that genuinely are pass or fail, like whether the guest was greeted and whether the wines were introduced. They handle the ask badly, because a single visit gives the evaluator no way to see the four holds that were correct.
Owners who use both should say which one governs. A score that punishes every unmade ask will produce hosts who ask a woman who just said she is pregnant, and the room loses more in that one exchange than a membership is worth. The shift count with reasons attached is the better instrument here, because it credits the judgment rather than the reflex.
None of this requires a budget or a new position. It requires stories worth telling and four decisions made before the next shift starts.
Patrick R. Dunn runs Vianarra, a hospitality storytelling practice working with winery owners, GMs, tasting room teams, hoteliers, and restaurateurs. The Unscripted Hospitality Workshops are described here.
The Vianarra newsletter goes out Wednesdays, written for the people who run the floor. Subscribe here.