How discovery-flight booking works

The discovery flight is your school's front door, and this is the flow the whole system is built around. Here's what happens from the caller's side and yours.

1. 1

   The caller asks to book

   By phone, text, or website chat — it doesn't matter. The Receptionist knows a discovery flight is an intro lesson: first-time flyer, no experience needed, typically 30–60 minutes with a CFI. It answers the obvious pre-booking questions (price, what to bring, weather policy) from the knowledge we loaded at setup.

2. 2

   It offers real openings

   The Receptionist reads your discovery-flight calendar and offers times that are actually free — respecting your availability windows, buffers between flights, and any time you blocked in your own connected calendar. It never double-books.

3. 3

   The booking lands in Calendars

   Open Calendars and the appointment is there with the caller's name, phone, and email. A matching contact exists in Contacts, and a card appears in Opportunities so you can see every prospective student in the pipeline.

4. 4

   Confirmations and reminders go out automatically

   A workflow sends the caller a confirmation text right away and reminders before the flight — the single biggest no-show killer. You can see the exact cadence in Automation → Workflows.

5. 5

   Weather cancel? It handles the rebook

   When you scrub a flight for weather, the contact is already in the system with full context — a quick rebooking conversation replaces the usual phone tag. Move the appointment in Calendars (or tell us), and the follow-up sequence keeps the lead warm.

6. 6

   Watch it once, then trust it

   Do one test booking yourself (call your number, say you want a discovery flight) and watch each piece appear: Conversations entry, calendar appointment, contact, pipeline card, confirmation text. Once you've seen the loop, you can stop checking.