Call your agency at 11:40 PM in booking season. Voicemail? The AI answers in one ring, checks availability on the Saturday wine tour, books two seats and sends the confirmation — in the caller’s language.

A group organizer asks for 42 seats, two coaches and a guide in May: the AI prices it from your real catalog and sends a quote with a payable link — the yes arrives with the payment.

Meeting point, what to pack, is lunch included, rain policy, visa notes: answered instantly and identically, from YOUR approved knowledge — and when there is no source, the AI says so instead of inventing.

Departure manifest recaps, supplier confirmation checks, end-of-season reports — assigned to the AI like to an ops coordinator, executed on schedule, fully auditable.

“What does the coach contract say about cancellation inside 72 hours?” — answered in seconds with the clause cited, instead of twenty minutes of PDF scrolling before you call the supplier.

Every AI-drafted manifest, recap and supplier letter lands in Output awaiting review. Nothing reaches a guide, a coach company or a traveler without a human decision.

Scanned coach contracts, brochure PDFs, spreadsheet manifests, photographed waivers, supplier emails — the ingestion pipeline turns what a tour operator actually receives into queryable knowledge.

No source in your library, no claim: the AI cites the contract clause, the itinerary page, the insurance certificate — or says it cannot answer. Nothing is improvised about a departure.

A freelance guide asks about the meeting point and the route notes; the finance lead asks about supplier payment terms: each gets answers scoped to their role, enforced server-side.

Manifest recap, supplier confirmation check, itinerary comparison, season report: work types molded to your operation, with default libraries and examples per type.

The AI’s workload is managed like the team’s: one-click views show what is urgent, late, today and tomorrow — in peak season, nothing slips silently.

Reasoning streamed, sources cited, milestones tracked, linked to the departure and the calendar — an ops file you can audit after the season closes.

The kayak-tour safety briefing, the mountain weather cancellation rule, the coach breakdown procedure, the lost-child protocol: one library, current versions on top, superseded drafts outranked.

“What is the wind limit for the catamaran tour?” — asked by a guide at the marina at 6 AM, answered in seconds with the briefing attached, without waking the ops manager.

Work types carry their default SOPs: the AI drafting a departure recap reads from the current safety briefing and cancellation policy — by construction.

Ten seasonal hires in one week learn your booking rules, route knowledge, phone scripts and refund policy through guided AI training — ramp-up in days, before the first May departure.

“How do I rebook a rained-out kayak tour?” — asked to the assistant, answered from the current SOP with the source attached, without pulling the ops manager off the phones in peak season.

Private chats work on any device with a login — the how-to knowledge follows the guide to the marina, the coach park or the ticket booth.

The moment a booking is confirmed, the AI drafts the pre-trip email — meeting point, what to pack, weather notes for the week — in the traveler’s language, queued for approval.

Two days before each departure, the manifest is checked: unconfirmed coach, unsigned waivers, headcount below minimum — flagged to the ops manager while there is still time to act.

The evening after the tour, a thank-you with a review request goes out in the traveler’s language — drafted from the actual itinerary they took, by your approval rules.

Meeting point, what to pack, weather outlook, arrival tips: sent days before each departure, in the traveler’s language — fewer 7 AM phone calls, fewer no-shows at the coach.

The review request lands the evening after the tour, mentioning the actual route they took — asked once, politely, with opt-outs enforced by the system, not by memory.

“Everyone who booked the Iceland tour two seasons ago” gets the new northern-lights departure first — audiences built from your own booking records, no list exported to a third-party tool.

Bookings, availability and traveler records mapped field by field, with a dry-run preview before anything writes — push, pull or two-way, your choice.

Your channel manager keeps distributing inventory exactly as it does today; Zanus reads the resulting bookings so quotes, manifests and pre-trip emails always reflect reality.

A full API for whatever else the operation runs: ticketing at the attraction gate, waiver tools, accounting — data in, results out, under scoped keys.

Your isolated private tenant trains no outside models — and for DMOs and operators under strict residency rules, the on-premises option keeps traveler data physically in-country, air-gap capable.

Payable links hand the transaction to your payment processor — card data lives there, not in Zanus. The AI closes the sale without ever holding the card.

School-trip rosters carry children’s data: field-level permissions and server-side redaction mean a driver sees a headcount, not birth dates — only authorized roles see the full roster.

Ask the chat: “two seats on a Saturday wine tour next month” — watch it qualify, offer real dates and confirm like your best agent in booking season.

Ask: “how would you draft Friday’s departure manifest recap?” — it walks the workflow it would run in your tenant, grounded, cited, sign-off included.

The full demo loads a travel tenant with a sample catalog: group quotes, manifest recaps, pre-trip emails — your season, working.