How to run a ticket presale for different audience groups

So you're getting ready to put tickets on sale. Last year's buyers expect first access, your mailing list has been waiting for the announcement, and a partner wants an offer for its members. You can invite all of them early, but you need to decide what each invitation actually promises before you send it.

A useful event presale strategy gives each group a clear reason to buy early, a defined access window and an honest explanation of ticket availability. Start with the audience rules, reserve only the inventory you intend to protect, and decide what happens to unsold tickets before the public sale opens. The invitations should describe those decisions in words a buyer can understand without asking your team.

The tricky part is that these audiences overlap. A returning buyer might also be a subscriber and a partner member. If you treat every list as a different collection of people, you can send conflicting messages, promise the same tickets several times and mistake repeat contact for fresh demand. Let's work through a presale that keeps those details under control while giving the people you want to bring back a worthwhile opportunity.

Decide what early access is meant to achieve

The first thing you want to do is choose the job of the presale. You might want to recognise repeat buyers, fulfil a membership benefit or give a partner time to organise a group. Those are different reasons, and they lead to different choices about who qualifies and how long the offer needs to remain available.

For repeat buyers, the benefit might be a chance to choose tickets before a wider announcement. For a partner, it might be a reserved allocation that members can buy during an agreed window. Someone arranging a group booking may need enough time to collect commitments from other people. A few hours of access could be useful for one audience and almost impossible for another.

Keep earlier access separate from lower pricing. A presale can sell at the same price as the public launch. If the event has scarce seats, an appealing programme or a history of selling out, the opportunity to book first may be the relevant benefit. You don't need to invent a discount just to make the word presale seem justified.

If you do offer a lower price, calculate what the event can afford before setting the allocation. Our guide to early-bird ticket pricing and allocation decisions explains how to calculate an allocation against your revenue needs. This article concentrates on who gets access, what inventory they can buy and how you move between audiences without confusing people.

Write one sentence for your own team about the purpose. For example, you could decide that returning buyers receive an earlier opportunity to purchase the next edition, while a community partner receives a small reserved allocation for its members. If you can't explain the distinction plainly, simplify the plan before trying to describe it in several emails.

Define who qualifies before creating the lists

An audience name is useful only when it has a rule behind it. Returning buyers could mean anyone who bought last year, anyone who attended two editions, or the people who bought a particular ticket type. Pick the definition that matches the promise you want to make. Then check that your records can identify those people accurately.

If your invitation says last year's ticket buyers, don't silently include people who only joined a waitlist. If it says previous attendees, remember that the purchaser and the guest may be different people. Someone who bought four tickets can be one buyer in your records while representing several attendees. Don't claim you have identified all previous guests unless you actually have their relevant records.

For a subscriber presale, set a signup cutoff. Someone joining after the invitations leave needs to know whether they still qualify, whether another message will follow and when they can buy. You can accept new subscribers during the window if that suits the offer, but make it a deliberate rule. Otherwise your support team ends up deciding eligibility one inbox conversation at a time.

Membership and partner audiences need their own checks. Agree whether membership must be active on the invitation date, the purchase date or the event date. Ask the partner how it will confirm eligibility and handle people who join after the cutoff. A forwarded email proves that someone received a message; it doesn't prove that they belong to the intended group.

You also need to decide whether eligibility belongs to the purchaser or every attendee. A member allowed to buy tickets for friends needs different wording from an offer limited to member attendees. The second arrangement requires a way to confirm each person's status, which may create more work than the benefit justifies. Be honest about what you can check consistently.

Collect only the information needed for that check. The UK's Information Commissioner's Office describes data minimisation as holding personal data that is adequate, relevant and limited to the purpose. A presale shouldn't become an excuse to request unrelated personal details. Agree a proportionate verification process and explain what you need before someone reaches checkout.

Separate the right to buy from the right to receive marketing

Qualifying for a presale and being contactable by marketing email are separate questions. A past purchase can establish that someone meets your audience rule without giving you unrestricted permission to promote every future event to them. Check the sending rules for the places where you operate and where your recipients are before treating an old attendee export as a launch list.

In the UK, the ICO's electronic mail marketing guidance describes consent and limited exceptions. Its products and services exception has conditions, including collecting details during a sale or sales discussion and offering an opt out when collecting them and in subsequent messages. A previous purchase alone doesn't establish that you meet those conditions. Check the current guidance against your collection and sending process.

For US commercial email, the Federal Trade Commission's CAN-SPAM compliance guide covers accurate sender information, truthful subject lines, a postal address and a working opt out, among other requirements. These are US rules, rather than a universal permission standard. Your audience plan should use the requirements applicable to the recipients and the business sending the invitation.

Keep the presale invitation separate from operational messages about an existing purchase. A date change for a ticket someone already owns has a different purpose from an offer for a new edition. Our event email marketing consent guide covers the practical distinction between buyer details, guest details and marketing choices at checkout.

With Loopyah's attendee email tools, buyer contacts include purchase information and whether they agreed to hear from you. You can create segments using what people bought, while opt outs and invalid addresses are removed from promotional sends. That helps you contact a relevant, reachable group. You still decide the presale eligibility rule, and purchase based email segmentation doesn't establish partner membership or enforce ticket access.

Choose whether groups share tickets or have reserved allocations

There are two straightforward ways to organise availability. Several audiences can buy from the same ticket inventory at different times, or you can protect a defined quantity for a particular group. Decide which arrangement you mean before using phrases such as exclusive access or reserved tickets. They describe different promises to the buyer.

Shared inventory is usually simpler when the benefit is earlier access. Returning buyers can start first, subscribers can join later, and both groups can continue buying until the public launch. But the later group may find fewer tickets available. If you want subscribers to have a protected opportunity, an invitation to the remaining shared inventory won't necessarily deliver it.

A reserved allocation can make sense when you have promised a partner a specific opportunity. You hold a quantity aside for its audience during the agreed period, then release whatever remains under a stated rule. The reservation protects availability for the group as a whole. Unless you have explicitly held tickets for individuals, it does not guarantee a ticket to everyone receiving an invitation.

Let's use a hypothetical event with 600 sellable general admission tickets. That total already excludes production holds and complimentary places. You choose to protect 120 tickets for returning buyers and 80 for a partner, while leaving 400 for the public launch. Those figures illustrate the mechanics; they are not recommended allocation sizes or evidence of demand.

You have now accounted for all 600 tickets. If a subscriber presale is added, it needs to use an agreed part of that inventory. You cannot create another 100 tickets simply because you have another mailing list. Either give subscribers access to an existing shared pool or change the original allocations while keeping the total within the sellable quantity.

For reserved seating, make the decision at the seat level too. A promise of early access to good seats needs a defined selection, especially when sightlines, price bands or accessible seating arrangements matter. Several ticket quantities can look reasonable in a spreadsheet while accidentally referring to the same seats. Check the actual available places before announcing what each group can choose.

Account for people who belong to several groups

Imagine that 60 returning buyers are also partner members. Those people qualify through both routes, but they aren't 60 extra potential customers. Keep audience membership separate from the count of unique people you can reach. Otherwise you can overestimate demand and send the same person several launch messages with different instructions.

One practical approach is to give overlapping buyers the earliest relevant invitation, then suppress repeated invitations that add nothing. Someone who has already purchased can receive their confirmation and useful event information without continuing to get reminders to buy the same ticket. If a later message offers a genuinely different ticket or opportunity, explain that difference rather than pretending they haven't bought.

Decide which purchase limit applies across the event. A limit per code, per order or per audience can allow someone with several routes to purchase more than you intended. If you want one overall buyer limit, confirm that the ticketing setup enforces it that way. Don't write an event wide promise while relying on separate controls that never check each other.

For our hypothetical event, suppose the returning buyer offer allows up to two tickets per eligible purchaser. A returning buyer who is also a partner member should know whether those two tickets use their complete allowance or whether the partner offer permits another purchase. Choose the policy before either group goes on sale, and make it consistent with what the system can enforce.

There's no universally correct answer about combining benefits. A membership may legitimately include a separate allocation, while an early access invitation may simply provide another route to the same tickets. What matters is that you know which arrangement you've offered. Support staff should be able to explain it from the agreed rules, rather than interpreting the wording after an order arrives.

Set access windows that your team can actually run

Your schedule needs opening times, closing times and a timezone. It also needs a clear rule about overlap. Does the returning buyer window close when subscribers gain access, or do returning buyers keep buying until the presale ends? Either can work, but buyers shouldn't have to infer the answer from the date of their invitation.

For an illustrative schedule, returning buyers could purchase on Monday from 10am, with their protected allocation closing Wednesday at 10am. The partner's separate allocation could open Tuesday at 10am and close Thursday at 10am. The public sale could begin Friday at 10am. Use the same named timezone throughout. These are planning examples, not timings proven to produce better sales.

That schedule has overlapping access without overlapping inventory. Returning buyers and partner members can buy at the same time from separate reserved quantities. If you instead give both groups access to one pool, say that availability is shared. The date schedule alone doesn't tell your team or the customer which tickets each person can purchase.

Leave enough time between a reserved window closing and public launch to reconcile sales and prepare the next availability. In the example, Thursday's partner close gives the team time before Friday's public sale. Your actual gap depends on the controls, reporting and staffing you use. Don't schedule several manual changes for a moment when nobody can verify the result.

Check the exact calendar date in every message. Next Tuesday can become confusing when an email is forwarded or read days later. If you serve buyers in several regions, identify the event's selling timezone and provide a reliable way to interpret the time locally. A scheduled email's timezone and the ticket access window's timezone should agree.

Decide how unused tickets return to sale

Unused reserved tickets need a destination and a deadline. In our hypothetical example, returning buyers purchase 90 of their 120 tickets and partner members purchase 50 of their 80. That leaves 30 unsold in each allocation. The event has sold 140 tickets, with 460 sellable tickets remaining. Nothing has been added to the event's original 600 ticket total.

If your agreed rule transfers all unused reserved inventory to the public sale, the original 400 public tickets become 460. Close or adjust the previous allocations as required before adding their unsold quantities to the public availability. Leaving the same 60 tickets available in both places would double count them, even if each individual ticket type looks correctly configured.

Reconcile completed sales rather than simply subtracting email clicks or abandoned orders. Check how your system treats tickets temporarily held during checkout, pending payments, cancellations and refunds. The people buying near the closing time deserve the published rule to apply consistently. You need to know when the inventory is genuinely available to release, not just when the marketing window has ended.

Tell partners what happens before launch. If their unused allocation moves into public sale on Friday, they need to remove or update any copy suggesting members still have reserved tickets. Agree who sends that correction and when. You can't prevent every forwarded old message, but you can make the current ticket page and the partner's current communication accurate.

A slower presale doesn't automatically justify keeping the reserve open indefinitely. If holding those tickets prevents public buyers from purchasing, you're making a commercial tradeoff. Review the evidence and your promises before changing the plan. An extension might help a partner finish group bookings, but it should have a clear reason and an updated inventory calculation.

Write invitations that explain the offer completely

Start with why this person qualifies and what they can buy. Then give the access period, availability rule, purchase limit and price information. Link to the correct buying page. The buyer should understand the offer before opening checkout, including any conditions that would make their purchase ineligible. Keep essential terms in the invitation rather than hiding them in a separate document.

For our example, the returning buyer message could say that people who bought the previous edition can purchase up to two general admission tickets from Monday at 10am until Wednesday at 10am in the stated timezone. Explain that 120 tickets are available for this group and purchases are first come, first served within that allocation. State the actual checkout price and what the ticket includes.

If the invitation is only early access to shared availability, use that wording instead. Don't say tickets are reserved for you unless you really have an individual reservation. An access code usually offers an opportunity to purchase, while a reservation suggests the ticket will remain available for a particular person. Buyers make different plans based on those promises.

The UK's Advertising Standards Authority advises advertisers to estimate demand reasonably and make availability limits clear. It also warns against falsely presenting an offer as available only for a limited time. For your presale, use the real quantity and deadline rules. A countdown that restarts or an exclusive offer promoted publicly can undermine the explanation you've given eligible buyers.

Include what happens if the allocation sells out before the closing time. Will people wait for public sale, join a notification list or choose a different ticket? If the public sale contains separately reserved inventory, explain that a sold out presale does not mean the whole event is sold out. Customers should know whether another genuine buying opportunity remains.

Give the reader one clear support route for access problems. Explain how to ask for help without posting personal details publicly. A buyer who can't use a code needs a useful answer while the offer is still available. Asking them to message several accounts only adds delay when the same support team eventually has to make the decision.

Make access controls match the promise

A private link, shared code and verified buyer list provide different levels of restriction. A link or code can be forwarded. That may be acceptable for a loose subscriber offer, especially if the aim is simply an early announcement. It is less suitable when you have promised an allocation strictly limited to active members.

Choose the lightest control that genuinely supports your rule. If forwarding would materially undermine the offer, you need a purchase process that checks the relevant eligibility. Confirm the available controls with the ticketing provider and test them. Avoid advertising strict enforcement until you know what happens when someone uses another person's link, changes their email address or attempts a second purchase.

Don't assume a promotional code protects ticket inventory or validates membership. A discount code may change price while leaving the tickets publicly visible. An audience email may reach eligible people while anyone with the buying link can purchase. These tools can support a presale, but each needs to perform the job you've assigned it.

With Loopyah ticketing, a ticket type can have several releases with their own prices and quantities, and the next release opens when the current one sells out. That is useful for planned quantity based selling. It doesn't establish that a release checks membership or opens and closes on your audience schedule. Verify the access controls you need before choosing this arrangement for a restricted presale.

Keep the customer experience accessible while you enforce the rules. The World Wide Web Consortium's form instruction guidance recommends explaining required input and formats clearly. Tell buyers where to enter their code, which email they should use and how to correct an error. An unexplained rejection creates a support problem even when the eligibility decision itself is correct.

Test the sale as different buyers

Before sending invitations, walk through the complete purchase experience using the scenarios your audience rules create. Test an eligible returning buyer, a partner member, someone in both groups and someone who does not qualify. Confirm which ticket each sees, when they can purchase, what happens at the quantity limit and whether the confirmation describes the ticket they intended to buy.

Also test the edge of each window. Someone arriving before the opening time should receive a clear explanation. Someone arriving after close should see the next relevant option, rather than a broken page or a vague error. Check that the ticket availability and email wording agree when a presale sells out early. The last buyer needs the same clarity as the first.

Review mobile checkout, the event date, the venue, prices and any eligibility instructions. Ask someone outside the campaign planning to read the invitation and explain what they think it offers. If they believe a ticket is guaranteed, a discount is included or their friends qualify when those things aren't true, fix the wording before launch.

Prepare support replies for missing invitations, forwarded codes, incorrect addresses and exhausted allocations. Give the support team the authority and information needed to make consistent decisions. If exceptions are permitted, record them against the inventory and buyer limit. An informal promise made in a direct message still affects what you can deliver to the other audiences.

Prepare for a failed opening or a changed event

A presale can fail at the moment it opens. A link might lead to the wrong event, an eligibility check might reject valid buyers or the expected tickets might not appear. Decide who can pause the invitations and who can correct ticket availability. Those decisions are much easier to make before everyone is watching the clock.

If a genuine access problem affects the offer, tell the relevant audience what happened and what you are doing. Give a specific next update time when you cannot yet confirm the fix. Avoid telling people to keep trying indefinitely, especially if repeated payment attempts might create uncertainty about whether they bought. Ask support to check the order record before advising another purchase.

A repair may require an adjusted window, but review the knock on effect first. Extending returning buyer access into the subscriber window could change which group gets first access to shared inventory. Extending a partner reserve past public launch could reduce what public buyers can purchase. Explain the revised arrangement to anyone whose opportunity changes, and update the buying page before restarting messages.

Treat a programme or venue change separately from a technical problem. If the offer materially changes after presale tickets have sold, check the obligations and policies that apply to those completed purchases. Your team needs a plan for communicating the change and handling buyer options. A presale's access deadline doesn't remove the responsibilities attached to tickets you've already sold.

Keep presale rules separate from admission rules

Once someone has bought an eligible ticket, they need to know whether anything else is required at the door. A presale restricted to purchasers with active membership can still sell ordinary admission tickets, if that's what you've agreed. A ticket that also requires membership at entry is a different offer. Explain that requirement before payment, including what happens if membership expires before the event.

Decide how companion tickets work too. If a member can purchase one ticket for themselves and one for a guest, say whether the guest must arrive with the member. If the tickets are independent after purchase, don't introduce a together arrival requirement later. Make the confirmation and door instructions reflect the same policy the invitation advertised.

Give door staff the relevant admission rule, rather than the entire marketing history. They need to know which ticket is valid, whether any additional eligibility check applies and how to handle a disputed case. They shouldn't have to decide whether someone deserved an invitation several weeks earlier. Resolve purchase eligibility when selling whenever the intended offer allows it.

Finally, agree how transfers and refunds affect the restriction. A ticket sold through member access might be transferable to another person, or the benefit might require the replacement holder to qualify. Check what the ticketing setup and published terms actually support. If a refund returns a ticket after the reserved window closes, allocate it under the current inventory rule rather than reopening an old offer by accident.

Review sales before opening the next audience

At each handover, check tickets sold, remaining availability, unresolved payment states and access problems. Compare the result with the purpose you set at the beginning. A returning buyer presale that brings previous customers back may be doing its job even if it doesn't sell the whole allocation. A partner reserve that remains mostly unused may need a smaller allocation next time.

Separate unique buyers from tickets and from invitation recipients. One buyer purchasing two tickets produces one buyer and two paid places. Someone included in several groups remains one person. Keep those counts distinct when reviewing response, and record which access route the completed sale used where your reporting supports it. Otherwise overlap can make one group look stronger than it actually was.

Treat the results as information about this offer under these conditions. A fast first window doesn't prove that the public allocation will sell at the same pace, and a weak response doesn't prove that returning buyers no longer care. The date, programme, timing, message delivery and access experience may all have affected the result. Investigate before changing several things together.

Before your next launch, write the rules on one page for the team running the sale. State who qualifies, which tickets each audience can buy, the exact access times, the overall purchase limit and where unused inventory goes. Keep that page available to anyone answering buyer questions during the launch. Then check the invitation and checkout against that plan. You can give different groups a worthwhile opportunity without leaving buyers or your own staff to work out what you meant.