Operator portal · book by tour (corrected model)
The operator books like a customer books an excursion online: pick the tour, see which dates have seats, choose a day, party size, done. The tourist is already on the island and wants a specific tour, so it's tour-first, not hotel-first (hotel is the office's dispatch concern). Step through it. Mobile-first.
Operator view vs manager view (different jobs)
Operator = sales / booking
- Organized by tour. Browse tours → availability → book.
- Same as a consumer booking an excursion online (Viator / GetYourGuide / Turitop widget).
- Cares about: which tour, what dates, how many seats left, the price.
- Hotel/pickup is a minor optional detail, defaulted.
Manager = operations / dispatch
- Organized by day. The daily board: who's on which bus.
- Cares about: guides, vehicles, pickups by hotel, the manifest.
- This is where hotel-first makes sense, it's dispatch.
The differentiation vs Turitop isn't this booking UX (match it, it's what everyone expects), it's the operations layer behind it. So make the operator side feel like the familiar consumer booking, and win on the manager/dispatch side.