How to get more reviews without begging for them

The most common gap in this industry is a venue with genuinely good rooms and a review count that suggests it opened last month. It is rarely because the games are unloved. It is because the ask is made late, in person, and vaguely, which is three ways of guaranteeing that a delighted group walks out and never thinks about you again.

Reviews are a process. Fix the process and the count fixes itself.

The window is minutes wide

There is a moment, immediately after the reveal, when a group is louder than they have been all week. They are photographing each other, arguing about the puzzle they nearly missed, and telling the one who solved it that they always knew. That is the peak, and everything after it is decay.

Two hours later they are eating. The next morning the whole thing has compressed into a sentence they will tell at work. By the time your booking system sends its automated follow-up on day three, the feeling that would have produced four specific paragraphs has become a vague warmth that produces nothing.

So the goal is to get the ask into their hands while they are still in the building, and to make it something they can complete on the spot or in the next hour. Not a promise to do it later. Later does not arrive.

Ask by message, not across the desk

Asking a group face to face feels like the natural thing to do and it is the weakest version. It puts a social obligation on people who are still coming down from the game, it is answered with yes by everyone and acted on by almost nobody, and it gives them nothing to act on anyway because your review page is not open on their phone.

What works is landing a link on the phone of the person who booked, at the moment they are still in the lobby. However your system does that, whether by email, message, or the confirmation flow, the requirement is the same: one tap from the message to the review box, no app install, no account hunt, no homepage detour.

Then the game master says the sentence that connects the two. Not a request for a favour. A pointer: the booker has a link on their phone, it takes a minute, and it helps the next group find the room. Said once, warmly, while handing back the bags. Said twice, it becomes pestering.

Make the ask specific enough to answer

The reason most people who intend to write a review do not is not laziness, it is the blank box. Faced with an empty field and no idea what is expected, they close the tab.

Give them a starting point and the friction disappears. Which room did you play, who did you play it with, and what was the moment that got the biggest reaction. Three questions, phrased as a suggestion rather than a template, produce reviews that are longer, more specific and considerably more useful to the next reader than yet another line saying great fun would recommend.

Do not script it beyond that. Suggesting the content is helpful. Supplying the content is the thing that gets reviews removed.

The two groups you are quietly missing

The team that did not get out

Operators tend to skip the ask when a group fails, on the theory that nothing good can come of it. That instinct is backwards. A group that failed but enjoyed themselves writes the most persuasive review you can get, because it tells the next reader the room is genuinely hard and that failing was still a good night.

What decides which way it goes is the ten minutes after the clock. A walkthrough of what they missed, generously given, turns a defeat into a story. Rushing a beaten group out of the door to reset for the next booking turns it into a complaint. The debrief is not customer service politeness, it is the single highest-leverage ten minutes in your operation.

The corporate booker

Corporate groups almost never review, and the reason is structural: the person who had the experience is not the person you have a relationship with, and the person who booked it was watching from the corridor and worrying about the invoice.

So ask them separately, and ask for a different thing. A day or two after the event, when the organiser knows the feedback landed well internally, ask whether they would write a couple of lines about how the day ran. That is a review aimed squarely at the next organiser who is deciding whether to risk their reputation on you, and it is worth ten from players.

Volume and recency both matter

A rating on its own tells a reader very little. A high score built on a handful of reviews reads as a small sample. A high score whose most recent entry is from two years ago reads as a business that may not exist any more, and readers are correct to think so, because staff change, sets age and standards drift.

Which means a steady trickle beats a burst. A venue collecting a few reviews every week always looks alive. A venue that ran a review push last spring and nothing since looks like a venue that ran a review push last spring. Build the ask into the shift so it happens on every game, not into a campaign that happens once.

The same requirement is what forces the design when nobody is standing there at the end. A City Sleuth route finishes on a street corner with no staff present, so the ask has to be built into the product itself, arriving on the phone at the moment the final scene resolves. That constraint turns out to be a discipline worth borrowing indoors, because a prompt that fires reliably at the right moment beats a member of staff who remembers most of the time.

The shortcuts that will cost you the reviews you have

Two practices are worth naming plainly, because both are common and both are against the rules.

Incentives. Anything offered in exchange for a review, a discount, a free hint pack, entry into a draw, is prohibited, and the penalty is not limited to the review in question. Google's prohibited content policy covers this directly, and enforcement can reach the whole profile.

Gating. Surveying customers first and only sending the review link to the happy ones is also against the rules, and it hollows out the thing you are building. A profile with no critical reviews at all reads as managed, and experienced readers go looking for the negative one specifically.

Both also fail on their own terms. Reviews from people paid to write them are short and generic, and short generic reviews persuade nobody.

Where to start

Run one shift and count how many groups were actually asked, by name, at the right moment. It is usually far fewer than the owner believes. Then write the two sentences your game masters will say, put the link where it takes one tap, and check the count again in a month.

Operators running a City Sleuth game beside their rooms get the ask built into the app by default, which is one fewer thing to remember on a busy Saturday. The rest of the operator library is at the partner guide.