Dispatch talks to the flight line.
When a tail goes down, the reassignment happens in the same thread the crew already reads, because the thread was opened by the booking and the squawk posted directly into it. Chat that integrates with your flight line behaves very differently from generic chat.
Nobody has to remember to make the group.
The limitation of generic team chat isn't features: it's that somebody has to manually create channels and invite participants for every single flight. Here, the system provisions them automatically.
A thread for that flight, with the student, the instructor, and the office already in it. Confirmations, denials, and cancellations post into the same thread as they happen.
A thread for that discrepancy, opened for the person who found it. A work order gets its own channel; work orders are never merged into the squawk thread.
A per-tail channel, so the quirks, the recent squawks, and the shared-scheduling arguments about one airplane live in one place.
A coordination channel for the student and the instructor, so the logistics of a checkride don't run over text message.
One channel per cohort, shared by everyone in the same course. It grows as students enrol rather than forking into a second group.
A private instructor-and-student channel. Endorsements, lesson reschedules, and post-flight debriefs all post into that same thread.
N9127F is DOWN: vacuum pump. Moving your 1400 to N738GG.
Copy. I'll tell the student.
24 kinds of channel, one taxonomy.
Every channel has a kind, and the kind decides its identity, who's in it, and who may post. That's what stops a chat feature turning into an unmanageable pile of rooms after six months.
- Direct message
- Group DM
- Booking
- Squawk
- Work order
- Aircraft
- Stage check
- Cohort
- Instructor & student
- Renter check-in
- Onboarding cohort
- Squadron
- Trip
- Expense
- Document
- Guest
- Announcements
- Alerts
- News
- General
- Instructors
- Maintenance
- Safety
- Events
Chat is easy to demo and hard to run.
Announcements are read-only for a reason
Posting rules are per channel kind. Ordinary threads are open to their participants; the announcement, alert, and news family requires the broadcast capability, which only admins and chief instructors hold.
A work-order requester keeps their voice
Some channels allow the person who opened the thread to post even without staff capabilities, allowing members who raised a work order to answer questions about it.
One conversation per pair, not two
Two-party channel ids are derived from the sorted pair of users, so a message from A to B and from B to A land in the same thread. Nobody ends up with two half-conversations.
A redelivered event can't double-post
Every automatic system message carries a deterministic id derived from the event that caused it. Infrastructure retries are invisible instead of embarrassing.
Unread is a number, not a scan
Your unread count is the gap between the thread's latest sequence and your read position. It stays instant on a thread with ten thousand messages in it.
Real-time across replicas
New messages, typing, and presence fan out per organisation, so a message sent on one server appears on a stream open against another. A dropped live delivery reconciles from history rather than disappearing.
The ordinary things, present and working.
- Threaded replies
- Edits
- Deletes
- Pins
- Reactions
- Mentions
- Attachments
- Link previews
- Read receipts
- Message reports
Attachments are stored as references to your files in object storage, never as bytes inside a message. Reported messages go to a moderation queue with an audit trail behind it.
The thread is downstream of the work.
Booking created, confirmed, denied, cancelled, or rescheduled: each lifecycle event posts into the flight's own thread.
MaintenanceSquawk threads and work-order channels, with status changes and completion posting into them.
TrainingEndorsements, certifications, lesson reschedules, and post-flight debriefs land in the instructor's thread with that student.
Do my members need a separate chat account?
No. Threads, messages, participants, and read state live directly in WingWrangler alongside the rest of your operation. It uses your existing logins and roles, so members never need an invitation to a second product.
Do I have to create channels manually?
Mostly not. Bookings, squawks, work orders, aircraft, stage checks, cohorts, and instructor-student pairs all open their own thread off the event that created them, with the right people already in it. You can also create your own channels for a trip or a cost-share.
Can students post in announcements?
No. Posting to the announcement, alert, and news channels requires the broadcast capability, held by admins and chief instructors. Ordinary conversational channels are open to their participants.