Chat
Company channels, program channels and direct messages. Replies, reactions, pins, search and unread counts, all realtime. Voice notes, photos and files. Conversations mute individually.
Event operations app for on-site teamsYour operation does not happen at a desk.
DMC Pilot on iOS and Android puts chat, the day sheet, transfers, attendee check-in and IROPS in the hand of the person actually running the day, writing to the same records the office is watching. Included on every plan.
iPhone and iPadAndroid
One app, one codebase, both platforms. It comes with your account: during onboarding we send your team the install link, and they sign in with the credentials they already use. Nothing extra on the invoice.
2
platforms, iOS and Android
1
record, written from either side
14
permission modules, the same ones as the web
0
extra cost, on every plan
01The mechanism
The same write, made from the floor.
This is not a companion app with its own copy of the data. A check-in tapped in the arrivals hall, a run acknowledged at the curb and a voice note posted to the program channel all land on the program record while they are happening, and the office watches them arrive.
- One database, one permission model, one activity log
- Realtime both ways: what the office changes is on the phone before anyone asks
- System events post into program chat, so the channel stays the timeline
- Nothing to export, nothing to reconcile at the end of the day
Four reasons it is not a companion app.
Every one of these is something a team has been burned by before: a second database, a weaker permission model, a silent send queue, an upsell.
- 01
One record, not a copy
An attendee checked in on a phone is the same write as one made at a desk. It lands on the program immediately. There is no sync step, no export, and nothing to reconcile in the evening.
- 02
The same permissions
The app signs in to the same organization with the same account and passes the same server-side checks. A person who cannot edit transfers on the web cannot edit them on a phone either.
- 03
A failed send says so
Offline, a message that could not send tells you and offers a retry rather than sitting in a queue that delivers an hour later. On a live program, a late instruction is worse than a visible failure.
- 04
No separate price
The same seat on the same plan, on every plan. Anyone who can sign in to DMC Pilot can sign in on their phone, and nothing about it appears on the invoice.
What belongs on a phone, and what does not.
Most mobile apps in this category are the whole product squeezed into a smaller screen, which is why people open them once. This one carries the work that happens standing up and leaves the work that needs a keyboard where it belongs. The line is drawn on purpose, and we would rather print it than have you discover it.
In the hand
The work that happens standing up
- Chat with the team, with voice notes when your hands are full
- The day sheet for the program you are on, in the program's own time zone
- Attendee check-in at the arrivals gate
- Transfer runs: assign a driver, dispatch, acknowledge a re-optimization
- Raise an incident and work it, without finding a laptop
- Client and supplier records, with one tap to call or WhatsApp
- Files and photos, uploaded from where they were taken
- The time clock, for your own staff on shift
At the desk
Deliberately left on the web
- Building a proposal and laying out its blocks
- Costing, margin and the price book
- Invoicing, credit notes and the cash ledger
- Configuring the organization, roles and permissions
- The Content Library and the Service Catalog
- Reporting across a season
Both columns read from the same record. Only the place you work changes.
02A day on the ground
Six in the morning to the last coach out.
The day sheet before the desk opens, the manifest in the arrivals hall, the coach that is late, and an evening with nothing to write up. The record was made as the day happened, by the people it happened to.
- The day sheet is assembled on the server, so the phone and the web read the same one
- Times are shown in the program's own time zone, never the handset's
- A zone chip appears only when your device disagrees with the program
- Everything posted from the floor is attributable, with a name and a timestamp
- 06:10The day sheet for the program you are on, in the program's time zone, with what moved overnight already on it.
- 09:35Guests come through arrivals. You tick them off the manifest and the count on the office board moves as you tap.
- 12:50A coach is late. Raise it as an incident, send a voice note to the channel, reassign the run. Everyone reading the program sees all three.
- 23:40Nothing to write up. The record is already the record, and tomorrow's sheet is already correct.
Everything the app carries.
The operational half of DMC Pilot, on the phone your team already has in their pocket.
Dispatch AI
Ask it a question about a program and it answers from your records inside the conversation, with the same grounding and the same permission gate as on the web.
Programs and the day sheet
The programs you are on, with the Run of Show assembled per day in the program's time zone. Team, suppliers, events and vitals on the same screen.
Transfers
The transfer board for the day: assign a driver, dispatch a run, cancel, and acknowledge a re-optimization when a flight moves. State changes post to the program.
Attendee check-in
Tick guests off the manifest as they come through the hall. The count on the office board moves as you tap, and two people checking the same guest is handled rather than silently overwritten.
Flights
Arrivals and departures for the program, with live status and the local times that matter at each end.
IROPS
Raise a disruption incident, work the impact, and stand it down. The duty-of-care timeline is written as it happens rather than reconstructed after.
Clients and contacts
The people behind the account, with key dates, follow-up cadence and one tap to call, email or WhatsApp from the record.
Files
The company drive and each program's drive, with previews, search and share links. Upload the photos from where they were taken.
Time clock
Your own staff check in and out of a shift on their phone, with location captured at the moment of the punch.
Push and activity
Push for mentions, direct messages and Dispatch answers. The badge respects muted conversations, and nothing that could carry sensitive attendee detail goes in a preview.
iOS and Android
One app, built from one codebase, on the phone your team already carries. Nothing to provision, no separate account to create.
The count on the office board moves as you tap.
Check-in is the moment the operation and the record usually come apart. Here they are the same action, and when two people check the same guest within a second of each other the app resolves it instead of quietly overwriting one of them.
Nobody outside your team installs anything.
The app is for your own staff, the people with accounts and permissions. Everyone else gets a link. That is not a limitation we are apologizing for. It is the reason your drivers and your clients actually use what you send them.
Your staff, with an account
Operations leads, coordinators, guides on payroll and anyone else who already signs in to DMC Pilot. One install, their existing credentials, the permissions they already have.
Everybody else
Drivers acknowledging a run, guests signing a waiver, clients watching the live cockpit, photographers uploading an album, freelancers punching a shift. No install, no account, no training, and nothing to chase.
Mobile questions
Is it a separate product, or a cut-down version of the web app?
Neither. It signs in to the same organization with the same account, reads the same records and obeys the same permissions and plan limits your people already have. An attendee checked in on a phone in the arrivals hall is the same write as one made at a desk, and the office sees it immediately. There is no sync step and no second copy of the data to reconcile afterward. What it leaves out is the desk work, on purpose.
Why does it not do everything the web does?
Because a proposal builder on a phone is a worse proposal builder, not a more convenient one. Costing, invoicing, the Content Library and organization settings are jobs for a keyboard and a large screen, and pretending otherwise produces an app people open once. The app carries the work that happens standing up. That is the whole design.
Do drivers, guides and guests need to install it?
No, and that is deliberate. The app is for your own staff, the people with accounts and permissions. Everyone you cannot realistically onboard gets a link instead: a driver acknowledging a run, a guest signing a waiver, a photographer uploading to an album, a freelancer punching a shift. No install, no account, no training. Two different problems, two different answers.
What happens when the signal goes?
It tells you. A message that could not send says so and offers to retry, rather than sitting in a queue that silently delivers an hour later. On a program, a transfer instruction that arrives late is worse than one that visibly failed, so the app refuses to pretend. What is already loaded stays readable, and it catches up on the missing messages the moment you are back.
Is attendee data safe on a phone that gets lost?
Sensitive attendee detail is fetched for the screen and never written to the device's stored cache, so it does not sit on the handset after the app closes. The session itself is held in the device keychain. Revoking a member's access in Settings ends their access on the phone the same way it ends it on the web, because it is the same account and the same permission model.
Does it notify people, or just sit there?
Push for the things that need a person now: mentions, direct messages and answers from Dispatch AI. Conversations can be muted individually, the badge count respects that, and nothing that could carry sensitive attendee detail is ever put in a notification preview.
What does it cost?
Nothing extra. It is the same seat on the same plan, on every plan, including Core. If somebody can sign in to DMC Pilot, they can sign in on their phone.
How does our team get it?
It comes with your account. During onboarding we send your team the install link for iOS and Android, and they sign in with the credentials they already use. There is no separate mobile license to buy and nothing to configure per device.
See it on your own programs.
A 30-minute walkthrough with the team, on data that looks like yours. Sales-led onboarding: we load your catalog, your vendors and your first programs with you.