How to use TicketSquad for your next event

If your squad is aiming for a big festival or arena sale, start by typing the event name before you build anything from scratch. When TicketSquad recognises the event, we can preload the stuff organisers normally end up hunting for in old chats: dates, venue, official-route notes, per-buyer limit and checkout fields.

That is the easy version: pick the match, sense-check it, create the event. For Glastonbury, Reading, Boomtown, Download and other big ones we already understand, you should not have to rebuild the basic sale setup from memory.

If the event is not in TicketSquad yet, no drama. Create a custom event, add the official ticket route, sale date and per-buyer limit you know today, then keep anything uncertain clearly marked until the official route confirms it.

Most groups already have the lively bit sorted: a WhatsApp thread, a Messenger chat, a Discord channel, a spreadsheet tab with everyone half-filling rows. Leave that where it is. TicketSquad gives the admin its own proper home.

Create the event, copy the TicketSquad invite link, paste it into the chat and tell people to tap Sign up, then Join the event. From there, members add or check their own details instead of making the organiser copy names, phone numbers, registration numbers and ticket choices by hand.

Now the organiser can see who has joined, who is missing fields, who needs a nudge, and who is actually ready for the official sale.

TicketSquad gives you the required checkout fields first, but the best organiser systems usually track more than ticket data. Maybe your group needs arrival-day choices, who has the camping stove, who has space in the car, who wants the Thursday coach, or who needs reminding that "Bristol" and "Birmingham" are not interchangeable airports.

Add those as custom fields so people answer once and everyone sees the plan. You can use single-choice fields for quick polls, text fields for notes, URL fields for links, and optional fields for useful-but-not-critical details.

For music festivals, keep the fun part visible too. If TicketSquad has a Clashfinder link for a known event, it can appear with the lineup information. You can also ask members for their Clashfinder username or a link to their personal clash plan so the squad can see who wants to be where.

Once people have joined and the important fields are complete, split the squad into buyer-ready Groups. If the seller lets one buyer buy six tickets, Groups of six make sense. If the limit is four, build around four.

Drag and drop members into buying groups, then check the gaps before the queue opens. Each helper can see who they are trying for, which details are ready, and what still needs attention without decoding the spreadsheet tab only you understand.

When someone gets through, they should not vanish into the group chat with a half-message like "I think I got some". Report the outcome in TicketSquad so everyone can see who is sorted, who still needs help, and which buyers should keep trying. Celebration can wait ninety seconds; the victory voice note will still be there.

TicketSquad does not improve queue position or guarantee a ticket. It reduces the avoidable chaos around the official route: missed details, duplicate attempts, unclear Groups and nobody knowing what happened after the first checkout.