How it works

The day runs. Nobody had to fix it.

Your booking system handles the sale. TourOperate makes sure every departure has its guide, its vehicle, its tickets and its details, and tells you the moment one of them is missing.

01 · The booking

Bookings arrive, in TourOperate a second later.

  • Product, time and passengers arrive on their own
  • Your booking system stays exactly as it is
  • No confirmation email to open or file
  • Nothing typed in twice
02 · The departure

Bookings stop being a list and join the departure they belong to.

  • Five bookings on the same 10:15 become one departure
  • Guide, vehicle, tickets and meeting point attached to it
  • Passenger requirements stay with the passenger
  • Set up once per product, not once per rate
03 · The gaps

Every important detail, for all your services, under control.

  • No guide on the 10:15, and you know at 07:12
  • Not in a phone call at 10:05
  • Missing tickets, missing pickup, missing passenger detail
  • Nothing counts as ready until it truly is
04 · The answer

When only the passenger has the missing detail, we ask them for it.

  • One short form for that one detail
  • No account to create, nothing else exposed
  • The link expires on its own
  • The answer arrives and the gap closes itself
05 · The day plan

Each guide and each driver gets tomorrow, in order.

  • One plan per person, not one message per booking
  • In sequence, with everything they need to run it
  • Marked as sent, so you know it left and when
  • A change reopens the departure and shows what moved
Capabilities

What you can run today.

The capabilities available today. Open a card to see why each one exists and where it draws the line.

  1. Your morning on the Today screen

    One screen shows every real departure and puts the problems first.

    1. No guide on the 10:15
    2. Assign a guide
    3. Staffed, day sheet ready
    Why it exists

    Coordinators cannot run 200 bookings by opening one booking at a time. They need to see the actual departures that must be staffed, ticketed, checked, and communicated.

    Limit: Day one has a shared flat view for a small operations team. Advanced coordinator claiming and collision handling come later.

  2. The departure everyone is preparing

    One actual tour or transfer at one resolved time.

    1. Five loose bookings
    2. They join one departure
    3. 30 passengers, one plan
    Why it exists

    Bookings, guides, tickets, passenger details, and sends need one shared operational home.

    Limit: Until availability-based pre-creation exists, a zero-booking departure cannot be planned. Ambiguous Profile matching becomes Attention, never a guess.

  3. The tour recipe and its variations

    Product stores the normal setup; Profile stores only the real operational differences.

    1. Many near-identical setups
    2. One product, one profile
    3. Changes land everywhere
    Why it exists

    Thirty products with eight rates must not become 240 copied configuration pages.

    Limit: An Operating Profile is not a copied provider rate. Provider IDs stay in External References rather than becoming internal identity.

  4. Where the tour happens

    Shared locations connect products, departures, and resource coverage.

    1. Three spellings, one place
    2. Merged into a Location
    3. Coverage attached
    Why it exists

    Without first-class Locations, every later screen quietly assumes one city or relies on inconsistent free text.

    Limit: Day one uses coarse coverage areas. It does not calculate traffic or prove that two far-apart assignments are physically possible.

  5. Which venue tickets are needed

    Ticket Type is the venue or package; categories are its tiers.

    1. Ticket type needed
    2. Matched by category
    3. Ready for the departure
    Why it exists

    A provider passenger category such as Adult does not automatically prove which exact venue ticket tier that person needs.

    Limit: Supplier stock, automatic ticket purchasing, and venue submission are later, or blocked by external capability evidence.

  6. Send each person one useful daily plan

    Every resource receives one ordered day sheet, not one message per booking.

    1. Day plan not sent
    2. Sent to guide and driver
    3. Marked Sent
    Why it exists

    A guide with three departures should not reconstruct their day from scattered booking emails and chat messages.

    Limit: Messaging apps, resource sign-in, delivery receipts, and automatic resend are later. The coordinator stays in control.

This page lists only the capabilities available today.