A games shop can automate tournament sign-ups and pre-order lists with a free form that closes at a set number of entries, a spreadsheet as the master list, and an automation step that sends confirmations, waitlist offers and deposit reminders. AI writes and tidies the messages. People take the money and make the exceptions.
Generic "best automation tools" lists miss what a games shop actually does: a Friday-night event with eight seats, a booster-box release with forty pre-orders and twenty-five deposits, and a customer who wants to know on release morning whether his box is ready. The workflow below is built around those three moments. It does not touch prize pools or betting; the scope is sign-ups, lists and messages.
The three-sheet system behind everything
Automation fails when information lives in five places. Before you pick any tool, set up one spreadsheet with three tabs. Everything else reads from or writes to it.
- Events. One row per event: name, date, start time, format, seats, entry fee (if any), status (open, full, closed).
- Entries. One row per sign-up: timestamp, event, name, phone or email, consent to messages (yes or no), status (confirmed, waitlist, cancelled, no-show).
- Pre-orders. One row per customer per item: name, contact, product, quantity, deposit due, deposit paid (yes or no), release date, status (waiting, ready, collected).
This is deliberately plain. A shop that runs on a spreadsheet can move to a dedicated shop system later and export the same columns. A shop with no tidy list cannot automate anything, however clever the tool.
Step 1: a sign-up form that stops at the seat limit
Choose a form tool that can close itself at a set number of entries or on a set date. Tally's pricing page lists "close forms on limit or date" on its Free plan, with unlimited forms and submissions under fair use. Check the current page when you sign up. Other form tools may put the limit behind a paid plan or an add-on, so test it before you rely on it.
Build one form per event series, not per event. Ask only for what you will use:
- Name (or the name the venue uses for the player badge).
- Phone number or email for confirmations. If you ask for both, say which one you will use.
- Which event date, as a dropdown from the Events tab.
- Skill or experience band, if you run beginner and open nights separately.
- A tick box: "Text me about this event and about releases" with the shop's contact for opting out. No pre-ticked boxes.
Set the form to close at the seat limit. For eight seats, the ninth person sees a message pointing to the waitlist form, which is the same form with a different heading and a status column filled "waitlist" in your sheet. Connect the form to the spreadsheet so every submission lands as a new row in Entries. Most form tools do this natively; if yours does not, a Zapier step (new submission, add row) does it.
An illustrative filled-in event row
| Event | Date | Seats | Fee | Status |
|---|---|---|---|---|
| Friday card night, beginners | First Friday, 18:30 | 8 | 5.00 | Open |
| Saturday board-game afternoon | Second Saturday, 14:00 | 12 | 0 | Open |
| Release-weekend draft | Release Saturday, 11:00 | 16 | 15.00 | Open, waitlist on |
Step 2: confirmations and the waitlist, with AI writing the words
When a new row appears in Entries with status "confirmed", an automation sends a confirmation. When the form has closed and a later sign-up goes to the waitlist, it sends a waitlist note. Zapier is a common choice: its Free plan allows 100 tasks a month and two-step Zaps (trigger plus one action), with checks every 15 minutes. A confirmation needs the trigger plus one message action, which fits. A Zap that also updates your sheet needs a second action and a paid plan.
Count tasks before you commit: each successful action counts as one task. Forty event entries a month with one confirmation each is 40 tasks. Add 40 reminders and 40 waitlist notes and you are at 120, over the Free limit, so reminders need a paid plan or a different route such as scheduled sends from your messaging tool.
Use AI to write the templates once, not on every send. Here is a prompt and a trimmed result.
Write four short customer messages for a tabletop and card games shop.
Friendly, plain, under 40 words each, no emojis. Use these merge
fields exactly: [first name], [event], [date], [time], [seat status].
Messages: 1) booking confirmed, 2) you are on the waitlist,
3) a seat has opened, reply YES within 2 hours to keep it,
4) reminder two days before, reply NO if you cannot make it.1. Hi [first name], you're in for [event] on [date] at [time]. See you
at the shop. Reply NO if plans change and we'll offer your seat on.
3. Hi [first name], a seat has opened for [event] on [date]. Reply YES
within 2 hours to keep it, or we'll offer it to the next person.What you would fix: confirm the "reply" route actually works. If your system cannot read replies automatically, change the wording to "call or text the shop on [number]" and handle replies by hand. A message that promises a feature you did not build is worse than a plain one.
The waitlist rule written down
Decide the rule once and put it on the form: waitlist is first come, first served; an opened seat is offered by message with a two-hour window; if there is no reply, the seat moves to the next person. Staff then apply it the same way every time, and nobody has to argue about favourites. Add a line in the sheet: when you promote someone, change the status and note the time. The log settles disputes.
Step 3: pre-order lists and deposit reminders
Pre-orders are where a games shop's cash flow lives. A distributor sets the order deadline, you collect interest from customers, and a deposit separates real orders from wishful ones. The workflow:
- Take the pre-order at the counter or through a form. Record product, quantity, contact, consent and deposit due. Deposits are taken through the till or your payment provider, not through AI or the form.
- Mark the deposit paid in the sheet when the money lands. Keep it a manual tick; it ties your list to your takings.
- Reminder run. Each morning, filter the Pre-orders tab for "deposit paid = no" and "days to distributor deadline is 5 or fewer". Send a reminder to those rows.
- Release-day message. When stock arrives, mark the rows "ready" and send "your pre-order is ready to collect".
- Uncollected follow-up. Seven days after "ready", send one polite message; after your stated hold period, release the item to the shelf.
The hold period belongs in your pre-order policy, which should also say what happens to deposits if the release is cancelled or delayed. If you do not have one, the pre-order policy checklist gives a structure, and a qualified adviser should look over refund wording.
Reminder wording, tested against the sheet
Hi [first name], a quick reminder: your pre-order for [product]
needs the [deposit amount] deposit by [date] so we can include it in
our order. Pop in, call us, or reply here and we'll sort it. Thanks!Run this against three real rows before turning anything on. Common faults: the deposit amount merges as blank, the date merges in a month-first format your customers misread, or one customer with two pre-orders gets two texts. Fix by adding a column "reminder sent on" and a filter that skips rows with a date in it.
A quick sum: is the automation worth it?
Say your shop runs four events a month with about 30 sign-ups in total and 40 pre-order lines. Manually: 30 confirmations, 30 reminders, and perhaps 20 waitlist or reschedule messages is 80 messages. At about two minutes each (find the customer, type, send, log) that is roughly 2.7 hours. Pre-orders add maybe 40 deposit chasers and 40 ready notices at one and a half minutes each: another two hours. So about 4.7 hours a month of pure admin, illustrative.
Automation does not delete that time. Setup might take six to ten hours once, and exceptions will still take a few minutes each. It pays back in two or three months if the volume is that steady, and it makes sure every reminder actually goes out, which is where manual chasing usually slips. If your volume is half that, a templated message you paste by hand, written once with AI, gets you most of the benefit at no tool cost.
Texts, email or both
Texts are read quickly and suit "your seat has opened" within a two-hour window. Email suits longer information: rules for an event, what to bring, deck-registration deadlines. Ask which customers prefer which and store it in the Entries tab.
For texts, you need a way to send them. A business phone service such as Quo lists plans from about $19 a user a month on annual billing ($28 monthly) as of late October 2026; check the current plans and the messaging limits before choosing. Whatever you use, collect consent on the form, include a way to stop, and look up the rules for marketing texts that apply to your customers. If you are unsure, ask a qualified adviser.
WhatsApp has its own rules. On its business platform, a message that starts contact outside the 24-hour customer-service window must be an approved template, and from 1 October 2026 some service and utility messages that used to be free became billable, so do not assume a free personal number is a sensible route for automated release messages.
Release-day messages that do not cause a queue
Release day is where a pre-order list pays off, and where a poor message turns into a queue at the door. Set a release-day schedule and send customers a collection window.
Hi [first name], your [product] is in. Collect any time Saturday
10:00 to 18:00 and bring this text or your name. We'll hold it until
[date]. Reply here if you need a different day.Stagger by surname or order number if you expect a rush: "A to H collect 10:00 to 12:00" is easy to apply from the sheet. A booster-box release with forty pre-orders in a small shop is manageable without staggering; with 150 it will not be.
Keep a printed list at the counter, sorted by name, with a collected column. A tablet running the sheet is fine, but when the shop is busy a paper list never needs a charge or a login.
Using AI on the data itself
Messages are the obvious job. Two quieter ones save more time. The first is tidying sign-up data. Hand-typed names and numbers arrive messy: "mike", "Mike R.", a phone number with a missing digit, a duplicate entry because someone submitted twice. Paste a batch of rows (names and numbers only, with no payment details) into an AI tool and ask it to flag likely duplicates and numbers that are too short. It will not be right every time, so treat its list as a set of rows to look at, not a set of rows to delete.
Here are 12 sign-ups for one event. List any rows that look like
duplicates (same person, different spelling), and any phone numbers
with the wrong number of digits. Do not delete or merge anything.
Return a table: row number, problem, suggested fix.The second is a post-event summary. After each night, jot a few lines in the Events tab: how many turned up, how many left early, what players said. Once a month, paste the notes into an AI tool and ask for patterns: which nights fill first, which formats flop, what newcomers asked for. Ten minutes of reading the summary beats a vague memory of how things went.
An illustrative Friday night, start to finish
A small shop runs a beginner card night with eight seats. The form opens on Monday. By Wednesday it is full and a waitlist of three has formed. On Wednesday evening the automation sends the two-day reminder to the eight confirmed players; two reply NO by Thursday. The shop owner changes those two rows to "cancelled" and the first two waitlisted players receive a "seat opened" message with a two-hour window. One says yes immediately; the other does not answer, so at the two-hour mark the owner promotes the third person.
On Friday at 17:30, an hour before the start, a final message goes to anyone still unconfirmed saying their seat will be released at 18:15. One player is late and finds the seat gone, which is awkward, but it was stated in three messages and on the form. Eight people sit down; one confirmed player does not arrive and is marked a no-show in the sheet. After the third no-show, the shop's rule (written on the form) asks that player to pay the entry fee up front next time.
Count what changed. The owner sent no messages by hand except two replies to special requests, and the log shows exactly who was offered which seat and when. The cost is a few hours of setup and the discipline of updating statuses.
The reminder Zap that sent four messages in one afternoon
A different shop connected its sign-up form to a reminder Zap and tested it with one entry. In real use, customers signed up to two events each, and the Zap sent every reminder for every row, so some players received four messages on the same afternoon. The complaints were polite but it looked careless. The fix was a "reminder sent on" column, a filter that skipped rows already dated, and a rule of one combined reminder per customer per day. The lesson for your own rehearsal: test with a customer who has two entries and a customer who cancels, not only the clean case.
Writing the event description once, with AI
Every event needs a short description for the form, the shop window and social posts. Describe the format in your own words (how many rounds, what players bring, whether decks can be borrowed) and ask the AI to turn it into a 60-word description for beginners and a one-line version for a poster. Read it for two things: invented promises ("all supplies provided") and tone. A beginner night that reads like a competitive tournament pushes newcomers away, which is the opposite of what you want from the sign-up page.
What to leave to people
- Allocation when stock is short. If the distributor sends 30 of your 40 pre-ordered boxes, deciding who gets what is a business decision. Use a fixed rule (deposit paid date, first order first), apply it consistently, and message everyone affected personally.
- Complaints and refunds. Draft replies with AI if you like, but a person reads and sends them.
- Under-age players. If events admit children, a parent or guardian contact and consent are your own policy decision; do not leave them to a form default.
- Money. Deposits, entry fees and refunds go through your payment system. Do not build payment steps in an automation tool unless you are comfortable maintaining them.
How to check the automation works
Before launch, run a dress rehearsal with your own number and a staff member's. Sign up to a test event with eight seats, fill the form to its limit, join the waitlist, cancel one entry and promote the waitlisted person. Check each message arrives, reads correctly, and logs a row. Then do the same for a test pre-order: deposit due, reminder, ready, collected.
Every month, scan the Entries and Pre-orders tabs for rows stuck in a status for too long: confirmed entries for a past event, pre-orders marked ready for more than your hold period. Those rows point at a step that did not fire. Also review your automation tool's run history: tools pause or hold runs when you hit plan limits, and on Zapier a Zap auto-pauses if 95% of its runs error over seven days. A quiet failure on Thursday means missed messages on Friday.
For ideas on connecting a form to an AI step without writing code, adding AI steps to Zapier explains where AI actions cost extra tasks. The stock side of pre-orders, including singles and trade-ins, is in the games-shop inventory tutorial, and software choices for tournaments are compared in game store software for trade-ins and tournaments.
The same form-to-reminder pattern appears elsewhere: a bakery pre-order form with collection slots uses slots instead of seats, and a community centre's volunteer rota uses reminders for people rather than products. If you would like help choosing the smallest set of tools for your shop, that is what my AI implementation consultation covers; you can get in touch here.
Questions from games-shop owners
Which tool should a games shop start with?
A free form tool that can close at a set number of entries, such as Tally, plus a spreadsheet. Add Zapier or a similar automation tool only when you are copying the same data by hand every week. Start with the form and sheet and see where the manual work really lands.
Can AI take pre-order deposits?
No, and it should not. Take deposits through your till or payment provider and let automation send reminders based on the spreadsheet. AI writes and tidies the wording of messages; money handling stays in a system built for payments.
How do I stop no-shows at events?
Send a reminder two days and two hours before, ask for a reply to confirm, and release unconfirmed seats to the waitlist an hour before start. A small entry fee or deposit refunded on attendance also helps, if your payment setup supports it.
Is it fine to text customers about releases?
Only customers who agreed to receive texts for that purpose. Record consent on the sign-up form, include a clear way to stop, and check the messaging rules that apply to your customers before you send marketing messages.
Further reads
- AI for Butchers: Christmas Pre-Orders, Cut Lists and Pick-Up Slots — Pre-orders with pick-up slots in a butcher's busiest week.
- AI for Farm Shops: Weekly Boxes, Seasonal Labels and Pre-Orders — A recurring pre-order list run from one sheet.
- Can AI Run Your Studio's Class Waitlist Automatically? — Waitlist rules for classes with a fixed number of places.
- How Small Shops Can Use AI to Forecast Stock and Reorder — Use pre-order counts to set your wholesale order.
- Board Game Café Business Plan: Table Pricing, Menu and Bookings With AI — How a board game café can price table time, cost a game-friendly menu, design booking slots and plan year one, with AI drafting and a spreadsheet checking.
- Bookshop Event Ideas: Author Nights, Book Clubs and Signings With AI — A filled-in event plan, a publisher outreach email, ticket-page copy and a promotion run for author nights, signings and book clubs.
- Yarn Shop Marketing: Fill Knitting Classes and Promote New Stock With AI — A class calendar, listing and caption prompts, a monthly newsletter template and a three-hour routine for a small yarn shop's marketing.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Tally pricing page (Free plan: unlimited forms and submissions under fair use; close forms on limit or date); Zapier plan pages (Free: 100 tasks a month, two-step Zaps, 15-minute checks); check each vendor's current plan before you subscribe.