How to Handle Gig Bookings Without the Email Chaos

Feb 5, 2026

Most bands run their bookings through someone’s personal Gmail. Which means missed messages. Which means the band leader leaves and takes every venue contact with them. Which means a dep asks “what time is load-in?” and the answer is buried somewhere in a thread that three people were CC’d on four months ago.

It does not have to work this way. Here is a practical workflow for managing gig bookings from first inquiry to confirmed gig — one that scales as your band gets busier and survives personnel changes.

The Booking Email Problem

The core issue is not email. Email is fine. The problem is personal email — an inbox only one person can see, with no shared history, no way to assign follow-ups, and no record that survives if that person steps back from the band.

Think about what gets lost:

A venue emailed six months ago about a recurring Friday slot. Nobody remembers what was agreed.
A promoter sent a follow-up that landed in someone’s spam.
The band manager who handled all the bookings left, and the history walked out the door with them.
Three people are now CC’d on every thread “just in case,” creating reply-all chaos every time someone responds.

The fix is a single shared inbox — one address, visible to everyone who needs to see it, with a thread history that lives with the band rather than any individual.

Setting Up a Dedicated Band Email

Get a proper band email address: bookings@[yourband].com, or at minimum a Gmail address that is not tied to anyone’s personal account. The domain address looks more professional to venues and promoters, but any dedicated address solves the ownership problem.

What matters most is that more than one person has access. Forward it to the band’s shared inbox in Gigmeister, or set up IMAP access for anyone who needs visibility. When the keyboard player joins or leaves, you update access — you do not lose the thread history.

Thread Management: From Inquiry to Confirmation

Every booking starts as a thread — an email conversation with a venue, promoter, or event organiser. The goal is to move each thread from New → In Progress → Waiting → Closed without anything falling through the cracks.

New — unread inquiry, not yet assigned to anyone.
In Progress — someone is actively handling it.
Waiting — you have replied and are waiting for a response. Snooze the thread to resurface it in a week if nothing comes back.
Closed — gig confirmed (calendar event created), declined, or cancelled. The thread stays in the record; close it when no further action is needed.

Assigning a thread to the person who is handling it means everyone else knows not to reply independently. The thread has one owner. If the owner cannot be reached, anyone with access can pick it up — because the full history is right there.

Assigning Threads Without CC Chains

The moment you assign a thread, the CC chain becomes unnecessary. The person assigned handles it. Everyone else can see the thread if they need to — but they are not getting pings every time someone responds.

This is a small cultural change for bands used to adding half the lineup to every booking email. It takes one gig cycle to appreciate how much quieter it makes the inbox.

AI Draft Replies

A venue sends a booking inquiry. You need a professional response that covers your availability, your rate, your sound requirements, and next steps. You write a version of this email dozens of times a year.

Gigmeister’s AI draft replies read the incoming message, the thread context, any internal notes you have added, and the linked gig details — and generate a starting draft. The tone matches how a working band communicates with venues: direct, professional, not overly formal. You read it, adjust anything that needs adjusting, and send. The research and structure are done; you just review.

This earns its keep most on the variable emails — the ones where the inquiry is specific enough that a template would not fit, but common enough that you know roughly what needs to be said.

Reply Templates for Recurring Responses

For the truly repetitive emails, templates beat AI drafts on speed. The six emails every busy band sends repeatedly:

Availability check reply — confirming you are available and providing your quote
Quote with rider — your fee, what is included, link to the tech rider
Deposit confirmation — acknowledging receipt, confirming the date is now secured
Show-day logistics — load-in time, soundcheck time, set times, parking details
Cancellation — short, professional, no hedging
Rebook follow-up — sent a month after a good gig, suggesting future dates

Templates let you send a consistent, professional email in under a minute. The writing is done once and reused — edit the specific details (fee, date, venue name) before sending.

The AI draft and the template are not competitors — they serve different situations. Template for the predictable, AI for the specific.

Distributing Your Tech Rider

Stop attaching PDFs to every booking email. Not because PDFs are bad, but because you update your rider and the venue is still looking at the version from 2023.

The rider share link is a single URL that always serves the current version of your production documents — tech rider, hospitality rider, stage plan, and patchlist. Send the link once. When you add a new channel to the patchlist, or update your monitor requirements, or change the stage plan because your guitarist switched to a Kemper, the link updates automatically. The venue coordinator can bookmark it and always have the right version for show day.

Drop the link into your quote email. It goes out with every booking confirmation. No more “which version is current?” questions at soundcheck.

The Patchlist: What Your Sound Engineer Actually Needs

The patchlist is the most practically important document you send a venue. It tells the FOH engineer — often someone who has never seen your band before — exactly what they are building before you arrive.

A good patchlist row per input:

Channel number
Instrument or source (kick drum, snare, bass DI, lead vocal, acoustic guitar)
Mic or DI type (or just “condenser mic” / “passive DI” if you are not specifying model)
Stand type (boom stand, short stand, clip)
Notes (phantom power required, pad, polarity flip, stereo pair)

The notes column matters. A drum overhead that needs phantom power, a guitar amp that goes DI rather than mic’d, a backing track output that comes in as stereo — these are the details that cause delays at soundcheck when they surface at the last minute.

Keep it in a simple format. Engineers read these on a phone in a noisy venue. Scannable beats comprehensive.

Tracking Payment and Contract Status

Confirmed gig, verbal agreement, no contract. Deposit sent, not received. Balance due on show day — but nobody wrote down the amount. These are not edge cases; they happen regularly in active bands.

For each gig, track:

Contract status — not sent, sent, signed
Deposit status — not requested, invoiced, received
Balance — amount, due date (usually show day)
Notes — anything the venue has agreed to that is not in the contract

This does not need to be a complex system. It needs to be visible to more than one person and linked to the gig event so the information is there when show day arrives.

When the band arrives at the venue and someone asks “what’s the balance?” — the answer should not require anyone to check their messages.

Keeping the Whole Band in the Loop

When a booking is confirmed, two things need to happen immediately:

The date goes into the band calendar — with load-in time, soundcheck time, set time, venue address, and parking notes
The setlist gets linked to the event (even if it is still a template — it can be finalised closer to the gig)

Every band member with access can see the calendar. They get the gig day details in the app alongside their chord sheets and setlists, not buried in a group message that will scroll away by show time.

When the venue sends an update — say, soundcheck has moved from 4pm to 5pm — update the calendar event once. Everyone sees the change. No group message needed.

The Booking Workflow in Practice

A consolidated timeline for a typical gig, from inquiry to show day:

Inquiry arrives — thread opens in the Shared Mailbox, status: New
Assign thread — booking person picks it up, status: In Progress
Reply with availability and quote — include the rider share link
Venue confirms and requests deposit invoice — send invoice, status: Waiting
Deposit received — update deposit status, create calendar event, close the thread
Send show-day logistics email — load-in, soundcheck, parking, venue contact
Show day — balance collected, show notes added to the thread for next time

From inquiry to confirmed gig, every step is tracked in one place. The next person who handles bookings — whether that is tomorrow or two years from now — walks into a complete history.

Get Started

Manage your band’s bookings, rider pack, and gig calendar from one place. Create a free Gigmeister account or read the Shared Mailbox documentation to connect your band email.