Docs

How BessieAI works

BessieAI captures charter requests in a structured flow — mission type, trip type, routing, and departure timing — then shows a Review Screen before delivery. Every request reaches your team complete, or explicitly marked TBD.

Data captured
  • Mission type — private jet, helicopter, cargo flight, or air ambulance
  • Trip type — one-way, round-trip, or multi-leg
  • Routing — leg-by-leg route (from → to for each leg)
  • Departure timing — local date/time per leg (or marked TBD)
  • Passengers — passenger count
  • Notes — optional constraints and context
  • Contact — email or phone (required before delivery)
Review Screen

Before anything is delivered, BessieAI presents a Review Screen. Mission type and trip type are locked. Routing, dates/times, passengers, notes, and contact can be confirmed and corrected.

  • Locked — mission type, trip type
  • Editable — legs (from/to), departure date/time, passengers, notes, contact
Completeness rule

BessieAI does not guess. If a detail isn’t available, it is explicitly marked as TBD so your team never works with implied assumptions.

Delivery outputs
  • Broker-ready email summary — always included
  • Telegram alert — included
  • SMS alert — optional add-on
  • Request ID — unique reference
  • Status + snapshot — draft → reviewed → delivered
Install

Installation is one copy-paste script tag. Works on WordPress, Webflow/Wix/Squarespace, Shopify, Google Tag Manager, and custom sites. See the installation guide for platform-specific steps and verification.

View installation guide →

Takes a few minutes.

FAQ
Is this just a form?
No. It’s structured intake enforced through a guided flow. Required fields are collected, validated, and normalized, then shown on a Review Screen before delivery.
Is this just an AI chat?
No. The chat is only the interface. The product is structured capture + rules + review + delivery.
What happens if a customer doesn’t know all the details?
Missing information is explicitly marked as TBD. Nothing is guessed or inferred.
Can it handle multi-leg trips?
Yes. Multi-leg itineraries are handled natively and summarized leg-by-leg.
Does every request get delivered by email?
Yes. Email delivery is always included and cannot be disabled.
Are notifications available beyond email?
Yes. Telegram alerts are included. SMS notifications are available as an optional add-on.
How long does installation take?
A few minutes. Installation requires adding a single script tag to your site.
Does this replace my existing process?
No. It sits in front of your inbox and ensures requests arrive complete. Your existing workflow stays unchanged.
What types of flights are supported?
Private jet, helicopter, cargo flight, and air ambulance requests are supported.
Can this be connected to a CRM?
Yes. CRM integration is available by request.
How are time zones handled?
Times are captured as local time for the route and normalized in the summary. If time zone context is unclear, it is flagged as TBD.
What if the customer gives relative dates like “tomorrow morning”?
Relative times (e.g., “tomorrow morning”) are converted into a specific local date/time when possible. If the reference is too vague, BessieAI asks once or marks it as TBD.
What if the customer provides incomplete contact details?
Delivery requires email or phone. If contact details aren’t provided, the request can’t be delivered and stays in Review.