How should an event respond to public complaints on social media?

Your festival's latest post was supposed to announce another ticket release. Instead, the comments are full of people saying the queues were ridiculous, nobody answered their refund request, and your team keeps deleting criticism. Someone has posted a video. The person running your socials wants to know what to say, while production is still trying to find out what happened.

Start by checking whether the complaint describes a problem that is still happening. Get that problem to someone who can act, acknowledge what you know publicly, and give affected people a clear route to help. Keep private booking details out of the comments, but keep information everyone needs in public. Moving a conversation into messages doesn't remove your responsibility to explain a wider failure.

The aim is to help people make their next decision and put right what your event got wrong. That might mean finding another entrance, getting a ticket checked, understanding a programme change, or receiving a remedy. A polished apology won't do those jobs by itself. Here's how to connect the public response with the work behind it, including what to say when you don't yet have the answer.

Find out what people are actually reporting

Read beyond the angriest sentence. "Your event is a scam" might refer to an unannounced artist cancellation, a duplicate payment, a missing accessibility arrangement, or a poster who never bought a ticket. Those situations need different investigations. If your first move is to dispute the word "scam", you've spent the opening exchange avoiding the information you need.

Record the original post, its time, the event and session involved, and the specific experience described. Preserve enough context to understand later replies. A cropped screenshot of one sentence can misrepresent a thread, particularly when the person adds details after your first response. Limit access to records containing personal information and apply your normal retention arrangements rather than collecting everything indefinitely.

Then ask the operational question. Is somebody currently unable to enter? Is the accessible route blocked? Has a visitor reported threatening behaviour? Contact the appropriate duty manager immediately through your event's established incident process. Social media can be where you discover the issue, but it shouldn't become the place staff negotiate an urgent safety response while the problem continues on site.

Check whether other reports describe the same underlying failure. Several comments about missing tickets might be separate email problems. They might also describe one failed send. Don't assume either explanation because it makes the response easier. Ask the ticketing lead to check the records and get the door team to confirm what they are seeing before publishing a cause.

Separate the report's severity from its popularity. An access complaint with little engagement can require immediate action. A widely shared disagreement about your ticket price may need an explanation, but it doesn't automatically deserve priority over someone stranded outside. Use potential harm, whether the problem continues, and who is affected to decide what your team handles first.

If you need help with an encounter happening at the venue, our guide to handling difficult attendees covers staff response and escalation on site. This guide concerns the public conversation around the event. The two processes should exchange verified information, particularly when a complaint describes an experience your staff are still dealing with.

Give someone authority to respond and someone responsibility to fix it

A social media manager can acknowledge a complaint, but they may have no authority to approve a refund, change an entrance, or make a statement about a supplier. Decide who owns those decisions before asking them to reassure anyone. Otherwise, every reply becomes another request for permission while the person complaining hears nothing useful.

For a small event, the same owner might coordinate operations and approve the response. They still need to name who is checking bookings, who is speaking with the venue, and who is watching replies. At a larger event, assign those tasks separately and use one shared record of confirmed facts. Avoid relying on a busy group chat where a correction disappears between unrelated messages.

Business Queensland's guidance on online customer communication recommends deciding who answers for the organisation, which channels they manage, their availability, and when to refer a complaint to someone senior. That is useful preparation for an event team because questions arrive while the people who can answer them are often doing other jobs.

Agree which responses can go out without further approval. An acknowledgement of a reported queue can usually use approved wording. A statement about an injury, discrimination allegation, or disputed cancellation needs the relevant senior lead and specialist advice where appropriate. The approval process should reflect the subject's seriousness while still allowing someone to confirm receipt and explain where help is available.

Keep the facts separate from decisions awaiting approval. "The north entrance is closed" may be confirmed, while an alternative opening time remains uncertain. Let staff communicate the confirmed fact and the available action without inventing the missing time. Record who supplied the information so a later shift knows where to check it, and replace outdated wording when operations change.

Acknowledge the complaint without pretending you know the whole story

Your first public response should show that you've understood the issue, say what you're doing, and tell the person what happens next. You don't need a finished investigation to acknowledge that waiting outside a paid event is frustrating. You do need evidence before saying why it happened or promising that it has been fixed.

Suppose someone writes that their reserved seats were occupied and staff couldn't help. An initial reply could say, "I'm sorry you couldn't use the seats you booked. Our event manager is checking what happened with the seating team. Please use the support form linked on our event page so we can find your booking without sharing its details here." Adapt the route to one your team actually monitors.

That wording accepts the reported experience without declaring a cause. Once you confirm that your team sold the same allocation twice, say so plainly and explain the remedy. If the facts differ, explain the relevant finding without turning the public thread into a cross-examination. The person should be able to understand the decision privately, and other buyers should receive any information that affects their own tickets.

Avoid "we're sorry you feel that way". It locates the problem in the person's reaction while leaving your event's conduct untouched. "We advertised reserved seating and did not provide it" is a meaningful apology when the records support it. When the facts are still unclear, acknowledge what was reported and the impact you can reasonably recognise without supplying a convenient account of events.

For serious incidents, the CDC's Crisis and Emergency Risk Communication manual offers useful principles around accuracy, credibility, empathy, and action. It was developed for major emergencies, including public health situations, rather than ordinary event complaints. Apply that distinction. A drink voucher dispute doesn't need emergency language, while a developing safety incident needs operational leadership and authoritative instructions.

You also need a realistic update commitment. Choose a time your team can meet based on what it needs to check, and specify the time zone if people are following remotely. There is no universal response interval that makes every event complaint acceptable. Someone deciding whether to travel needs information before that decision becomes irreversible, regardless of your usual inbox target.

Decide what belongs in public and what needs a private channel

Public responses should carry information that helps anyone affected. A revised entrance, a delayed start, an explanation of the refund process, or a correction to the advertised offer should be easy to find without sending a message. Individual booking references, payment information, medical details, and personal allegations need a more suitable channel with appropriate access controls.

Tell people why you're moving part of the conversation. "Please contact support" can sound like you're hiding the issue, especially if support has already failed to answer. Explain what details you need, where to send them, and how that route connects with the team reviewing the complaint. Ask whether they've already opened a case so they don't have to start again.

The ICO's guidance on receiving data protection complaints advises asking for another contact method when a complaint arrives through social media because it is generally insecure for sharing personal information. That guidance concerns data protection complaints specifically. For your wider event response, the practical lesson is to avoid collecting sensitive case details in a comment thread or assuming direct messages are secure storage.

If an attendee posts a ticket image, protect the exposed information under your moderation process and contact them through an appropriate route. Don't quote the image in your reply or copy its barcode into a staff chat with broad access. Ask the ticketing team what action is necessary for that booking. The public explanation can say that personal ticket information was removed while the complaint remains under review.

Keep general progress public even when individual remedies stay private. "We have contacted the people affected by the seating allocation error, and the support team is reviewing remaining requests" tells observers what is happening. It doesn't identify buyers, disclose their offers, or claim everyone is satisfied. Only publish completion claims after the responsible team confirms them.

Remember that people can share private replies. Write every case response as if the recipient might post it, while still protecting the information it contains. The standard should stay consistent across public and private channels. A sympathetic comment followed by a dismissive email will create another complaint, and this time the person has evidence of how your team handled the first one.

Publish an update when the issue affects more than one booking

A common failure deserves a common explanation. If an artist cancels, the shuttle stops running, or a ticket delivery problem affects a group of buyers, replying separately to every comment is a poor substitute for an event update. People who haven't complained still need to know whether their plans or purchase have changed.

Use one clearly labelled page or post as the current public update, with a visible date and time. Explain what is confirmed, who is affected, what they should do, and when the next information will be available. Link replies to that update while continuing to deal with individual questions that it doesn't answer. Keep an older update readable as history where useful, but clearly identify the current instructions.

For example, a fictional tasting event discovers that one entrance cannot open as planned. Its first update could explain which ticket holders need to use the alternative entrance, where that entrance is, and whether admission times have changed. If the replacement route isn't suitable for everyone, say how people needing assistance can reach staff. "Follow signs on arrival" is insufficient for someone deciding how to get there.

Coordinate the wording with staff at the door before posting. Confirm that the entrance you name is open and that the people directing attendees know about it. An update can be accurate when approved and wrong by the time it publishes. Ask the operational lead to verify time-sensitive instructions immediately before release, then make sure social staff hear when those instructions change.

Use direct communication alongside public updates. Social distribution doesn't guarantee that a ticket holder will see your announcement. Loopyah's attendee email tools distinguish an update about an event someone has bought from a promotional email, and send event updates to its ticket holders. You still supply the verified explanation and decide what buyers need to know. Confirm the audience and contact route before sending the update.

Check the event page and any scheduled messages too. A corrected post won't help if the ticket page continues to advertise the cancelled session or an automated email sends the old arrival instructions. Pause conflicting promotions, correct the current offer, and brief partners who are directing people to it. Don't continue taking money against a description you now know is wrong.

Apologise for the actual failure and make the remedy understandable

Once you know what happened, explain it with the level of detail the affected person needs. "Unexpected operational challenges" tells a buyer very little. If your supplier didn't deliver the seating you advertised, state the resulting failure and what you are doing for ticket holders. You can investigate responsibility with the supplier separately without making the customer manage that relationship.

The NSW Ombudsman's effective complaint management guidance describes apologies that explain what went wrong, recognise the effect, accept appropriate responsibility, and include action to address it. Its wider guidance is aimed principally at public and community services. Those elements provide a useful way to check an event apology without borrowing jurisdiction-specific legal protections for your own statement.

Match the remedy to the failure and your obligations. A free ticket to another edition may be unwelcome when someone couldn't attend the experience they paid for. A refund may address the ticket cost while leaving an accessibility failure that still needs investigation. Check the applicable terms, consumer requirements, and circumstances before deciding what must be offered. Your financial inconvenience doesn't determine the buyer's rights.

Our guide to writing an event refund policy helps explain the rules before tickets go on sale. During a complaint, read the policy that applied to the person's purchase, including what the offer said at that time. Don't quietly rewrite today's page and treat the new wording as proof of what an earlier buyer agreed to.

Explain eligibility, how requests are made, what information is needed, and what timing you can support. Distinguish a decision to approve a refund from the payment being processed and reaching the buyer. If a payment provider controls part of that timing, use its current guidance. Don't promise a bank arrival date merely because someone on your team has approved the request.

Apply the same criteria to comparable cases, whether someone complained publicly, emailed quietly, or has a large following. Keep a record of justified exceptions and who approved them. If a failure affects a clearly identifiable group, work out whether you can contact them proactively. Requiring every buyer to argue their own case can leave the least persistent people with the worst outcome.

Moderate harmful content without hiding reasonable criticism

Your moderation policy should distinguish criticism from conduct that harms other people or prevents the channel being used. Someone saying the show was poor value is expressing dissatisfaction. Someone posting a crew member's home address or making a threat creates a different problem. Keep the complaint process available while dealing with that conduct through your safety and moderation procedures.

Publish understandable rules and apply them consistently. Record the reason for a significant removal, preserve necessary evidence appropriately, and limit access to it. Explain moderation decisions where that helps people understand what happened without repeating the harmful material. Avoid claiming that every negative comment breaches a rule merely because the discussion is uncomfortable for your brand.

In the United States, the FTC's Consumer Review Fairness Act guidance explains that standard consumer contract terms cannot prohibit or penalise honest reviews. It also distinguishes potentially removable material, including private information and harassment, from opinions a business simply dislikes. That's a specific legal context, but it reinforces a sensible operating decision. Don't write ticket terms designed to silence genuine complaints.

Don't offer a remedy on condition that a buyer deletes criticism. Resolve the case on its merits. If someone later chooses to update their account, that's their decision. Asking staff, friends, or sponsors to flood the thread with praise is also a poor response. People need evidence about the reported failure, and your team needs time to address it.

When a comment contains a factual error, correct the specific fact with evidence you can share safely. "The event has not been cancelled; doors remain open at the time shown on the event page" is useful if verified. Avoid repeating an unsupported accusation in a prominent standalone post simply to deny it. Respond where the misunderstanding is happening unless its reach or effect justifies a broader correction.

Some posters will keep arguing after a clear answer and a genuine route to review. You can restate that route and stop repeating the exchange. Keep watching for new facts and further affected people. Ending an unproductive conversation is different from deciding the complaint no longer deserves investigation. Staff should also be able to hand over abusive interactions and receive support after them.

Handle controversy about your choices without inventing agreement

Some criticism concerns a choice your event made rather than a service you failed to deliver. You booked an artist whose conduct people question, accepted a sponsor some attendees oppose, or changed programming that regulars care about. A refund script alone won't answer why the decision was made. You need to understand the objection and decide whether you stand by the choice.

Start by checking the specific allegation or concern with the people responsible for the booking. Distinguish documented facts, disputed accounts, and opinions about what your event should support. Don't ask the social team to declare an allegation false because a partner objects to the attention. Equally, don't publish an accusation as fact because many comments repeat it. Serious allegations require appropriate investigation and advice.

Then decide what you can explain about your own conduct. You may be able to describe the criteria used, what information was available when the decision was made, and whether new information changes the assessment. Protect confidential and personal information, but avoid using confidentiality as a blanket answer to questions about your standards. Explain the decision you control and any limits on what you can responsibly disclose.

Suppose a fictional conference accepts a sponsor whose public activities conflict with its stated environmental commitments. People ask how the partnership was approved. A useful response explains the review, whether those commitments were considered, and what the event will do now. Telling people that sponsorship pays for production may be true, but it doesn't answer the inconsistency they identified.

If you keep the partnership, acknowledge that some attendees will disagree and explain your reasons without portraying criticism as disloyalty. If you end it, confirm the decision before announcing it and check the effects on the programme and buyer offer. Either way, give people information they need about their tickets and where individual questions will be handled. Agreement isn't something you can promise on their behalf.

Use a spokesperson when explaining the decision requires judgment and accountability. That may be the founder or event director, supported by the person checking the facts. A video can convey seriousness, but text should carry the essential information too. People should be able to find the actual decision without watching a lengthy statement or interpreting a facial expression.

Pause unrelated celebratory posts while the team assesses a serious issue. Decide what can resume based on the situation, rather than waiting for every critical comment to disappear. An operational update about tomorrow's entry arrangements may still be necessary. A sales countdown that ignores unresolved questions about the advertised programme can make your next public response harder to believe.

Work through a complaint before it turns into a second failure

Consider a fictional paid conference where buyers discover that a workshop advertised as included requires a separate booking. The social team initially assumes people missed an instruction. Before posting that explanation, the event manager compares the purchase page with the confirmation email and discovers that the booking requirement wasn't included in the offer buyers saw.

The first acknowledgement should recognise the confusion and confirm that the team is checking access arrangements. It shouldn't tell people they misunderstood instructions that didn't exist. The programme lead then checks workshop capacity and available alternatives. Finance reviews possible remedies. The public response depends on those decisions, rather than a writer trying to invent an attractive answer while the allocation is unresolved.

If additional sessions can be delivered, confirm their hosts, rooms, capacity, and booking process before offering them. If some buyers still cannot receive what was promised, explain the available remedy through the appropriate channel. Update the event page for future purchases and contact existing buyers about the difference. A correction for new customers doesn't resolve the earlier commitment.

Now imagine the first update promises that every request will be reviewed by Friday, but the support team cannot finish. The next decision is straightforward. Tell affected people before the promised point passes, explain what remains, and provide a revised commitment that the team has checked. Repeating "we're experiencing high demand" without a useful next step leaves buyers planning around information you know is unreliable.

By the following edition, the improvement should be visible in the buying process. The event page explains whether a separate booking is needed, confirmations repeat that instruction, and support staff can check allocations. Announcing that you "take feedback seriously" adds little if the same ambiguity returns. The change should prevent the complaint's cause, rather than merely reduce the number of comments about it.

Check the answers people will receive next

Before publishing the conference update, test the support route from the buyer's position. Does the form ask for a booking reference they can find? Does its confirmation say when someone will reply? Will an existing complainant receive a contradictory automated message? Have the staff reviewing requests seen the same eligibility explanation that appears in public? These checks catch failures that proofreading the statement won't reveal.

Ask the person responsible for support to read the announcement. If it promises individual contact, confirm who will make that contact and how the affected bookings will be identified. If it invites everyone to submit a request, check that the team can distinguish duplicate requests without losing new information. Keep a route for someone whose purchase used a different email address or who bought as part of a group.

When you cannot yet offer a complete answer, explain the part you are checking. For this fictional conference, that could mean confirming whether another workshop session can run, with a stated next update. Don't offer a waiting list as a substitute for explaining that the purchased inclusion is currently unavailable. People may accept uncertainty when you describe it honestly; they cannot make a useful decision around a promise your team has invented.

If a journalist asks for comment, identify their question and deadline, then direct it to the agreed spokesperson. Keep their request separate from the customer's support case so media attention doesn't determine who receives help. Use the same confirmed facts in both responses, while protecting individual details. If the journalist's deadline arrives before your investigation finishes, explain what is confirmed at that point and when you expect another update. Don't guess to fill the space, and don't describe an unresolved allegation as settled because the event needs a statement before the evening news runs.

Prepare the next shift and review what changed

Before handing over, record outstanding cases and the promises your team has made. Include the latest approved public wording, the operational contact, unresolved factual questions, and the next update time. Make clear which remedies have been authorised and which are still proposals. The next person should be able to continue a case without asking the buyer to retell an upsetting experience.

Check that your contact route works for people who don't use social media or cannot complete the form you chose. Offer a practical alternative and tell staff how to manage it. A complaint process fails if someone needs to create an account on the very channel where they've reported harassment, or if an inaccessible form prevents them explaining an access problem.

After the immediate issue settles, review the operational cause and the communication separately. Did the advertised offer match delivery? Did reports reach the right person? Were updates accurate when published? Did you meet your own commitments? A quick acknowledgement can coexist with a poor remedy, and a fair eventual remedy can follow several avoidable days of confusion.

Count distinct cases rather than treating every comment as another affected buyer. Keep repeated questions visible as evidence that the public explanation may be unclear, while checking how many actual bookings were affected. Don't claim silence proves satisfaction. People may stop replying because they received help, gave up, or chose another channel. Use case outcomes and direct follow-up to understand which explanation fits.

Our guide to measuring attendee trust can help you check whether buyers believe your next set of promises. For the complaint in front of you, finish the practical work first. Confirm that the remedy happened, communicate any remaining limitation honestly, and make the operational change before you sell the same experience again.