Booking Flights

The flight booking flow walks you through setting search parameters, selecting flights, and confirming the booking. Juno pre-populates dates and airports based on the event, but you have full control to adjust them.

Step 1: Travel Details

The first step is configuring the search parameters:

• Origin airport — Where the guest is flying from
• Trip type — Roundtrip, one-way (outbound or return only), or multi-city if the guest’s policy allows returning to a different destination
• Number of travelers — Defaults to 1
• Departure and return dates — Shown as dropdowns with annotations:
  • ✦ Recommended — Dates that fall within the guest’s travel window
  • ⚠ Requires approval — Dates outside that window, which will need approval

The travel window is set by the guest’s travel policy. Depending on how it’s configured, Juno either calculates the window around the event — optionally allowing extra shoulder nights — or applies custom rules based on how long the guest’s outbound flight takes. Recommended and approval-required dates reflect whichever method the policy uses.

Cabin is no longer chosen here — the guest’s cabin is selected when comparing options on the results page (see Step 2: Select Flights).

The destination starts at the event location, with its airports pre-populated. If the guest needs to fly somewhere else — for example, a nearby city or a different airport — type another city or airport in the destination field. Choosing a city includes all of its airports. On return-only and multi-city trips, the same destination is also where the return flight departs. Clear the field to go back to the event location and its airports.

Open Search settings to view or adjust which destination airports are included, and to turn on Refundable fares only to limit results to refundable fares.

After you book a flight to a different destination, later flight searches for that guest start from that destination, and the guest sees it in their flight search. Changing the flight destination doesn’t change the event location: event-based timing policy, recommended dates, and hotel search still use the event.

Once you’re satisfied with the parameters, continue to search for flights.

Step 2: Select Flights

The results page shows available flights organized into two sections:

• Juno Picks — AI-curated recommendations based on the guest’s travel preferences and policy
• Other — All other available options

You can filter and sort results to find the right option.

If the guest’s applicable travel policy changes during an active search, Juno can refresh the flight results automatically. Review the refreshed options and select flights again if prompted before confirming for the guest. If results expire and do not refresh automatically, start a new search.

Because Juno searches every cabin at once, results include a cabin comparison matrix spanning Economy, Premium Economy, Business, and First. Filter by cabin to compare the options in each, then make a per-cabin selection in the cabin you want for the guest.

Cabin options that do not meet the guest’s travel policy are flagged with an Out of policy or Not allowed badge. Open a cabin option to see its details, where hovering over or tapping the policy badge reveals the reason — such as a cabin restriction or a price above the policy limit.

If the guest’s policy sets an advance-booking window, flights departing fewer than the required number of days away are labeled Booking too close to departure. Depending on the policy’s enforcement, the selection shows a warning or is treated as out of policy. An out-of-policy selection follows the approval flow in Policy and Approval: if you are the approver, you approve and book it immediately; otherwise it becomes a Request to Book and appears under Needs Review with the timing as the reason.

The Latest available option in this search notice identifies the latest departure Juno returned for that route and date. It is based on the current search results, not the airline’s complete schedule. Depending on the guest’s policy, Juno either recommends an earlier flight or requires approval; when approval is required, the option remains selectable and follows the existing Request to Book flow.

Refundable Alternatives

A non-refundable selection may be marked Out of policy when a comparable, fully refundable alternative without a cancellation penalty is available within the guest’s policy allowance and meets all other policy requirements. The selection remains available and follows the existing approval flow described in Policy and Approval. Juno does not switch fares automatically.

For round trips, Refundability check pending return selection is an informational notice until both directions are selected. The definitive approval result applies to the complete itinerary.

The Refundable fares only search setting limits the fares you see; it is separate from the policy comparison. If your organization permits trip exceptions for Refundable fares, you can set an allowance for the trip even when none is inherited, increase or decrease the amount, change the currency, turn the allowance off, or revert the trip-specific allowance.

Turning the allowance off stops this approval comparison for the trip. Reverting removes your trip-specific allowance and restores the inherited policy setting, which may be enabled or off. A zero allowance keeps the comparison enabled; it does not turn the rule off. Other policy requirements still apply.

Select the outbound and return flights (or just outbound for one-way trips). Once all required flights are selected, Juno automatically advances to the confirmation step.

Step 3: Confirm the Booking

The confirmation step shows your selected flights alongside a pricing summary. Before confirming, review:

• Traveler profiles — Select which traveler profile(s) to attach to the booking. If the guest hasn’t submitted their profile yet, you’ll see an option to request it. See Requesting Traveler Details for more.
• Custom onboarding fields — Any trip-specific fields required by your organization
• Internal notes — An optional memo field for notes about this booking

Policy and Approval

The confirm button reflects the policy status of your selection:

When a selection requires approval, the notes field becomes required — you’ll need to provide a reason for the out-of-policy request.

Step 4: Confirmation

After submitting, Juno processes the booking and shows the result:

• Confirmed — The flight is booked. The guest receives a confirmation email with their itinerary.
• Needs Review — The booking requires approval. You and the approver are notified by email.
• Sold Out — The selected flight is no longer available. You’ll be sent back to the selection step to choose another.
• Denied — The approval request was not approved. Return to the selection step to choose an alternative.

If an approved flight’s fare increases during checkout and Juno receives a confirmed current total, Juno returns the booking to Needs Review so the approver can review the new total before another booking attempt. Approving the new total doesn’t confirm the booking. Once it’s approved, Juno tries the booking again automatically. If the flight hasn’t changed, Juno uses the approved fare as the most it will pay, so the flight is never booked at a higher fare. Separately priced seats are charged on top of the fare, so the booked total can be higher than the approved fare. If the fare is still above the approved amount, the booking doesn’t go through and can return to Needs Review.

When the guest selected flights on separate tickets and that fare expires, the booking isn’t necessarily Sold Out. If the same flights can still be booked on one ticket, Juno continues with that ticket. Checkout confirms the fare, and a higher total returns to Needs Review.

If the guest also needs a hotel and it hasn’t been booked yet, the confirmation page shows a Book a Hotel option to continue. Otherwise, use Return to Dashboard to go back to the guest’s detail page.