You can also browse, search and filter all release notes directly in the application → Open release notes in TAI.
Reports and chats can now deliver Excel and Word files
Major New Feature.
Ask for it in a report's requirements or straight in a chat — "give me an Excel export of the top destinations" — and you get a real .xlsx or .docx: listed as a download on the report, and attached to every scheduled email of it, exactly like the CSV.
Excel gets the data as data: numbers stay numbers, so the columns still sum, sort, and chart when you open them — and you can ask for several sheets in one workbook. Word gets headings, paragraphs, bullets and tables, ready to edit and send on.
Nothing new to switch on, and no format setting to hunt for: the prompt still decides. Ask for one format or all of them — CSV is unchanged and still the leanest extract, and an HTML report still carries its one-click PDF.
One ask, every format: Excel and Word alongside the CSV and the HTML report's PDF — each one its own download.
Reports can now deliver CSV data, not just a document
Major New Feature.
Ask for a CSV in a report's prompt and you get one: it's listed as a download on the report, and attached to every scheduled email of it. Handy for allotment and analytics extracts you want to open in a spreadsheet or feed into another system.
There's no CSV setting to find — the prompt decides. That's on purpose: it also means the prompt decides what the file looks like (which columns, whether an amount and its currency are split), which no dropdown could express. An image the report produces rides along the same way.
Attach PDF is unchanged and still yours to set; it now says Attach the report as PDF, because it only ever governed the report document. Data files ride along either way, so you can send a PDF summary with its CSV data, or just the CSV.
Ask for a CSV in the report's requirements — there is no CSV setting to find.
The scheduled email lists and attaches every file the report produced.
Built-in report agents: one clear input instead of three
Improvement.
Launching a report on one of the built-in report agents — Itinerary Checker, TripBuilder Ops & BI Agent, or Passolution Agent — now asks for one thing, Report requirements, and explains what it accepts right on the form. Custom agents' report forms are unchanged.
Write whatever fits: general reporting requirements, the data period to look at, or simply a booking or itinerary reference. The agent reads it alongside its own instructions and skills.
No more guessing which of three fields a booking reference belonged in — they did the same job.
Your own agents can do this too: every report input parameter now takes an optional description, shown above the field when the report is launched or scheduled. Enabling the Report channel starts you off with a ready-made Report requirements field you can keep, edit, or replace.
Your saved schedules carry over — anything you had entered in the old fields is merged into the new one, so they keep running untouched.
Faster, more consistent itinerary checks
Improvement.
Checks run faster and score the same booking the same way run to run, and a review of a past trip now reads as a reconciliation rather than expired deadlines. Two new catches: a night in your travel dates with no accommodation booked, and dead time at either end of a stay — a dawn landing hours before check-in, or a checkout hours before a late-night flight. It also stops guessing at seasonal closures, local holidays, and opening hours, which it had no live source for.