dispatch · in private build
Dispatch any crew. Any show.
Stop chasing fourteen threads to fill one call. Dispatch pulls every show request into one ranked queue, with a receipt on every decision.
who built this
Built by someone who works the calls.
The dispatch software that exists today was built by people who never had to wake up to a venue-changed-its-loading-dock email, never had to figure out who’s ETCP-certified at 6am, never had to defend a dispatch decision in front of a grievance committee.
Its author has — a working IATSE journeyperson, thousands of show hours across theatre, festival, corporate, and broadcast. The data model encodes those hours.
pick your side
Three views, three jobs.
for the dispatcher
I run a dispatch desk.
Union locals, vendor shops, anyone routing crew. Ranked queue. Premium math. Grievance-ready audit log.
See the dispatcher view →
for vendor shops + employers
I'm hiring crew or running a shop.
Submit a show in 90 seconds. Or run your own bench. Two audiences, one page.
See the employer view →
for crew
I'm crew.
Every dispatch from your local or shop in one clean inbox. Your phone, your calls, one tap.
See the crew view →
drag-drop · live demo
Drop a call sheet. Get a call.
The first interaction with Dispatch isn't a form — it's a drop zone. AI TD reads the file the producer already sent you and files the request for you.
step 1 of 5
Drop a call sheet.
PDF, Word, Excel, image — whatever a producer just emailed you. No reformatting, no copy-paste.
live sandbox · real AI TD
Try it now.
Drop a call sheet here, or
max 1 MB · pdf / docx / xlsx / text / image
under the hood
How it works.
The corpus
Every IATSE local. Every Teamsters local that runs a load-in. A thorough understanding of the agreements that govern crew pay across the trade. Vendor + partner network. Venue + room intelligence. Decades of operator-level wisdom.
How the TD learnsThe TD
AI TD orchestrates inbound channels (email, text, voicemail, booking page) and outbound (text, email, voice, web). Reads the corpus. Cites the answer. Logs every decision. Learns from every override.
The flywheel
More crew → sharper skill catalog. More shows → outcome recipes. More vendors → wider sourcing. More locals → broader reach. More aggregates → pricing power. Every dispatch makes the next one easier.
How Dispatch measures valueThe receipts
Every offer pushed, every reply, every confirmation, every pass-back, every override — stamped, attributed, queryable. When a grievance lands, the timeline is the answer.
the wall
Your data, contained.
Production data is sensitive. Crew personal records, CBA-protected wage information, vendor pricing — none of it leaks past the people who legitimately need it.
- Row-level security on every org-scoped table
- User-scoped personal records (xHand)
- TLS 1.3 in transit, AES-256 at rest
- No model training on your data
Full writeup at /security.
common questions
Quick answers.
Who is Dispatch for?↓
Anyone who routes crew to shows. Union locals dispatching members under a CBA. Vendor shops calling out of a freelance bench. Tour managers running the same crew across cities. Any size show.
Is this only for union dispatch?↓
No. Dispatch works for freelance crew pools, vendor benches, and union locals from the same data model. The union-specific features (tier-aware ranking, CBA-bound premium math, grievance documentation) only activate when the org is configured as a local.
How is this different from Union Impact?↓
Union Impact is a generalist union-management platform mostly used by trades outside entertainment. Dispatch is the first SaaS purpose-built for live-entertainment crew dispatch — the data model encodes how entertainment crews actually get called.
Can I see it in action?↓
Yes, by invitation. Dispatch is in private build — onboarding one shop, one tour, one local at a time. Pick the page that fits and book a walkthrough.