These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Bus / Coach Management
- Features
- Booking desk
Booking desk
Give each charter or scheduled booking a clear owner, service window and next action.
OverviewMy bookings×
Bus / Coach Management · Booking desk
New
My bookings
Bookings
| Record number | Subject | Customer name | Starts at | Ends at | Status | |
|---|---|---|---|---|---|---|
| BKN-13599 | Requested bkn-257 | Customer 525 | 05 Oct | 13 Oct | Requested | |
| BKN-86722 | Held bkn-825 | Customer 705 | 05 Oct | 08 Oct | Held | |
| BKN-86503 | Confirmed bkn-554 | Customer 405 | 08 Oct | 16 Oct | Confirmed | |
| BKN-62721 | In progress bkn-395 | Customer 932 | 18 Oct | 25 Oct | In progress | |
| BKN-94980 | Completed bkn-533 | Customer 705 | 19 Oct | 24 Oct | Completed |
6 of 6 records
Requested bkn-257Bookings · BKN-13599
RequestedCustomer nameCustomer 525
Starts at05 Oct
Ends at13 Oct
Revision670
Quoted amount USD270
What you can do
Start with a booking the operating team can use
The Booking Coordinator records what the customer has requested and when the service is expected to run. The booking brings together the customer name, subject, carrier organization and accountable owner. A quoted amount in USD gives the commercial discussion a recorded reference while the operating team arranges the service.
Requested, Held and Confirmed bookings represent different points in that conversation. The coordinator can hold a request while the Dispatcher checks the resources and then confirm the agreed booking arrangements. The booking continues to provide the common reference for its departures, supporting files and later operating outcome.
How the work is organized
- Customer context. The subject explains the intended service in terms the Dispatcher can recognize. Keep the customer name and quoted amount with the booking so a change of owner does not require the next person to reconstruct the conversation from memory.
- Service window. Start and end dates describe the booking’s operating window. The assigned owner reviews that window alongside dispatch arrangements. A departure time belongs to its departure record and should be checked against the booking when plans change.
- Accountable follow-up. The owner keeps the booking state current as arrangements progress. Supporting files carry their title, evidence type and visibility, giving the next person a place to find the information relevant to a customer query or an operating review.
What to agree during setup
Agree how booking numbers and subjects are written, especially when a customer requests several similar journeys. Identify the Booking Coordinator responsible for each carrier organization and explain when a request should become Held or Confirmed. Confirm the time zone used by the organization and the people entering service dates.
Decide how quoted USD amounts are maintained when a customer changes the request. Keep the commercial conversation separate from the provider payment events that finance later reconciles. Establish which supporting documents can be shared and who checks them before their visibility changes.
Check the handoff on an actual case
A customer asks for a coach for an afternoon group visit. The Booking Coordinator records the service subject, customer, planned start and end, and quoted amount. The request moves to Held while the Dispatcher reviews the intended coach and staffing arrangements.
Open the booking schedule together and check the service window. The Dispatcher prepares resource lines and a departure linked to this booking. When the booking arrangements are accepted, the coordinator records Confirmed and directs the departure to its independent review. The two people should be able to identify the same customer request without relying on a similar subject or a separate note.
Repeat the case with a changed return time. Check the booking revision and revisit the departure and reservation details affected by the change. Keep the revised customer information attached to the same booking so the reviewer can understand the current plan. Finally, rehearse a cancellation and identify who tells dispatch and who checks any payment evidence requiring follow-up.
What your team sees
- My bookings — The current owner’s bookings with customer details, service windows and commercial reference.
- Booking pipeline — Requested, held, confirmed and active service work grouped by state.
- Booking schedule — Booking windows that the coordinator and Dispatcher review together before making arrangements.
Follow the work through
Continue with booking and reservations and departure review and release.
What it keeps track of
Data model- Bookings
- Charter and scheduled booking records with reserved resources
- Organizations
- Carrier organizations operating the coach network
- Team members
- Authenticated platform identities attached to an organization
- Resources
- Coaches, drivers and partner operators allocated to bookings
- Record attachments
- Supporting files attached to bookings and departures
Who uses it
Permissions- Booking Coordinator
- , Dispatcher, Operations Manager.
- The coordinator owns customer follow-up, the Dispatcher prepares operating arrangements and the manager reviews the outcome.
Set up Bus / Coach Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.