How do you market an event after bad reviews?

You've announced the next edition, and somebody comments, "Have you fixed the queues this time?" Then another person asks about the workshop they paid for but couldn't get into. Your new lineup might be excellent. Right now, those buyers want an answer about the last event.

To market an event after bad reviews, first establish what went wrong and make the changes you can actually deliver. Then explain those changes in the places buyers will check before paying again. Handle outstanding complaints separately, give returning customers a clear account of the next edition, and increase promotion only when the offer and the delivery plan agree.

That doesn't require a campaign built around apologising forever. It requires enough honesty for someone to make a fresh decision. A customer should be able to understand what happened, what you've done about it, and what they're buying now without piecing together a comment thread.

We'll work through a fictional paid food festival whose entry delays and oversubscribed tasting sessions disappointed buyers. The event, messages and financial figures below are teaching examples, not customer results or industry benchmarks. The same decisions apply to a conference with a weak programme, a music event with poor communication, or a workshop that promised more individual feedback than it delivered.

Work out what people are asking you to fix

Start with the actual gap between the advertised event and the experience people received. "People were unhappy" is too broad to guide another production budget. "The ticket page implied that every ticket included a tasting session, but places were allocated first come, first served" tells you which promise needs attention.

Bring together the event description, ticket inclusions, support messages, public reviews and the team's records. Read the version buyers saw at the time. A page corrected after the event doesn't establish what someone reasonably expected when they booked. Keep the original wording available to the people reviewing the complaint.

Separate documented facts from explanations you still need to check. A buyer can accurately describe waiting outside without knowing why admission was slow. Your team can accurately report that scanners worked without establishing that enough people could enter through the space available. Neither account cancels the other out.

For our fictional festival, suppose the evidence supports two problems. Admission started later than advertised, and tasting sessions filled before some ticket holders could claim a place. Those are different failures. One concerns the arrival operation. The other concerns how the offer was described and how scarce places were distributed.

Ask what each complaint means for the next purchase. Someone who missed a tasting needs to know whether a future session is included and reserved. Someone who waited outside wants to understand the arrival arrangements. A generic statement that you've "improved the experience" answers neither question well enough.

Sometimes you delivered the advertised programme and people still didn't find it worth the price. A conference can run on time with every named speaker present and still disappoint experienced attendees because the sessions were too basic. Check whether you described the level accurately, whether you reached the right audience and whether the next programme is stronger. You may need to change the offer itself. An apology about logistics won't answer a complaint about the substance of the event.

You don't need to count every unhappy post as a different affected customer. One person may contact support, post a review and comment on the announcement. Keep those records connected where you can do so appropriately, while preserving each account. Otherwise you can exaggerate the number of people affected and still overlook a smaller group with a more serious problem.

Use an event debrief to establish causes and assign the work. The marketing decision comes afterwards. Which findings affect what you can promise publicly, and which changes are ready to describe? A debrief full of recommendations doesn't mean the next event already delivers them.

Don't let the loudest topic determine the whole response. A disputed parking complaint might dominate social comments while a small number of accessibility complaints reveal a much bigger delivery problem. Assess the consequence and investigate the evidence. Popularity in a comment thread is a poor way to decide what deserves money and attention.

Decide whether the next edition is ready to sell

Before drafting the comeback announcement, ask the person responsible for delivery a direct question. If people buy today, can we provide the event this page describes? If the answer depends on an unsigned venue agreement, an unapproved staffing budget or a session-booking arrangement nobody has tested, the claim needs to wait or become narrower.

There is a useful distinction between an improvement you've proposed, one you've arranged, and one you've seen work under relevant conditions. You might have asked the venue for another entrance, received agreement to use it, or actually tested the route and admission procedure. Say which of those things is true. They give buyers different levels of information.

For the food festival, the team could confirm the permitted entrance arrangements with the venue and agree the staffing plan. It could also change tasting tickets so each one names a reserved session. Those are concrete changes. Promising that nobody will queue or that every attendee will be delighted would go well beyond what those arrangements establish.

Check that your proposed fix addresses the cause. More admission staff won't resolve an entrance that cannot open until production clears the route. A new booking screen won't create more tasting places. If there are fewer places than general admission tickets, the offer has to make that difference clear before purchase.

Where the previous edition involved safety concerns, injuries, safeguarding complaints or a serious incident, the responsible operational and professional review comes first. Follow the investigation and reporting requirements that apply to the event. A marketing timetable cannot decide when an unresolved safety issue is ready to be described as fixed.

For events in Great Britain, the HSE's guidance on managing an event recommends monitoring and reviewing arrangements, including a debrief after significant incidents. Check that the agreed changes are working and being followed. A completed review doesn't certify your next event or establish a date on which promotion can resume.

Sometimes the sensible decision is a smaller edition. You may be able to deliver a well-run seated tasting before you're ready for another festival. Explain the actual format and sell it on its own terms. Don't present a reduced offer as identical to the previous event with all its problems solved.

If the unresolved work affects the central reason someone would buy, delay taking payment until you can describe the offer accurately. You can keep people informed about progress without asking them to finance an uncertain promise. Whether that means postponing an on-sale date or changing the programme is a business decision you need to make before the campaign calendar becomes a commitment.

Put the previous customers' unresolved problems first

A better next edition doesn't automatically settle a complaint about the last one. Someone who paid for an inclusion they didn't receive may be asking for an explanation, a refund or another remedy. An invitation to buy again can feel evasive when that original request remains unanswered.

Review outstanding cases with the person authorised to decide them. Check the applicable consumer rights, ticket terms and facts of the purchase before offering an outcome. Don't invent a universal rule that disappointment always entitles someone to a refund, or that a completed event rules a refund out. The details and jurisdiction matter.

Give the customer a useful next step. Explain what information you need, where they can provide it privately and when they should expect another update. Set a response time the team can meet. "We'll come back to you soon" leaves the customer unable to tell whether their case is moving at all.

Keep the decision record separate from promotional activity. You need to know what was offered, what the customer accepted and what has actually been completed. A support reply saying a refund was approved isn't the same as confirmation that it was processed. Check the payment record before telling someone the issue is closed.

In the fictional festival, a buyer who missed a tasting should receive a review of that purchase. The next festival's reserved sessions can explain how future bookings differ, but they don't replace the review of the earlier ticket. Both jobs need an owner. Neither should disappear because the new announcement is getting good engagement.

Don't make assistance depend on a review being removed, changed or kept private. If you offer a goodwill benefit, state its purpose and conditions clearly, without tying it to praise. A customer can accept a remedy and still accurately describe what happened at the event.

This also changes the timing of your campaign. Before a promotional send reaches previous buyers, check whether your support team is ready for replies about unfinished cases. You don't need every customer to agree with every outcome before ever selling again. You do need a fair, functioning process and an honest account of anything still unresolved.

Protect the person's privacy throughout. The public needs to understand the event's response, not the details of an individual's payment, access requirements or personal circumstances. Move those details into the support conversation. A persuasive public defence of your business is a poor reason to expose a customer's information.

Write an acknowledgement that answers the complaint

The best acknowledgement names the problem in words the affected buyer recognises. If entry opened late, say that. If the tasting allocation was unclear, say that. "We're sorry that some people felt disappointed" moves the sentence towards their feelings and away from what your event did.

You can be direct without claiming facts you haven't established. Explain what the records confirm, what you're still checking and when you'll provide the next update. If an investigation remains open, have the responsible person review the wording. Don't speculate about a supplier's motives or publish an explanation simply because it makes the organiser look better.

Here's illustrative wording for the festival, assuming both findings have been confirmed. "Entry started late at our previous festival, and our ticket information didn't make the tasting allocation clear enough. Some ticket holders missed the session they expected to attend. We're sorry. We've contacted affected buyers about their individual cases and changed how entry and tasting bookings will work for the next edition."

Only use the statement about contacting buyers if that contact has happened. If you are still working through the cases, say so and provide a realistic update date. Completed language is tempting because it sounds reassuring, but it creates another promise people can check against their inbox.

Follow the acknowledgement with the changes buyers need to assess. Don't bury them beneath paragraphs about how hard the team worked. People can appreciate the effort and still want the event they paid for. Your account should make room for that without asking customers to reassure you.

One named spokesperson should approve the shared explanation. Support staff can personalise replies, but they shouldn't each invent an account of what caused the failure. Give them the confirmed facts, the current changes and the person who can answer an unresolved question. That is especially useful when partners and venue staff also receive complaints.

Place the acknowledgement where the concern exists. A pinned update can answer a recurring social question, while the event page explains the future offer. Individual support messages address individual cases. You don't need to insert the full history into every new advertisement, but a buyer who looks for your response should be able to find it easily.

Avoid an apology followed immediately by a countdown or discount code. Give people enough space to understand the response before asking for another purchase. The next edition can have a sales campaign; the acknowledgement has a different immediate job.

Show exactly what has changed for the buyer

Build the explanation around the buyer's previous problem and the new arrangement. For our festival, the tasting issue becomes a clear ticket choice. General admission covers entry and the stated festival programme. The admission-and-tasting ticket covers that same entry plus one named session, selected when booking, with its time and conditions visible before payment.

That is only an example of a possible offer. If your commercial model includes a tasting in general admission, describe how that included place is secured. The important part is consistency. The headline, ticket description, confirmation and staff answers must describe the same entitlement.

For admission, explain the confirmed entrance and arrival instructions. You could show which route each ticket holder should use and when the doors are scheduled to open. Avoid promising a maximum wait unless you have suitable evidence and a delivery arrangement capable of supporting that promise. Another entrance alone doesn't establish a guaranteed waiting time.

Use proof that fits the claim. A confirmed timetable supports a statement about scheduled sessions. A venue-approved route supports an explanation of where people enter. A rehearsal can show that staff understand the procedure under the conditions tested. A photograph of a smiling team doesn't establish that any of those arrangements work.

The UK's ASA and CAP explain in their guidance on substantiation that objective advertising claims need documentary evidence before publication. For this campaign, keep the evidence for statements such as reserved places or extra provision with the approved copy. Check the rules in each market where you advertise, too.

You don't have to publish confidential supplier contracts to explain a change. Describe the relevant arrangement accurately, obtain permission for any material you share, and keep supporting records available internally. A supplier's commercial terms can remain private while buyers receive a clear account of their ticket.

If the change costs you more, explain its benefit rather than asking the audience to applaud the spending. "We've invested heavily" gives a buyer very little to judge. "Your tasting time is selected when you book" tells them what they can rely on when organising their day.

Be equally clear about what hasn't changed where it affects the decision. If the venue still has outdoor waiting areas, say how arrival will work in that setting. If a ticket still excludes workshops, make that visible. A buyer should not discover the remaining limitation after paying because the campaign concentrated entirely on the improvement.

Give the event page enough detail to support a fresh decision

Your new ticket page needs to stand on its own. Someone discovering the festival for the first time should understand the current programme without studying last year's dispute. Someone returning after a poor experience should be able to find the changed arrangements without guessing whether the same problem remains.

Start with the current date, location, programme and ticket inclusions. Then add a clearly labelled section explaining the changes for this edition. Use the buyer's question as the heading where it helps. "How do tasting bookings work this year?" is easier to use than a broad promise about taking the experience further.

For the fictional festival, the section could explain that the admission-and-tasting ticket reserves a named session as well as festival entry, general admission alone doesn't include a tasting, and the confirmation shows the booked time. It should also explain the conditions for arriving late, changing a booking and receiving any included materials. Decide those conditions before writing the reassuring version.

Make the arrival information practical. Name the entrance, show the accessible route where relevant, and explain how ticket queries are handled. Verify that this information matches the venue arrangement and the staff brief. A clear page can still disappoint customers if the onsite team has been told something different.

Keep any previous-edition material accurately labelled. A video of last year's programme may show why the event is appealing, but it shouldn't imply that every activity shown is included this year. Check old captions, reused graphics and partner pages as well as your main ticket description. Buyers can encounter any of them first.

Use a visible support route for unanswered questions. That doesn't mean turning the purchase page into a complaints form. It means giving someone a way to clarify the exact issue stopping them from booking. If a question appears repeatedly, answer it on the page so the next buyer doesn't need the same exchange.

Update the event marketing plan around those buyer decisions. The campaign needs time for people to read the changed offer and ask questions. A timetable made entirely of price reminders assumes the problem is procrastination, when the buyer may still be deciding whether to trust the offer.

Before launch, ask someone who wasn't involved in writing the page to explain the ticket back to you. What do they think is included? How do they get a tasting place? Where do they go on arrival? Their answers can reveal an unclear promise while you still have time to fix it.

Invite previous buyers without assuming they're ready to return

Previous customers need different information depending on their experience. Some enjoyed most of the festival and want reassurance about arrival. Some missed a paid inclusion and are still waiting for an answer. Others bought for friends and may not know exactly which problem each guest encountered.

Don't write as though everyone had a terrible time, and don't assume everyone has forgiven the event. Describe the confirmed issue, link to the changed arrangements and let people decide whether the new offer suits them. You can acknowledge mixed experiences without conducting a public vote on whether the complaints were justified.

Send invitations only to people you can lawfully contact with that promotion. A customer-service conversation about an earlier purchase doesn't automatically provide permission to market the next edition. Keep a reply about a complaint focused on that case rather than adding a ticket offer and treating the whole message as customer service.

In the UK, the ICO's electronic mail marketing guidance explains when consent or a valid soft opt-in can apply to individual subscribers. The products-and-services soft opt-in has specific conditions, including direct collection during a sale or negotiations, similar services, and opt-out opportunities at collection and in later messages. A past purchase alone isn't enough. Check the relevant requirements for your audience and location.

Loopyah's attendee email tools let you select audiences using purchase information and distinguish promotional sends from updates about a purchased event. Opt-outs are removed from promotional audiences. That helps you contact the relevant previous buyers; your team still needs to write the explanation and decide which customers need individual support before receiving another invitation.

Here's a sample promotional email for reachable previous buyers after the festival's new arrangements are confirmed. Its wording is illustrative, and the named changes must be true before you use it.

Subject: What's changing at the next Riverside Food Festival

"If you came to our last festival, you may have waited longer than you expected to get in, or missed a tasting because the allocation wasn't clear. We've reviewed both problems. For the next edition, tasting tickets reserve a named session when you book, and the event page explains the confirmed entrance and arrival arrangements.

"You can read the programme, ticket inclusions and changes before deciding whether to join us again. If you still need help with your previous booking, reply to our support team through the contact details on that page. Your case doesn't depend on buying another ticket."

That invitation leaves room for someone to decline. It also directs an unresolved complaint to a real process. Include the correct support contact and a clear unsubscribe route in the actual email, and check that replying works. A thoughtful message sent from an unattended address can undo its own promise to listen.

If someone responds with criticism, answer the concern before sending another sales reminder. Some replies will reveal an incomplete fix. Others will show that the explanation needs work. Neither is a reason to keep increasing send frequency until people stop replying.

Respond to public reviews without trying to win the argument

A public reply has more than one reader. The reviewer needs a response to their experience. A prospective buyer wants to see whether your business understands the problem and can explain its next step. Keep the reply specific enough to help both people without exposing private case details.

Google's guidance on responding to reviews recommends clear, relevant replies, protecting privacy and moving complex details into a private conversation. On Google Maps, incentives for posting, changing or removing reviews are prohibited. Check the policies of any other review service you use rather than assuming the same approach is allowed everywhere.

A short illustrative reply could say, "We're sorry you missed the tasting you expected. Our ticket information didn't explain the allocation clearly enough. Please contact the support address on our event page so we can review your booking privately. Next edition's tasting tickets reserve a named session when purchased."

Only acknowledge that particular failure when you've established it, and don't imply that the future arrangement resolves this person's case. If the customer has already contacted support, check that record first. Sending them back to the start without recognising the earlier contact can be more frustrating than the original reply.

Correct a factual error calmly when you have evidence. If the review names the wrong venue, explain the distinction without using it to dismiss unrelated concerns. If the reviewer describes a queue you cannot verify, say what you can check and invite the details privately. "We can't find your booking" is a request for information, not proof that the review is false.

In the US, the FTC's consumer reviews and testimonials guidance addresses false accusations, intimidation and unfounded legal threats used to suppress reviews. It also warns that paying people to remove truthful negative reviews may violate the FTC Act. Let customers describe their real experience without pressure to make the public record more flattering.

Moderation still needs rules. Remove or report material under the platform's applicable policies, such as exposed personal information or threats, and apply the same standards regardless of sentiment. Preserve an appropriate internal record where needed. Don't describe a page as open feedback while quietly excluding every critical account.

Avoid asking employees, suppliers or friends to flood the page with praise after a bad review. Their involvement can distort what prospective buyers think they're reading, and relationships may require disclosure. A genuine account of the next edition is more useful than a sudden burst of comments from people who never bought a ticket.

Some people won't accept your response. You can state the confirmed position, keep a reasonable support route open and stop repeating the argument publicly. Exhausting the reviewer into silence doesn't establish that your event has improved.

Choose a return offer that the event can afford

A returning-buyer offer can be reasonable after you've addressed the delivery problem. It can acknowledge the relationship or make a second visit easier to consider. But a lower price doesn't answer whether the tasting is included, and it can't substitute for a remedy owed on the earlier purchase.

Decide what the offer is for before choosing the amount. Is it a goodwill gesture for an affected group, a promotional invitation for previous buyers, or compensation agreed through an individual case? Keep those purposes clear in the wording and records. A discretionary marketing offer mustn't be presented as the customer's only available option when other rights may apply.

Here's a fictional calculation in USD. Suppose a standard ticket leaves $40 after the costs that increase with each attendee, before fixed event costs and campaign spending. A $10 discount reduces that amount to $30, assuming those attendee costs stay the same. That is $10 less available from every discounted sale to cover the rest of the event.

Imagine 100 previous buyers would each have booked one ticket at full price anyway, while the offer persuades 20 additional people to attend. Without the offer, those 100 buyers provide $4,000 towards the remaining costs. With it, all 120 discounted tickets provide $3,600. Attendance has risen, but the amount available towards fixed costs has fallen by $400, before any extra campaign cost.

At $30 left per discounted ticket, you would need at least 134 discounted sales to exceed the original $4,000, which would leave $4,020. That's 34 additional sales compared with the original 100. This isn't a forecast that the offer will produce them. It shows what the assumption would require.

You won't know perfectly who would have purchased anyway. Make a conservative estimate using previous buying behaviour and record the uncertainty. Don't celebrate every redemption as an additional sale. The code proves that someone used the offer, not that they needed it to decide.

Capacity changes the calculation too. If the smaller, improved edition has limited places, a broad discount might fill seats that would otherwise sell at full price. An extra paid benefit also has a delivery cost and may recreate the scarcity problem you just fixed. Check whether it can be provided to every eligible buyer before announcing it.

Budget separately for settling earlier complaints, even if the recipients never attend again. If some customers later buy tickets, you still need to record what the business spent resolving the previous event's problems. Keep that cost visible when assessing how much the next edition can afford to spend on promotion.

You can choose to spend on goodwill even when it doesn't maximise immediate ticket income. Just name the decision honestly and fund it. A deliberate relationship expense is easier to assess than a discount described as profitable solely because more tickets were redeemed.

Relaunch in a sequence your team can support

Start by making the confirmed explanation and new ticket information consistent. Then brief the people who will answer questions, including venue contacts and any partners sharing the event. Only after that should you send the next invitation. Otherwise your campaign can reach customers before the team knows what has been promised.

A practical sequence is to finish the relevant complaint updates, publish the current arrangements, invite reachable previous buyers, and review the questions before expanding promotion. These activities can overlap when the work is ready. There isn't a universal waiting period after a bad edition, and a quiet week doesn't itself establish that the underlying problem has gone away.

Give previous buyers a reasonable opportunity to read and respond before committing the next advertising budget. Choose that review point according to your sales lead time and support capacity. A workshop happening soon needs a different timetable from an annual festival that requires travel. Record what you need to learn and the spend you are prepared to risk.

When you introduce the event to new buyers, lead with the actual programme. They need a reason to attend, plus the information required to understand the offer. Make your account of the previous problems accessible, and answer a direct question honestly. You don't have to turn every prospecting ad into the full history of your business.

For the festival, an ad could describe the producers attending, the demonstrations included in admission and the separate reserved tastings. The landing page then explains the ticket choices and changes. Avoid creative showing a tasting as universally included if the advertised price buys general admission only. The first impression and the detailed page should agree.

Partners need the same care. Supply the current inclusions, approved claims and the route for difficult questions. Ask them to replace outdated material they control, and verify important changes. A partner can accidentally repeat last year's promise even after you've corrected every page you own.

If you invite someone to inspect preparations, be accurate about what they saw. Walking through an empty venue can explain the layout; it doesn't establish how the entrance will perform with a crowd. Don't turn a preview into a testimonial about an event that hasn't happened. Let the person describe their actual experience and disclose relevant benefits or relationships where required.

Choose the next spending decision from what you've learned. If people understand the new offer but dislike the date, more reassurance about queues won't solve the problem. If people keep asking whether tastings are included, the page still needs work. Fix the question that is actually stopping the purchase before buying more visits to the same explanation.

Measure whether people understand the changes

Before the relaunch, write down what you'd expect to see if the response is helping. The useful signs might include fewer repeated questions about tasting allocation, completed complaint follow-ups and paid bookings from eligible previous buyers. Keep each measure connected to a decision. A rise in social engagement could mean interest, criticism or both.

Read replies alongside sales. A customer saying, "I understand the new arrangement, but I can't make that date," tells you something different from, "I still don't know what my ticket includes." The first may need no further persuasion. The second tells you to improve the offer explanation.

Use consistent definitions for returning buyers. Someone who purchased two tickets last year is one buyer with two tickets, not two independently identified returning customers. Refunded purchases and complimentary admissions need their own treatment. Decide which records count before comparing editions so the result doesn't change with whichever definition looks strongest.

For example, if a fictional invitation reaches 200 eligible previous buyers and 20 of them book, that's a 10 percent buyer booking rate for that group and period. It doesn't mean 90 percent distrust the event. Some may be unavailable, uninterested in the new programme or buying later. Check the reasons you can actually observe.

Don't treat campaign-attributed purchases as proof that the apology or changed wording caused the sale. Buyers may have seen partner content, spoken to friends or already intended to return. A report helps you describe what happened under its attribution rules. It doesn't isolate the effect of each part of the recovery effort.

Our guide to measuring attendee trust explains how to ask about confidence in specific promises and interpret the answers carefully. Use that work when you need a consistent measure across editions. Here, the immediate question is narrower: can buyers understand the changes, and are there unresolved concerns your team can act on before the next event?

Review spending against the revised event budget as well. Include corrective production costs, complaint handling, any discretionary return offer and the campaign itself. A successful sales relaunch can still leave the edition financially weak if you kept the old cost assumptions after changing how the event operates.

Set a limit for extra promotion before the results arrive. If sales are below the level needed to justify the next commitment, decide whether to narrow the event, seek another confirmed income source or stop additional spending. Avoid raising the budget simply because the business now feels it has something to prove.

Make the next event produce evidence you can use

The next edition is where buyers experience the change. Make sure the delivery team knows which promises the campaign emphasised and how to check them. If you've sold reserved tasting sessions, staff need the booking information, the relevant admission procedure and a way to resolve a disputed place. Accurate copy cannot compensate for an onsite handover nobody arranged.

Record what happened at the points you changed. For the festival, check when admission opened, how the planned routes worked and whether booked tasting places were available to the people entitled to them. Use records appropriate to the task and protect personal information. You want evidence that can improve operations, rather than a content team hunting only for flattering moments.

If something fails again, respond to that actual problem. Don't insist that the campaign's reassurance must have been correct because the revised plan looked good. Explain what has happened, support affected customers and reassess the arrangement. Repeating a confidently worded promise after the team has evidence against it makes the next conversation harder.

Ask for feedback consistently after the event, including from customers who raised concerns. Keep the request neutral and voluntary. A useful reply might confirm that booking a tasting was clearer while pointing out that the session still started late. Preserve both parts; the remaining criticism tells you what to investigate before calling the change a success.

Use future public claims only at the level the evidence supports. You might be able to say that tasting places were reserved and delivered for that edition, if the records establish it. That doesn't justify saying every attendee trusted the event again. A strong result on one operational change is still a result on that change.

Before you approve the relaunch, put the revised event page beside the delivery plan and the outstanding complaint record. Check each statement about what has changed, who will provide it and what remains unresolved. If the central promise still depends on work nobody has confirmed, fix that first. Then you can ask buyers to return with an offer your team is ready to honour.