Your inbox was never meant to hold the operational record.
Forward the vendor's rate change, the hotel's rooming list, the airline's schedule note: to the program's own address. The AI Inbox classifies it, extracts it, verifies who sent it, and hands you a reviewable draft. The #1 pain in the industry is manual re-entry; this is the painkiller.
How an inbound message becomes a change request
Ingest
Each program has a dedicated inbound address. Forward anything: the mail and its attachments arrive together.
Classify
Manifest, rooming list, vendor quote, vendor change or general, and the sender checked against known contacts.
Extract
Rates, dates, rooms, passengers: pulled into structure with the original text alongside, so verification is one glance.
Review & act
Create the change request with impact pre-filled, or dismiss. Nothing touches the record until you say so.
Parsing is a commodity; landing the result in the right record is not.
Plenty of tools can turn an email into JSON. The AI Inbox works because it sits inside the system that knows your programs, vendors and manifests: a rate change doesn't become “parsed text”, it becomes a draft change request on the right vendor with the cost and charge impact computed. Forward the chaos; confirm the result.
- Known contact verification on every inbound mail
- Cost and charge impact pre-filled on vendor changes
- Inquiries can become draft proposals via RFP Autopilot
- A note posts to program chat when a draft is created
- Included on Growth and Enterprise
AI Inbox questions
What kinds of email does it understand?
The operational mail a program actually receives: flight manifests, rooming lists, vendor quotes and vendor changes, plus general correspondence. Classification decides the type; extraction pulls the structured details, rates, dates, names, occupancy, with the original alongside.
How do you guard against spoofed or malicious mail?
Senders are checked against the program's known contacts: known senders are marked verified, unknown ones are flagged and never trusted by default. Inbound content is treated as data to review, not instructions to follow, and nothing commits to the record without a human.
What happens after review?
You act on the draft: a vendor's rate change becomes a change request with cost and charge impact pre-filled; an inquiry can become a draft proposal. Some rarer types are captured for manual handling rather than auto-routed: the inbox says so honestly when that's the case.
Why per-program addresses?
Because context is the hard part. Mail arriving at the Lisbon program's address is read against the Lisbon program's vendors, services and manifest: which is what lets the extraction land in the right place instead of a generic parse.
See it on your own programs.
A 30-minute walkthrough with the team, on data that looks like yours. Sales-led onboarding: we load your catalog, your vendors and your first programs with you.