Event operations app for on-site teamsThe DMC Pilot app for your team on site.

Neither. It signs in to the same company with the same account. It reads the same records and follows the same permissions and plan limits your people already have. A guest checked in on a phone in the arrivals hall is the same guest the desk sees. With signal the office sees it at once, and a tap made without signal is sent when the phone is back online. There is no second copy of the data to match up afterward. What it leaves out is the desk work, on purpose.

Because a proposal builder on a phone is a worse proposal builder, not a more convenient one. Costing, invoicing, the Products & Services catalog 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.

No, and that is deliberate. The app is for your own staff and the freelancers you invite, who use it free and see only the programs they are assigned to. Everyone else gets a link or a portal instead: a transport supplier checking its runs in your branded supplier portal with an emailed code, a guest signing a waiver, a photographer uploading to an album, a casual hire checking in for a shift. Each of them only needs the link.

Chat, check-in lists and issue logging keep working, and everything else tells you. A message written with no signal waits in its conversation with a clock beside it, is kept if the app is closed, and goes by itself, in order and only once, the moment the phone is back online; one the server refuses says Not sent and offers Try again. Conversations you have opened are kept on the phone, so they stay readable and catch up on what you missed when you are back. A check-in list you have opened works with no signal too: taps wait on the phone, the screen says how many are waiting, and they go when the signal returns. An issue logged with no signal, photos included, waits the same way and is sent when the signal returns. Every other change, such as a transfer change, needs the connection and fails visibly without it, because on a program a write that silently did not happen is worse than one that told you so.

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 sign-in is encrypted on the phone, with its key kept in the phone's secure storage. Two things are kept on the phone: recent chat (messages, drafts and unsent messages), so conversations open at once, and the list of a check-in you opened, guest names and seats only, never contact or health fields, encrypted and destroyed after 16 hours. Signing out deletes both. Removing a member on the Team page ends their access on the phone the same way it ends it on the web, because it is the same account with the same permissions.

Push for the things that need a person now: mentions, direct messages, answers from Dispatch AI and ops alerts (team broadcasts, supplier pickup notices and the next-day dietary count), each with its own switch. Conversations can be muted individually, the badge count respects that, and an urgent broadcast still arrives. A preview carries at most 140 characters of the message: no attendee record field is ever put in a notification.

Nothing extra. It is the same seat on the same plan, on every plan, including Core, and freelancers use it without taking a seat. Chat, check-in and Dispatch AI are on every plan; the day sheet, transfers, IROPS, broadcasts and the time clock appear on Growth and up, as on the web.

It comes with your account. It is on the App Store for iPhone and on Google Play for Android. They sign in with the email and password they already use, with two-factor codes where those are switched on. Organizations that enforce single sign-on use DMC Pilot on the web for now. There is no separate mobile license to buy and nothing to configure per device.