Docs

Starting a squad

Start a squad for a known event with the details prefilled, or for a custom one - and make the two choices that shape everything else.

Tap Start a squad and say which event it's for. It takes a minute if we already know the event, and not much longer if we don't. If you're not in a squad yet, your welcome page and dashboard also suggest events with tickets going on sale soon, each one already filled in.

Start from a known event, or from scratch

Start typing the event's name and TicketSquad searches its catalogue of known events. Pick a match and the event arrives pre-filled with what the catalogue has confirmed: official event and sale dates, venue, timezone, the seller's per-transaction ticket limit, recommended data fields, and the right ticket mode from checked ticket rules. Where we don't have a confirmed limit, it defaults to a sensible 4 with a warning to check the ticket site. Dates, fields, limits and modes are all overrideable; the venue travels with the catalogue link itself. Because the catalogue has filled them in, the smaller settings for a known event sit under More options, and open by themselves if one needs a look.

Not in the list? Keep typing - a custom event gives you full control over every detail. There's also a Request that we add it button, which sends the event to our curation queue while you carry on creating.

Linking to a known event is also how your event gets the in-app Guide tab and, once editions pass, the reviews surface.

The two choices that shape everything

Tickets - are they named to a person, or transferable? This decides which sale-day machinery your event runs (see the overall process). For known events we pre-select the answer from checked ticket rules - with the reason shown - and warn you if your choice contradicts what we know about the seller. You can change the mode later, until ticket evidence locks it (someone recording a ticket, or a group outcome being reported), or until you turn on sale plans, which keeps named tickets for good.

Privacy - Open or Closed. Open is the default: everyone in the event can see everyone's details, perfect for a group of mates. Closed keeps personal details inside each buying group - the right call when the invite list is bigger than your trust circle. Covered in depth in Privacy; you can change it later in settings.

The smaller dials

  • Per-buyer ticket limit - how many tickets one person can buy per transaction; set from catalogue data when known. This drives sensible buying-group sizes.
  • Community - if you run a community, attach the event so its members can see it and join without an invite link.
  • Dates and timezone - known events bring official dates; custom events take a single date, a range, several labelled dates, or an honest TBC until the announcement lands.
  • Sale plans - not a choice you make here. If your named-ticket event turns out to have more than one sale, you turn them on later from settings. See Sale plans.

The free plan

The free tier (Squad Solo) includes one squad you create. It counts as used once someone else joins it; until then you can delete it and start again. Joining other people's squads, helping coordinate them, or being handed one is never limited. To create more, upgrade to Squad Crew.

After creating

You land on the event page with a fresh invite link ready to share - one link, the same for everyone, regenerable at any time from settings if it ever leaks. Then the flow follows the overall process: people join, details get collected, and the sale-day machinery for your ticket mode takes over.