How to use attendee testimonials on a ticket sales page

You've got a folder of lovely comments from your last event. People enjoyed themselves, the team is proud of the feedback, and someone suggests putting all of it on the next ticket page. It sounds sensible. But which comment would help a person who's interested and still hasn't booked?

Start with what that buyer is unsure about. Choose a genuine attendee comment that speaks to that question, check that it describes the experience you're selling now, and get permission for the exact words and credit you plan to publish. Place it beside the relevant programme or ticket explanation so the reader can use it while deciding.

Someone wondering whether a workshop suits beginners needs a different comment from someone weighing up an expensive conference pass. "Amazing event" doesn't tell either person very much. A guest explaining what they could follow without previous experience, or how a session helped them work through a specific problem, gives the buyer something to judge.

You don't need to turn your page into a wall of praise. You need enough relevant evidence to help people understand the offer, followed by a straightforward route to buying it. This guide covers selecting quotes, getting approval, editing without changing meaning, placing testimonials, and checking whether the work is useful. We'll use a fictional paid workshop to work through the decisions, including what to do when the best feedback isn't suitable for publication.

Start with the booking doubt you need to answer

Before looking through comments, read your ticket page as someone who hasn't been to your event. They know less than your team does. A phrase like "practical sessions" might mean hands-on work, a demonstration, or a talk with a few questions at the end. Your returning guests may understand it. A new buyer has to guess.

Look at recent enquiries, refund explanations, and questions under your announcements. Separate missing information from uncertainty about the experience. "What time does it finish?" needs a finish time. "Will I be able to follow this without experience?" needs a clear explanation of the level, and might also benefit from a previous beginner's perspective.

Don't make a testimonial do the work of a missing fact. If the buyer needs to know whether dinner is included, say whether dinner is included. A delighted guest mentioning the food could have bought a different pass or attended a sponsor dinner. Their enthusiasm doesn't establish what the next ticket includes.

Imagine you're selling a beginner printmaking workshop. In this fictional example, the next edition includes an introduction, a guided practice session, and materials for making a print. Your enquiries suggest that people are worried about arriving without drawing skills. The first improvement is to explain which skills the session requires and what the tutor teaches. Then you can look for an approved comment from someone who attended at that level.

The comment should add a person's experience to that explanation. Perhaps a previous guest describes how the tutor demonstrated the first step and gave them time to practise. That would help someone picture the teaching. A comment about the playlist might be lovely, but it doesn't answer the question holding this buyer back.

Choose the doubts that matter to this event. A professional conference might need to explain how much discussion happens outside the main talks. A seated music night might need to make the listening environment clear. A paid food event might need to explain portion sizes and how the tasting works. The useful testimonial changes with the purchase.

Keep the wider campaign in view, too. Our guide to an event marketing plan explains how the audience, offer, channels, and sales targets fit together. For the ticket page, narrow that thinking to the decision the reader is making now. You can't answer every possible concern with one quote, and you don't have to.

Choose a quote that describes the relevant experience

A useful testimonial gives the reader something more specific than your own promise. For the workshop, a guest's account of following the demonstration tells us about the teaching. A comment about leaving with a finished print tells us what that particular guest completed. Neither automatically proves that every attendee will have the same result.

Start by checking the original material. Which event did the person attend? Which session or ticket did they use? Were they a paying attendee, an invited guest, a speaker, or someone working on the event? Did they write the words themselves, or are you looking at a team member's summary of a conversation? Get those answers before deciding the quote is publishable.

Relevance can be quite narrow. A guest who praised the small-group masterclass may have had direct access to the tutor that a general admission buyer won't receive. If you put that quote beside the general pass without explaining the difference, the reader could expect something you're not offering. Put it with the masterclass description if the current edition genuinely includes the same experience.

Dates and locations matter for the same reason. Praise for comfortable seating at the old venue doesn't tell a buyer about the new room. A recommendation for a weekend programme may say little about a shorter evening version. Keep the edition visible and check which parts of the praise still apply. A date label alone won't fix an overall impression that the next event includes something it doesn't.

Now compare the comment with the question you identified. Would a buyer learn anything about the teaching, atmosphere, programme, or ticket value? Or would they only learn that someone liked you? A short specific comment can be useful without being dramatic. You don't need the most flattering sentence in the folder.

There is also a difference between an experience and a claim that needs separate evidence. "I enjoyed talking to the other attendees" describes a person's response. A claim that your conference guarantees clients, or that a wellness session treats a condition, creates a much bigger promise. Quoting someone else doesn't remove your responsibility for what the page communicates. Leave out claims you cannot support.

The US FTC's Endorsement Guides guidance says endorsements must reflect honest opinions and cannot make claims the advertiser couldn't legally make. It also addresses unexpected connections that could affect how people judge an endorsement. Treat a guest's comment as advertising once you choose to use it to sell the next event.

If you can't establish what the person experienced, keep the comment out of the sales page until you can. Ask them which session they attended and what they were referring to. They may have meant something quite specific that the original message didn't explain.

Ask for useful feedback without writing the praise yourself

The easiest comments to use often come from a specific, neutral question. Ask what the person attended, what they expected, and what the experience was like. Give them room to say that something didn't work. A request that assumes everyone loved the event is poor research, and it can produce strangely similar answers.

For the fictional workshop, you might ask whether the pace matched the guest's experience and which part helped or frustrated them. Someone could explain that the opening demonstration was useful but the drying time felt rushed. That answer gives your delivery team something to improve. It also stops the marketing team treating every response as a ready-made endorsement.

Keep general feedback and permission to publish as separate decisions. A guest should be able to tell you something privately without finding their words on a sales page. Explain the purpose of the request and how you will follow up if you want to quote them. Don't bury a broad promotional release inside a form that appears to be about customer service.

If you already have an appropriate post-event feedback process, use it rather than creating another survey just to collect nice sentences. Our guide to attendee-created event content covers the wider collection and reuse process. Here, the additional job is to check the exact excerpt and the booking question it will help answer.

When you request feedback by email, use an appropriate audience and respect the rules that apply to the message. Loopyah's attendee email tools let you select audiences using purchase information, so you can start with people connected to the relevant event. You still need to decide whether your request is appropriate and obtain permission before publishing their response. Sending an email doesn't grant permission to use the reply in promotion.

Avoid writing a glowing statement and asking the attendee to approve it as though they had written it. If someone gives you a few factual notes, you can ask them to explain in their own words. If you need to prepare an edited version, show them the original context and the proposed excerpt together. Their approval should concern an accurate account, not agreement with a sentence you wish customers would say.

Leave staff out of the first selection where you have suitable independent attendee feedback. A team member may have genuinely enjoyed the programme, but readers should understand their relationship to the event. Likewise, a speaker's praise is a speaker's perspective, not evidence from an ordinary ticket buyer. Label it accurately if you have a reason to use it.

Don't create urgency around answering. The person has already paid to attend your event. They don't owe you promotional material. A clear request, an easy way to respond, and acceptance of a refusal will leave you with a process you can keep using without making guests uncomfortable.

Get permission for the exact excerpt and attribution

Finding a public post isn't the end of the permission check. Before reusing a comment on your sales page, contact the author, confirm the words you want to use, and explain where they will appear. Check any platform terms or other rights involved in copying the material. A private email, a survey response, and a public review can each need different handling.

The ASA's UK testimonials and endorsements guidance, which covers advertising such as websites and social posts, addresses permission, evidence of authenticity, and relevance to the advertised product. It notes exceptions for some accurate quotations from published sources. Our recommended workflow for routine attendee quotes is to ask the person, keep the answer, and publish only the agreed version.

Make that request concrete. Tell them which event page will use the quote, which future edition it promotes, the proposed credit, and how long you expect to use it. Ask separately about a photograph if you want one. Permission to publish words should not be treated as permission to copy their profile photo or display their employer's logo.

Here is a permission-request template to adapt, rather than a complete legal agreement: "Thanks for your feedback about [event and date]. May we publish this excerpt on the ticket page for [next edition], until [end date]? The excerpt is [exact words]. We'd credit it as [agreed name and relevant attendee description]. We won't add your photo or use this permission for paid advertising. Please reply to confirm whether you're happy with that version, and contact [address] if you'd like to discuss its use."

Keep the placeholders until you fill them with the actual details. If you want use across email, social posts, or advertising, ask for those uses explicitly instead. For a recurring campaign or a more complicated arrangement, get an appropriate agreement prepared for your market. The point of the template is to make the proposed use understandable, not to settle every rights or privacy question.

Ask how the person wants to be credited. A first name and an accurate attendee description may be enough for the page. A full job title can help establish relevance for a professional event, but only if the person agrees and the title is correct. Naming an employer can imply the company endorses you. Don't add a company name or logo merely to make the quote look more impressive.

Keep the contributor's contact details and original message in a restricted record, separate from the published credit. The buyer doesn't need to see someone's email address or booking reference. Whoever checks the quote internally should be able to find the evidence without giving the whole marketing team unnecessary access to attendee information.

If permission hasn't arrived, leave the space empty or use your own accurate explanation. Silence isn't approval. An assistant saying "they probably won't mind" isn't approval either. You can launch a useful ticket page without a testimonial; you can't responsibly fill that gap by guessing what another person has agreed to.

Edit for length without improving what the person claimed

The original comment might be too long for the page. That's normal. Look for a complete part that answers the booking question and still means what the person meant. Keep the original beside the proposed excerpt while you edit, then ask the contributor to approve the final wording.

Consider this fictional feedback, written only to illustrate the editing decision: "I hadn't tried printmaking before. The first demonstration helped me understand the steps, and the tutor checked my first attempt. I would have liked longer to finish the second print." These are invented teaching examples, not words you can attribute to a real attendee or publish as genuine proof.

The beginning could support a narrow point about how an inexperienced guest understood the introduction. It could not honestly become "Every beginner finishes two prints with individual tuition." That new sentence changes one person's experience into a universal outcome, adds a completion promise, and ignores the time concern. Getting the person to like your rewritten sentence wouldn't make the event promise accurate.

Even an exact excerpt can mislead through its surroundings. If you use the positive opening beside a claim that everyone leaves with several finished prints, the whole presentation suggests more than the original supports. You might use a relevant excerpt about the demonstration in a clearly described teaching section, but first investigate the pacing complaint and make sure the next programme is described honestly.

Here's how that could look in our fictional example after those checks and the contributor's approval. Your own page copy explains: "The tutor demonstrates each stage before you practise. No previous printmaking experience is required. Materials for the guided exercise are included." Under that explanation, the approved excerpt reads: "I hadn't tried printmaking before. The first demonstration helped me understand the steps, and the tutor checked my first attempt." The credit identifies the contributor as a previous-edition attendee using the name they've agreed to publish.

That combination has a useful job. The organizer states what the next session includes, and the attendee describes how they experienced the teaching at the earlier edition. The page makes no promise about completing a second print, and the team still has to address the pacing feedback. All wording in this example is invented to explain the process. Your page needs the actual programme details and a real person's approved words.

Sometimes the right choice is to use a different comment. You don't need to turn every mixed response into promotional copy. A guest can have given you valuable feedback without providing a suitable testimonial. Let the delivery team work on the issue instead of asking the editor to remove the awkward part.

Be careful with small changes in certainty. "I felt more confident" isn't the same as "You will become confident." "The tutor helped me" isn't the same as "Personal coaching included." Removing a word like "mostly" or "for me" can change the meaning even though the sentence becomes shorter. Read for that change, rather than counting how few words you altered.

Don't combine sentences from different people into one quote. Don't join separate comments from different editions so that they appear to describe a single visit. If you want to summarise recurring feedback in your own words, make it clear that you're writing a summary and keep evidence for the claim. It still needs to be accurate and shouldn't imply a representative survey you never ran.

For a translated comment, retain the original, have the translation checked, and explain to the contributor what you plan to publish. Keep the tone and qualifications. If you can't check a translation properly, choose material you can verify. An elegant sentence is not worth publishing if you don't know whether it still says what the attendee meant.

Disclose incentives and relationships where readers can see them

A complimentary ticket doesn't necessarily make someone's account useless. It changes the context in which a reader should judge it. The person may have received an invitation, worked with a sponsor, or agreed to create content. Establish that relationship before presenting their words as independent attendee feedback.

Make the explanation understandable beside the quote. "Invited guest; ticket provided by the organizer" tells the buyer more than an unexplained label or a link hidden at the bottom of the page. If the person is an employee, say so. If they were paid to contribute, explain the arrangement clearly enough for the reader to understand it.

Record why the person received complimentary access and whether you offered any benefit in exchange for feedback. The right disclosure depends on the actual arrangement and the market. Don't assume that one short phrase covers every situation. Ask the person who checks your advertising claims to review unfamiliar arrangements before using them across a campaign.

For US consumer reviews, the FTC's consumer reviews and testimonials rule FAQ explains that incentives cannot expressly or implicitly depend on positive or negative sentiment. It also distinguishes featured testimonials from merely hosting reviews. A sales-page quote you've selected for promotion deserves that extra attention; it isn't simply an untouched comment sitting in a public review feed.

The practical choice for a small event team is usually to ask for honest feedback without a reward tied to what people say. If you decide to offer an incentive, check the applicable law and the review platform's rules first. Disclose it where required and don't assume disclosure makes every incentive arrangement acceptable.

Suppose you offer a future ticket discount only to guests who describe the workshop as excellent. That request is steering the content before the person answers. Changing the wording to "tell us how much you loved it" doesn't remove that pressure. Ask what the experience was like, accept criticism, and keep any benefit independent of the response's sentiment where the rules permit the arrangement.

Avoid choosing a partner's glowing quote solely because their logo makes the page look established. A partner may know your team well while knowing very little about attending as a paying guest. Their comment can support a clearly identified partnership or professional observation. It should not quietly substitute for a ticket buyer's experience.

Keep the disclosure with the quote through every revision. If a designer shortens the credit to fit a small card, the relationship mustn't disappear. Review the final mobile version, because a disclosure that's obvious on a desktop can become separated from the words it explains when the page rearranges.

Place each testimonial beside the decision it helps

Once the words are approved, decide where the buyer needs them. Resist creating a large testimonial section simply because your website template has one. That section might be useful, but it can also separate the evidence from the question it answers. Start with the current offer and place the comment where its meaning is clear.

For the fictional workshop, explain the level and what the tutor demonstrates, then add the approved beginner comment. Keep the actual requirements visible: what attendees need to bring, what prior knowledge is expected, and what help is available. The comment supports that description. It shouldn't be the only place the buyer learns whether they can attend.

For a ticket upgrade, put relevant experience beside the upgrade's actual inclusions. If a guest attended a small-group discussion available only with a premium pass, identify that pass and the edition. Don't put the quote under every ticket option. Someone comparing passes should be able to tell which experience they would need to buy.

At the top of the page, establish what the event is, when and where it happens, and why someone might want to attend. You can include a short relevant testimonial there if it helps, but don't let a row of endorsements push the basic offer and ticket route out of view. A person ready to book shouldn't have to read your entire review collection first.

Further down, use specific comments near the programme explanations they support. A conference attendee's account of a useful discussion belongs near the explanation of how those discussions work. Praise for last year's headline speaker needs clear context, especially if that speaker isn't returning. Keep the next event's confirmed programme more prominent than a memory of the previous one.

Near ticket selection, answer the remaining practical questions directly. State inclusions, restrictions, and current prices through the supported ticket setup. Loopyah's ticket-selling tools show ticket types with their current prices and sold-out status. Make sure your surrounding copy and testimonials describe the option the buyer is actually selecting. A quote cannot correct a mismatch between a pass description and checkout.

There is no useful universal number of testimonials. Start with a small selection that answers distinct doubts, then remove any comment that repeats an earlier point. If you have several relevant experiences to show, group them so the reader understands the difference. More praise is not automatically more information.

Finish by following the page through to a completed purchase using your supported testing process. Check that the event, date, ticket type, quantity, and price stay clear. The reader should move from understanding the experience to choosing a ticket without having to reinterpret which edition the endorsements describe.

Keep the words readable on a phone

An approved quote can lose much of its usefulness when it's turned into a tiny screenshot. Readers may need to zoom, the credit may be unreadable, and the image can include usernames or private details you didn't mean to publish. For an ordinary text testimonial, use readable page text with the agreed attribution close by.

This also makes revisions more manageable. If the contributor asks you to correct their name, you can change the credit without remaking a graphic. You can check the words against the approved excerpt, and people using assistive technology have a clearer route to the content. A decorative quote image should never be your only way of presenting essential information.

Keep the context visible when the layout narrows. The event date, ticket type, and any relationship disclosure need to stay attached to the comment. Don't allow a mobile layout to leave a quote near one pass while placing its credit under another. Read the page in order, rather than only checking whether each separate card looks tidy.

I would usually start with static quotes. A rotating slider adds controls and movement to something that needs time to be read. W3C's carousel accessibility tutorial explains requirements such as pausing movement, keyboard operation, and communicating changes to screen reader users. If you choose a carousel, have those behaviours checked rather than assuming the template handles them.

If a video testimonial adds something the text can't convey, let the person choose whether to play it and provide accurate captions. Keep a readable version of the useful comment and its context available. Ask whether the extra filming, editing, permission, and page weight help a real buying decision. A spoken version of "great event" may take more work while answering no additional question.

Review the published preview on a real phone. Can you read the words without zooming? Can you see whose experience this was and which edition it concerns? Does the ticket route remain easy to find? Ask someone who wasn't involved in the page to explain what the testimonial made them expect. Their interpretation may reveal a promise your team didn't realise it was making.

Keep selected testimonials separate from review ratings

A few chosen comments are a selection of attendee experiences. They are not an average satisfaction score, an independent review service, or proof that everyone had the same experience. Present them in a way that makes the selection clear, such as a heading that identifies them as comments from previous attendees.

Don't add decorative stars to a quote just because stars look familiar on sales pages. If the person never supplied a rating, you've created a new piece of information. If you display an actual rating, retain its source, date, event coverage, and the number of responses behind it. Check that you have permission and a supported way to use any third-party rating display.

Australia's ACCC guidance on online reviews discusses misleading reviews, undisclosed relationships, and review manipulation. It also says businesses should display the number of reviews behind a star rating. For an event page, the important distinction is between a selected quote and a summary that claims to describe a wider set of responses.

Here's a fictional example of why that matters. You receive forty workshop survey responses. Six people give you permission to publish a positive comment. That gives you six possible testimonials to assess. It does not establish that all forty people were satisfied, or that the six comments are representative of everyone who attended. Permission to publish and satisfaction are different things.

If you ask a consistent rating question and want to publish its result, work from the complete relevant responses and explain what you measured. Don't calculate an event score using only the people whose words you liked or whose publication permission arrived first. Keep non-responses separate from negative responses as well. Someone declining to be quoted hasn't necessarily disliked the event.

Selecting testimonials doesn't require placing every survey answer on your ticket page. It does require avoiding a misleading picture of the experience. If you operate a public review feed, apply a clear moderation policy rather than removing genuine criticism because it makes the page less flattering. Your selected marketing quotes and that review feed need their own honest descriptions.

Pay attention when several people report the same delivery problem. A page full of praise for the tutor won't solve a recurring complaint that there wasn't enough equipment. Investigate the issue, decide what changes, and describe the next edition accurately. If you cannot deliver the experience a quote suggests, don't use the quote to sell around the problem.

What if the next event is new or has changed?

You can sell a new event without pretending it has previous attendees. Show the confirmed programme, the people delivering it, the format, and what the ticket includes. Explain why those choices suit the audience. A clear demonstration or programme preview may answer a buyer's question better than a testimonial from a loosely related project.

If you have feedback about the tutor's previous work, identify that work accurately. A comment about a separate class can support a carefully described point about the tutor, provided you have permission and the context is clear. It cannot become an attendee review of this new workshop. The same applies to a performer moving into a different event format.

Don't ask friends to fill the page with reviews before the event happens. They may be able to describe their professional experience of working with you, but they cannot honestly describe attending something that hasn't taken place. A person who helped plan the event also has a relationship the reader should understand.

For an established series, review the differences between editions before reusing the archive. Has the venue changed? Is the programme shorter? Has a hands-on session become a demonstration? Does the new ticket include the same access? Mark which comments remain relevant, which need clearer context, and which no longer belong on the page.

The workshop's beginner-teaching comment might remain useful if the teaching approach is unchanged and the edition is identified. A comment about generous practice time becomes questionable if you've shortened the practical session. You need to examine the detail the quote supports, not simply decide that the event name is the same.

If the previous edition disappointed people, start with the documented changes. Tell buyers what you've fixed and what you can now deliver. Don't imply that an old quote proves the new arrangements work. You might have evidence that the changes are in place, but the next audience hasn't experienced them yet.

Make the archive review part of preparing a new sales page. A quote approved for one edition may need fresh permission for the next use, depending on what you agreed. Even where permission continues, accuracy needs another check. Someone's words don't stay relevant just because your team has the file saved.

Keep a short record that the next editor can understand

You shouldn't have to search an old team chat every time someone asks whether a quote is approved. Keep one record with the original feedback, the context, the permission, and the published wording. Link it to the page or campaign using it, and make one person responsible for checking changes.

For a small team, this can be a restricted table or content record in the system you already use. You don't need another elaborate approval process. You need enough information to stop a colleague copying an old quote into a new ticket offer without noticing that the permission or context has changed.

Use these fields as a starting point:

• Original comment and a private reference to where it came from.

• Event name, edition date, session, and ticket type experienced.

• Contributor contact and agreed public attribution.

• Any complimentary access, payment, employment, or other relevant relationship.

• Exact approved excerpt and the contributor's confirmation.

• Agreed uses, duration, and any editing or photo permissions.

• Current page placement, owner, and next review point.

Keep private records private. A designer needs the approved words, attribution, context, and disclosure. They may not need the contributor's contact or booking details. Share the information required for the task and use your existing privacy and retention arrangements for the underlying evidence.

Give the quote a clear working status. "Awaiting permission" means it cannot be published. "Approved for this edition's ticket page" means exactly that. "Needs review after venue change" warns the next editor what has to be checked. A vague label like "good content" tells a busy colleague almost nothing.

When someone requests a correction or raises a concern about use, record the request and check every location where you've published the material. Resolve it under the agreement and applicable rules, and stop new uses while you investigate if the permission or accuracy is in doubt. Don't make promises about removing third-party copies that you don't control.

Before handing the page over, compare the final words with the approved excerpt once more. Check the credit, edition, pass, and disclosure in the actual layout. This last read is worth doing after design: a shortened caption or moved block can change what the buyer thinks the quote is about even when the quote itself hasn't changed.

Check usefulness without claiming every sale came from the quote

Start with the question you wanted the testimonial to answer. Ask a few people unfamiliar with the page what they think the event involves and whether they understand who it suits. This isn't a conversion study, but it can reveal that the quote creates confusion or that a practical detail is still missing.

Then look at the enquiries and complaints associated with that issue. If beginners still ask whether they need drawing experience, your explanation may be unclear or hard to find. A fall in enquiries can be encouraging, but traffic volume, audience mix, and other changes also affect it. Don't treat fewer messages as proof that the testimonial increased sales.

If you have sufficient eligible traffic, reliable purchase tracking, and time before the event, you can test a specific placement or selection. Our guide to A/B testing an event ticket page explains how to compare versions properly. Keep the offer comparable, use simultaneous random assignment, and judge completed purchases rather than clicks on the quote.

For a fictional illustration, suppose each version receives one thousand eligible assigned visitors. On the original page, forty visitors buy; on the page with the testimonial, forty-five buy. The observed purchase rates are four percent and four and a half percent. That half-percentage-point difference is an observation, not enough by itself to declare a reliable improvement.

You still need to consider the test design, ordinary variation, purchase window, and whether enough evidence has accumulated for the decision. If your event cannot support a useful test, say that. You can still improve inaccurate or confusing copy without claiming a measured sales lift. Don't keep a misleading quote in place simply to preserve an experiment.

Remember the cost of producing the material. Gathering permission, checking the excerpt, and publishing readable text may be quite manageable. Commissioning videos, custom animations, and a complicated review display adds work that the ticket business has to pay for. Choose the simplest presentation that answers the buying question well, then expand only for a clear reason.

For your next sales page, begin with one hesitation you can actually address. Fix the factual explanation, choose a relevant genuine comment, and confirm its exact use with the contributor. When you read the finished page on your phone, you should be able to explain what that person's experience helps a new buyer understand, and which current ticket offers that experience.