Keep Your Tickets With the Fans Who Want Them

Spread a Sell-Out Release Across More Fans

A release you expect to sell out fast reaches more people when no single basket can take a big share of it. Set the most tickets one order can hold, and the most one customer account can buy across all its orders, for the whole event or for one ticket type. A buyer who comes back for a second and third order still stops at your limit, so a tout needs a new account and a new card for every few tickets, and buying a block to resell stops being worth the trouble.

Give VIP a tighter limit than general admission, or sell a table ticket that must be bought in multiples of two. Ticket Fairy counts the active tickets of that type on the customer account when a signed-in buyer adds tickets and again at checkout, and cancelled or refunded tickets do not count against them.

When a partner sells part of your event, turn on This ticket type is being sold on a different platform and enter the address in External Platform Link. Your event page shows a button for that ticket type that opens the partner's page, beside the tickets you sell yourself.

• Per order: the most tickets one basket can hold
• Per account: the most one customer can buy across every order
• A limit for each ticket type: tighter on VIP, looser on general admission

• Limit who can buy a ticket type
• Raise Your Price as Each Release Sells Out, and Open Your On-Sale on Time

Decide Who Gets a Ticket Before It Is Issued

A membership tier, an industry night, a student rate or a curated party admits people on your decision. Turn on order approval, and buyers place a request at checkout instead of receiving a ticket straight away. Ask for approval on every order for the event, or only on the ticket types that need a decision, and buyers of your other ticket types check out as normal.

An order that includes one ticket needing approval waits for you as a whole, and approving it issues every ticket in it. Buyers can still find your event and place a request, so order approval suits an event where anybody may ask. Use a password, personal invitations or an access code when only invited guests should reach checkout at all.

• The whole event: every order waits for your decision
• Chosen ticket types: approval only where you need it

• Approve orders before buyers receive tickets

Charge the Buyer Only When You Say Yes

Turn on Hold payment until approved, and checkout reserves the amount on the buyer's card and takes it when you approve. If you decline, the hold is released and the buyer pays nothing. The Needs Approval tab in your event's Orders lists every request with the buyer, the tickets, the total and when the payment hold expires, so you can see which requests to decide on first.

Approve an order and the buyer is charged and gets their tickets. Decline it, and the buyer hears your decision straight away, with the hold released or a payment taken at checkout refunded, so a buyer you turn away is never left out of pocket. Each decision shows you the order number to confirm, on a desktop or a phone. Leave the hold off when you would rather take every payment at checkout and refund the buyers you decline.

• Hold payment until approved: the amount is reserved, not taken
• Needs Approval: every request with its Hold expires time
• Approve or Decline: confirmed with the order number

• Answer Every Buyer Quickly and Keep Your Tickets With Real Fans

Ask Buyers to Prove Who They Are on High-Demand Nights

Ask for an ID check on the whole event or on the ticket types under most pressure. Buyers finish checkout as normal, then photograph their ID and take a matching selfie on their phone. Their card is held, not charged, until they pass, so a bulk buyer with no identity behind each order never gets the tickets.

Every order still waiting appears on the Needs Verification tab of Orders. Send a buyer the check again when they closed the page before finishing it. Take the payment without the check when you have satisfied yourself another way, and the buyer gets their tickets. Release a hold that is going nowhere, and the tickets go back on sale. Taking a payment and releasing a hold each ask you to confirm first.

• ID and selfie check: the buyer proves who they are on their phone
• Card held, not charged: until the buyer passes
• Resend verification: a fresh link for a buyer who closed the page

• Clear the ticket orders waiting on an ID check

Put a Name on Every Ticket and Check It at the Door

Turn on Names required, and every attendee gives their name when the tickets are bought. Turn on Name checks, and your door team checks those names at entry. Turn on ID required, and attendees show ID at the door as well as their ticket. A ticket bought to resell then carries a name the tout does not share.

• Names required: a name for every attendee
• Name checks: names checked at entry
• ID required: attendees show ID at the door

• How do you keep touts and bots off your tickets?
• Get Your Crowd Through the Door Quickly, With Nobody Getting In Twice

Send Returned Tickets to Fans at Face Value

With Ticket resale on, a buyer who cannot come passes their ticket back through Ticket Fairy, and it goes out again at the price you set. With the waiting list on, the next fan waiting for that ticket type is offered it first. A fan who knows they can get a ticket at the original price has no reason to buy from a resale site, and the old ticket's code stops working at the door once the new holder has theirs.

The Waiting List tab on Performance shows who is waiting for each ticket type once it sells out, which tells you how much demand you did not serve and who to offer the next release to. Add-on resale works the same way for parking, camping and other extras.

• Ticket resale: returns go out again at your price
• Waiting list: returned tickets offered to fans in order
• Old codes refused: only the new holder gets in

• Let buyers resell their tickets at face value
• Run a waiting list for a sold-out event
• Get Every Spare Ticket to a Fan Who Wants to Come

Keep Your On-Sale Where Only Fans Reach It

Run your highest-demand on-sale by invitation, by presale code or behind a password, so your tickets never sit on a public page for a bot to find. When the public sale opens, a waiting room in front of checkout shows each buyer their place and lets them in turn, so the buyers already paying finish quickly and refreshing the page gains nobody an advantage.

Split your tickets into releases with their own on-sale times, and two smaller rushes replace one big one, with a reason for fans who missed the first release to come back. Pre-registration and invitations move your most likely buyers ahead of the public crowd.

• Invitation, code or password: tickets only your fans can reach
• Waiting room: buyers move into checkout in turn
• Releases: demand spread across on-sale times

• Sell Tickets to Exactly the People You Choose
• How do you keep a high-demand on-sale running smoothly?

Set Your Protections by Asking Fai

Tell Fai, the assistant inside your dashboard, the limit you want on a ticket type, and she sets the per-order limit, the per-account limit or the external sales address. She can turn on order approval for the event or the ticket types you name, change the anti-scalping settings and switch the waiting list on, and she shows you each change and saves it only once you approve.

Ask Fai to open a pending order, and she shows you the buyer, the tickets, the total and the payment hold, then approves or declines it once you choose. Approving can take the held payment and declining emails the buyer, so she asks you again before either one.

• Limits in a sentence: per order, per account or an external link
• Pending orders: approved or declined once you choose
• You approve each change: nothing is saved until you say so

• Get Your Ticketing Work Done by Asking Fai