Adoption · June 2026

The integration is a forwarding address

Ask a Part 135 operator to rip out the systems their dispatch desk already runs and you’ve lost the deal before the demo. The lightest integration wins. Ours is a forwarding address.

Forward the email, get a trip

Charter requests already arrive as email — an Avinode marketplace lead, a broker chain, a direct note from a client. Forward that message to your Readback inbound address and it becomes a structured trip card: origin, destination, dates, passengers, notes — ready to quote.

Inbound email to compliant quote — the only setup is a forwarding rule.

Confidence, then a human

Parsing real-world email is messy, so we don’t pretend it’s perfect. Anything the extractor isn’t at least 70% sure of is flagged for a person to confirm before it moves forward. A wrong tail number or a transposed date is worse than a slow one — the threshold is there on purpose.

The fanciest integration we could build would still lose to the one that’s already running: the inbox.

Meet the workflow where it is

No new app to learn, no data migration, no API project on the operator’s side. The work already lands in an inbox — so that’s where we plugged in.

Readback — charter quoting with the compliance gate built in

Forward a charter request; get a compliant, formula-annotated quote — but only if the assigned crew is legal.

See the product →Free tools More posts