for vendor shops + employers · in private build
Submit a call. Get a crew.
One booking page, one workflow, one receipt. Whether you run a vendor bench or you’re hiring from the local — Dispatch is the surface in between.
for vendor shops + freelance benches
Your bench, your queue.
bench · 34 freelancers · 8 calls active
dispatching1incoming
- National promoter · 4 a1, Sat
- Regional promoter · 2 carp, fri pm
- Promoter X · keynote
- callback · producer J
2bench · ranked
- 1M. ChenA114daudio
- 2P. RiveraA118d
- 3J. SinghA29d
- 4L. ColeCarp22dETCP
- 5K. TanA126d
- + 29 more · sorted by reliability → last-dispatched → skill match
3rate · per crew
4settlement
auto-generates per-call invoice + per-freelancer payable
settle this call →
Incoming requests
Email, text, booking page, voicemail. The TD parses inbound, classifies by skill, queues for the dispatcher.
Your bench, ranked
No CBA, no tier hierarchy by default. Configure your own ranking: reliability, last-dispatched, skills match, geographic proximity. Same audit log either way.
Rate per crew
You set the rates. Per crew, per gig type, per cert. The system computes the line item; you verify.
Settlement
Per-call invoice, per-freelancer payable. Auto-generated from day-worked records. No spreadsheet cross-check.
vendor vs union flow
What’s different.
No tier-aware ranking by default
Configure your own: reliability, last-dispatched, skill match, geographic proximity. Whatever your shop actually uses.
No CBA-bound premium math
You set rates and rules per crew or gig type. The math runs against your rate card, not a collective agreement.
Same audit log
Every decision stamped. Every override has a required reason. Same paper trail that defends a union grievance defends a freelancer dispute.
Same TD, scoped to your shop
AI TD reads your shop's corpus — past calls, gear lists, post-mortems. Your data, your context, your dispatcher's brain on a faster clock.
brokerage layer
When you don’t have the crew, the call still gets filled.
If your bench can’t cover a call, Dispatch can route the request to partner vendor shops or the local that covers the jurisdiction. The call gets filled. The routing is documented. The relationship is visible. You stay in the loop on the outcome.
your bench · example view
Your bench, in motion.
volume
calls dispatched · this quarter
days on call · this quarter
2.8 avg days per call
freelancers worked · unique
26.2 avg days each
bench utilization
utilization (days dispatched ÷ available)
top performers · days worked
acceptance rate · distribution
office speed
office turnaround · avg
crew confirmation · avg
repeat-client rebook · 90 days
brokerage
calls routed to partners · this quarter
routing log audit-ready
filled without spreadsheet cross-check
was ~60% pre-Dispatch
settlement time per shift
↓ from 18 min/shift baseline
baseline comparison · before dispatch vs now
Office turnaround
↓ 73%
Filled without spreadsheet check
↑ all calls
Settlement per shift
↓ 78%
for producers + employers
Submit a show in 90 seconds.
book a crew · your local’s public page
Show name
Venue
Dates
Crew
Special
TD parsed
2-day install · 9 crew · ETCP required day 1 only · gala seating 1,800 · 5am call recommended (loading-dock window).
no login · BA reviews on the other side
The public booking page sits at a URL your shop or local owns. Producers fill the form (or paste a freeform call sheet — AI TD parses it). The dispatcher reviews on the other side. Every submission becomes a receipt — for the producer, for the dispatcher, and for the audit log.
- Auto-classification from a pasted call sheet
- Pre-fill from your last show with this org
- Submission timestamp + email confirmation
- Dispatcher response with offer status
returning employer
Last year’s gala lives here.
Pre-filled show templates
Every prior call is saved. Next year’s gala starts from last year’s configuration. One click to re-book.
History with this org
Crew you've worked with. Calls that ran clean. Calls that didn’t. The TD has read every post-mortem.
Rate visibility (when granted)
If the org opts in, you see rate ranges they typically run. Negotiation with information, not against it.
One-click re-book
The submit button on a re-booked configuration is one tap. The BA gets a fully-typed request with the prior-year context attached.
your history · example view
What you’ve worked, remembered.
overview
calls placed · in 3 years
days booked · total
avg office turnaround on your requests
per-show recall · timeline
- Oct 202514 min
Foundation gala
9 crew · 2-day install
- Mar 20259 min
Tech keynote · day-of
22 crew · 1-day
- Sep 202421 min
Foundation gala
9 crew · 2-day install
- Jul 202434 min
Music festival · stage carp
14 crew · 4-day run
- Sep 202340 min
Foundation gala
8 crew · 2-day install
the pattern
Your gala has run year over year. The 2025 office turnaround was 14 minutes — down from 40 minutes in 2023 (pre-Dispatch). One-click re-book of next year’s configuration is live and waiting on your dashboard.
honest limits
What Dispatch does not do.
No payments layer
Dispatch doesn't process money between you and the org. Booking, fulfillment, audit only.
No contract layer
Doesn't replace your contract with the org. Your master agreement stays where it lives.
No invoicing for you
Vendor shops settle through Dispatch; producer-side invoicing stays in your accounting system.
pricing
Vendor shops pay. Employers don’t.
- Vendor shops: flat monthly, tiered by bench size. Design partners pay nothing during the prototype phase.
- Producers + employers submitting calls into someone else’s Dispatch system: free. The shop or local that hosts the booking page covers the cost.
every action trains the TD
The longer Dispatch runs in your operation, the more it knows about your operation specifically. Override rate drops as the TD learns your patterns. Answer quality climbs as the corpus deepens.
running a shop?
Book a vendor walkthrough.
30 minutes. Your bench, your rate card, your gig pipeline. We show what the queue looks like with your data.
hiring crew?
Try the booking page demo.
90 seconds. Walk through what submitting a show looks like on the public-facing side — what the producer sees, what the BA gets, how AI TD parses freeform input.