“The doors opened late” sounds straightforward until you check what happened. Was there a venue delay, an outdated listing, or did the guest arrive before the advertised entry time? Replying too quickly can turn a small complaint into a public argument. For venues, promoters, rehearsal studios, record shops and other music businesses, the first step is to verify the experience behind the review.
Reviews appear beside the practical details people use to make plans. A concertgoer might check whether a room is accessible or how staff handle queues; a record shop customer might want to know whether an order will be held. The rating matters, but the details—and the reply—often say more. Give someone responsibility for monitoring reviews, protect customer privacy and use repeated complaints to spot problems that need fixing.
Know which reviews belong to your business
Find the places where customers already leave feedback: search and map listings, ticketing services that support reviews, relevant social pages and marketplaces where you sell goods or services. Check which accounts your team can access. Look for old listings with a former address, outdated hours or an old business name. Incorrect information can generate complaints that a customer service reply will never solve.
Assign someone to check each channel regularly and name a backup. A small team needn’t watch notifications all night, but it should have a predictable routine. Check more often after a show, during a busy festival period or when you know something went wrong. In a shared log, note the platform, date, main issue and response status. A link or review identifier and a few factual notes are usually enough; there’s little reason to copy someone’s personal details into another system.
Work out which parts of a complaint concern your service and which belong to another party. A venue may control entry, facilities and its staff, while a visiting promoter controls ticket terms or set times. That helps you route the issue, but it shouldn’t become a public excuse. If conflicting information from several organisations sent a guest to the wrong door, they still need a clear answer.

Triage before you reply
Read the whole review, check its date and compare its claims with what your team can verify. For a live event, that might mean looking at the published schedule, entry notes, a shift report or a colleague’s account. If there’s a record from the night, don’t rely on memory alone.
A useful order of attention
- Safety, accessibility and discrimination concerns: send these promptly to someone authorised to investigate. Don’t debate them in a public reply.
- Time-sensitive service problems: identify unresolved ticket, booking or order issues that still need a direct response.
- Specific negative reviews: check what happened and decide what you can acknowledge or correct.
- Positive reviews and general feedback: reply when you can say something personal and relevant, rather than turning every thank-you into a script.
- Suspected spam or mistaken identity: preserve the details and check the platform’s reporting options before making public accusations.
This order keeps a one-star rating with little detail from taking priority over a credible report of an unsafe queue or inaccessible entrance. It also helps prevent rushed promises. Whoever monitors reviews should know who can authorise a refund, confirm an accessibility change or speak for an event partner—not improvise those decisions in public.
Write responses for the reviewer and everyone else reading
Address the specific issue, stick to what you know and explain the next appropriate step. You don’t need to repeat the entire complaint, dispute how the customer felt or bury the answer under promotional language.
If you’ve confirmed an error, you might write: “You’re right that entry started later than the time shown on our event listing. We’ve corrected the listing process for future shows. If your booking was affected, please contact our box office through the details on your confirmation so we can look at the transaction.” That acknowledges the mistake without discussing an individual booking in public. If you’re still checking the cause, say so rather than announcing a fix that hasn’t happened.
Be just as accurate with praise. “Glad the staff helped you find the step-free entrance” responds to something the guest mentioned. “We always deliver a perfect experience” makes a claim no business can support. Reply when you have something genuine to say; identical thanks under every short rating add little.
Keep private information out of public replies, even if the reviewer has shared some of it. Don’t publish order numbers, medical details, staff schedules, descriptions of security footage or a customer’s contact information to prove a point. Move case-specific discussion to an appropriate private channel. Describe the general resolution publicly only if the customer agrees and it would be useful to others.
When an apology is appropriate
Apologise plainly for a known mistake or an experience your team reasonably should have prevented. “Sorry you feel that way” can sound dismissive. But don’t treat an unverified allegation as fact just to end an uncomfortable exchange. “I’m sorry you had difficulty getting information about the accessible entrance; we’re checking what was communicated to staff that night” acknowledges the problem without pretending the investigation is complete.
For serious allegations, preserve the review, escalate it through your organisation’s normal process and seek appropriate specialist advice where needed. A public reply can confirm that you’ve received the report and offer a safe way to get in touch. A comment thread is no place to interview witnesses or reach findings.

Handle disputed reviews without escalating them
Some reviews land on the wrong listing, describe a transaction you can’t match or appear to break a platform’s rules. An unrecognised name doesn’t prove the experience is false: concertgoers may book through someone else, pay at the door or use a different name online. Check what you can, then use the platform’s reporting process if there’s a specific policy reason.
If you reply publicly, keep it narrow: “We haven’t been able to match the details in this review to an event at our venue. Please contact our team with the event date so we can investigate.” Don’t speculate about competitors or accuse someone of lying. You can’t control whether a platform removes a review, and repeated arguments may draw more attention to it.
Don’t offer payment, discounts or special access in exchange for removing or changing a review. If a service remedy is warranted, offer it because of the service issue, not the rating. Check the platform’s current rules on incentives and review requests; they differ and can change.
Ask for feedback without shaping the answer
You can invite genuine customers to review an experience, but leave room for honest criticism. A short message after a purchase, studio session or event can point people to the review option without asking for five stars. Don’t invite only those who praised you privately while directing dissatisfied customers elsewhere. That filtering makes reviews less useful and may conflict with platform rules.
Consider the timing. An event-night message while guests are still travelling home may feel intrusive. If there’s been a known disruption, give the team a chance to address it. Review invitations must also respect the consent and communication preferences that apply to each customer relationship. Having access to an event mailing list does not mean you should upload it to a review service.
Frontline staff can say feedback is welcome, but their pay or performance shouldn’t depend on named positive reviews. That pressure can distort conversations with guests and create problems when someone criticises an employee. Offer a private route for sensitive feedback alongside public review options—not as a way to suppress negative posts.
Use patterns to improve the experience
A review log earns its keep when someone looks beyond the ratings. Group comments by issues you can act on: unclear entry instructions, sound levels, delayed merchandise dispatch, booking responses, facilities or staff communication. Keep compliments in the picture, too. Repeated praise may point to a practice worth preserving.
Weigh frequency, specificity and context together. Three detailed accounts of confusion at the same entrance may tell you more than a larger set of vague low ratings. A complaint caused by a one-off power failure calls for a different response from one repeated across several events. Record what changed and when, then check later feedback for signs that it helped. A higher average rating alone doesn’t prove the problem is gone.
If guests repeatedly say they couldn’t find the accessible entrance, inspect the physical signs, the instructions sent before arrival and what door staff tell people. A clearer web page won’t help if the entrance is locked on show nights. Equally, a well-informed door team can’t reach a guest who was directed to the wrong side of the building before arriving.
Share patterns with the people who can act on them, not just whoever manages the listing. For a small organisation, a monthly discussion may be enough: pick a recurring issue, assign an owner and record the change you’ll test. If an outside promoter, delivery partner or building operator is responsible, decide who will contact them and what information can be shared.
Protect the relationship behind the rating
Music businesses often serve overlapping communities. Someone leaving a critical venue review may also be a regular at another event, a local performer or a neighbour. Handle that criticism carefully, without expecting special treatment from the reviewer. Ask employees not to challenge reviewers through personal accounts or discuss identifiable complaints in group chats beyond the people who need to resolve them.
Show similar restraint with praise. Before reposting a customer’s review in marketing material, check whether permission is needed—particularly if it includes a name, photograph or sensitive detail. A review meant to inform other customers isn’t automatically an invitation to appear in a campaign.
Set a response-time target your team can meet, with clear exceptions for urgent concerns. Keep brief internal notes on what needs escalation and who owns each platform account. After a busy weekend, the next person on review duty should be able to see that a ticket complaint has gone to the box office, rather than promising a second, conflicting resolution in the comments.
An end-of-shift note can be as simple as: “Saturday show, entry-time complaint; published listing checked, box office investigating affected bookings; public reply pending confirmation.” It tells the next person what to do without copying the reviewer’s private details into the log.