Hot CuesThe full tour
A week in the life of one booking, with nothing left on another app.
Follow a single wedding from the Monday it lands in your inbox to the Monday after, when everyone's been paid. Everything below ships today — the maybes live on the public roadmap.
The sale, tracked as a sale
A date lands in the pipeline before you've finished your coffee.
A public inquiry form on your own page feeds a Kanban board that tracks the sale — New, Quoted, Booked, Lost — separately from the event itself, so a completed wedding never gets shuffled by a board move.
The dashboard nags so you don't forget
Which proposals have gone quiet, which calls never got their notes written up, which dates clash with what's already booked — the “needs a human today” list, every morning.
Strangers stay at the door
An unauthenticated form submission never lands inside a client's portal and never silently merges with an existing client — a human triages it first, with the possible match flagged.
One inbox for every conversation
Messages thread against the client and the event they belong to, and the company-wide inbox shows who's waiting on a reply — no more digging through a personal mailbox for the venue question.
Contracts & the deposit, one motion
The date isn't real until it's signed and deposited.
Draft from your own template with the names, date, venue and quote already merged in. Send it and the text freezes; the client signs with a typed name from their portal; the signature itself mints the deposit invoice. No third tool, no re-typing, no gap where the booking lives in an email thread.
- Merge fields that stay honestNames, date, venue, package total and the itemized quote resolve when you draft — and an unknown field stays visible instead of vanishing.
- Frozen at sendWhat they sign is what you sent. Edits after signing mean voiding it on purpose, with your name in the audit log.
- Copies for the people payingSend a copy to a parent or the planner — they get the full text by email, while the signature stays with your client alone.
- Signing mints the depositThe moment the typed name lands, the deposit invoice exists and is on its way — exactly once, even if they tap twice.
The questionnaire writes itself
The timeline decides the questions. The couple just answers.
This is the mechanism nobody else has: Hot Cues reads your run of show, works out which formalities need a song or an answer, and builds the questionnaire from them — in the order the day actually happens. A couple skipping the garter toss never sees a garter question, and every answer lands on the exact cue it belongs to.
Templates that know weddings
A processional is four moments, not one. Your event templates break the formalities out properly, so nothing hides inside a line that just says “Ceremony”.
Meetings booked inside the planner
Open your weekly windows once and couples book real slots from their portal — your calendar blocks them for the whole company, with 12 hours' notice guaranteed. No Calendly link-out.
Machines suggest, you approve
Emails, call transcripts and pasted notes get read for songs and details — and everything lands as a pending suggestion a person accepts. Nothing edits the sheet on its own.
Requests with a chain of custody
A request and a rule shouldn't look the same at 10pm.
Everything the couple and their guests give you arrives in tiers — Must play, Play if possible, Do not play — so the sheet tells you how much each track means before you're standing in front of the floor.
Guests request from a link
Every event gets a shareable page the couple can send with the invitations. Requests land in the same tiers, attributed, ready to triage — not shouted across the booth.
Songs attach to moments
The first dance track lives on the first dance cue, not in a separate playlist you cross-reference. What still needs a song is a list the sheet keeps for you.
The do-not-play list is law
It prints with the sheet and travels with the event, so the DJ you send knows the Chicken Dance is banned before the request comes in.
Real roles, real departments
Assign the gig, and the rest follows it.
People are organized the way your company actually is — DJs, MCs, lighting, photo booth, coordination — with leads per department and access levels that gate what each person can touch. The payout split is set when you assign the gig, not remembered on Monday.
Offers they answer from a phone
An assignment goes out as an offer with the date, the role and the pay on it. Accepted means on the schedule; declined means you know now, not Saturday.
Everyone sees their own season
My-schedule shows each person their gigs and nothing else. Staff see the events they work; the books stay with the people allowed to see them.
The crew pack travels
Arrival times, the venue's quirks, who's who in the wedding party — the sheet carries what you'd otherwise say on a phone call, so a second crew runs it the way you would.
The night itself
Saturday gets its own page.
The offline sheet, the live ticks, the barn with no wifi — the night is the whole reason the product exists, so it isn't a bullet point here.
Deposits in, balances out, shares paid
The night ends. The business doesn't.
- Invoice straight from the eventDeposit and balance, card or a Venmo / Cash App link if that's what your clients use. Money that arrived outside the system still gets marked paid by a person, on purpose, with their name against it.
- Payouts that come off the assignmentEach DJ's share derives from the gig they were assigned, at the split you set then. It will never release more than actually came in — it holds and tells you instead.
- Reports an owner actually readsThe season by month, by event type, by staffer — what booked, what paid, what's outstanding.
- Gear that earns its keepThe inventory sheet ties every uplighting rig and photo booth to the bookings it earned, so payback isn't a guess.
The parts you stop thinking about
Quietly yours, all the way down.
Your brand on every client screen
One hex value repaints the portal, the sign-in page and the printed sheet — every derived shade checked for contrast so nothing you pick can quietly go unreadable.
A venue book that compounds
Load-in doors, dead outlets, the coordinator's rules — written once, attached to the venue, waiting for the next person you send.
Isolation the database enforces
Another company on Hot Cues can never see your events, clients or numbers — that separation is enforced by the database itself, not only by the code that queries it.
Leaving stays easy
Every plan — Free included — exports everything it ever put in, one click, any time. That promise disciplines everything else we build.