The Unified Reservation Timeline

Open any reservation in Vanio and you see one screen — one chronological feed — with everything that has ever happened on that booking. Guest messages from every channel. Internal team chat. AI conversations. Workflow runs. Access code generations. Smart lock events. Payment events. Calendar changes. Alteration requests. Task assignments and completions. Review activity. Noise alerts. Portal activity. The full Vanio AI reasoning trace inside the AI Lab.

In every other tool you've used, this same context lives in 8 different places: a messaging tab on Airbnb, a separate inbox on Booking.com, a third inbox on VRBO, your team's Slack channel, your accounting platform's payment log, your smart lock app, your task scheduler, your calendar tool. Switching between them is the job. Reconstructing what happened is the job.

In Vanio, the reservation IS the job. Open it once, and the whole story is in front of you in chronological order — sortable, filterable, searchable, and replyable from the same screen.

Quick reference: Unified inbox, single timeline, reservation timeline, all-in-one reservation, dashboard reservation modal, reservation context, full reservation history, message timeline, channel-agnostic inbox, omnichannel inbox, every channel one inbox, internal notes on reservation, AI on reservation, workflow on reservation, smart lock on reservation, payment on reservation, single source of truth — open any reservation in the dashboard and look at the unified timeline.

Getting started

To open any reservation's unified timeline:

1. Go to your Dashboard in Vanio
2. Click any reservation card or row to open the reservation modal
3. The unified timeline loads automatically in the center panel

Performance improvements: Recent updates have made opening reservation details significantly faster, especially when multiple team members are using Vanio simultaneously. Timeline data now loads more reliably under heavy usage.

[Screenshot: Dashboard with reservation cards showing click-to-open action]

Understanding inquiries vs. bookings

Inquiry display improvements: When viewing inquiries (potential bookings that haven't been confirmed yet), the financial summary section now displays 'N/A' instead of '$0.00' or blank fields. This makes it immediately clear that financial information isn't applicable until a booking is confirmed.

What you'll see:

• Confirmed reservations — Full financial breakdown with actual amounts
• Inquiries — 'N/A' in financial fields, indicating the inquiry stage
• Timeline clarity — The reservation status and financial display now align perfectly to show exactly where each booking stands in the lifecycle

This change eliminates confusion between inquiries with no financial data and confirmed bookings that happen to have zero-dollar amounts (like comp stays or promotional bookings).

[Screenshot: Inquiry financial summary showing N/A values vs confirmed reservation showing actual amounts]

What lives on the timeline

A single reservation timeline shows every one of these in chronological order, threaded together as one story:

Messages — every channel, one feed

• Guest messages from Airbnb, Booking.com, VRBO, WhatsApp, SMS, email, your direct booking website portal, plus WhatsApp Business and Twilio SMS for direct conversations
• Host messages sent through any of those channels, with the channel auto-routed based on which channel the guest is on
• Internal team messages — notes between you and your staff that the guest never sees
• AI messages — every reply Vanio AI has sent to the guest, with the full reasoning trace if you want to see why it said what it said
• Email threads rendered inline with attachments and reply threading

You can switch channels mid-conversation. A guest asks a question on Airbnb, you reply on Airbnb. Two hours later they text you on the property's phone number — same reservation, same timeline, same context. The AI knows they're the same person and threads the SMS conversation into the same timeline as the Airbnb messages.

Internal notes

A separate visual lane for messages your team writes to each other about the reservation. The guest never sees these. Use it to flag a difficult guest for the next shift, leave a note for the cleaner, or document a damage claim before submitting it. They're searchable, taggable, and stored alongside the guest-facing messages so context is never lost.

Reservation lifecycle events

• New reservation created
• Inquiry received (shows with N/A financial summary until confirmed)
• Reservation accepted / declined
• Reservation confirmed
• Reservation modified (alteration request, dates change, guest count change, price change)
• Reservation cancelled (by guest, by host, or by channel)
• Reservation marked as no-show
• Move to a different listing
• Reservation completed (after checkout)

Each event shows up as a single line in the timeline with a timestamp, the actor (you, a teammate, the guest, the AI, or the channel itself), and a one-line description. Click for full details.

AI events and reasoning

• Every AI auto-reply, with the message itself plus the full thinking trace and the knowledge-base sources the AI used
• AI workflow runs — what triggered, what fired, what tools were called
• AI escalations — when the AI hit a situation outside its skill set and flagged it for human review
• AI procedure executions — multi-step skills like "early check-in flow" running across the reservation
• AI suggestions waiting for approval (Shadow Mode)
• Voice calls — the AI handled an inbound call about this reservation, with the transcript right there in the timeline

Workflow / automation events

Every workflow that fired against this reservation logs a line in the timeline showing which workflow ran, which actions it took, whether each succeeded, and which conditions triggered it. If a workflow auto-charged the security deposit, the timeline shows it. If a workflow sent the welcome message at 2pm before check-in, the timeline shows it. If something failed, the failure shows up too with the error and a retry button.

Tasks

• Cleaning task created when the reservation was accepted
• Task assigned to a specific cleaner
• Cleaner accepted via SMS
• Photos uploaded by the cleaner
• Quality check status
• Task marked complete
• Maintenance request raised mid-stay
• Inspection scheduled

Every task event lives on the reservation timeline AND in the global task list — they're the same data, just viewed differently.

Smart lock activity

• Access code generated for the reservation
• Code activated at check-in
• Door unlocked (with timestamp and which device)
• Door locked
• Code timing updated (e.g. early check-in approved, code activation moved up)
• Code deactivated after checkout
• Lock connectivity issues, battery alerts, code-entry failures

For multi-device properties, every event from every lock attached to the reservation flows through this same timeline.

Payment events

• Initial charge at booking
• Pre-authorization for security deposit
• Scheduled future payments (split bookings, deposits due before check-in)
• Successful charges, failed charges, retries
• Refunds — partial, full, with reason and the user who triggered them
• Damage claim charges
• Deposit captured / deposit released
• Payout deposited

Note: For inquiries, payment information shows as 'N/A' until the booking is confirmed, making the financial timeline clearer.

Calendar / pricing events

• Date held when the reservation was created
• Per-date overrides applied via the calendar
• Price changes (manual or via dynamic pricing)
• Calendar block events that affect this reservation's range

Reviews

• Review request sent to the guest
• Review received (when it lands)
• AI-drafted response shown for approval
• Response posted back to the channel
• AI review analysis (severity, issues, action items)

Issues

• Noise alerts from connected sensors
• Climate control anomalies
• Lock issues
• Verification failures
• Anything the operations watchdog flags

Portal activity

• Guest accessed the portal
• Guest completed verification (ID upload, signature)
• Guest accepted house rules
• Guest purchased an upsell (early check-in, late checkout, parking)
• Guest viewed a knowledge base article

How it works

Automatic timeline loading: When you click any reservation, Vanio automatically pulls together all events from every connected service — messages, payments, smart locks, tasks, AI actions — and sorts them chronologically. This happens in real-time, so the timeline is always current.

Multi-team reliability: Recent performance improvements ensure the timeline loads quickly and reliably even when multiple team members are accessing reservation details simultaneously. The system now handles high-usage periods more efficiently.

Smart threading: Related events automatically group together. A guest message, your reply, and the AI's follow-up message appear as a threaded conversation. A cleaning task creation, assignment, and completion show as connected events.

Inquiry vs. booking clarity: The system automatically detects whether you're viewing an inquiry or confirmed booking and adjusts the financial display accordingly. Inquiries show 'N/A' for financial fields, while confirmed bookings show actual amounts, eliminating any confusion about the booking status.

Live updates: If something new happens while you have a reservation open — a guest sends a message, a payment processes, a door unlocks — it appears on the timeline automatically without refreshing.

Reservation Codes panel

To the side of the timeline, the Access Codes panel shows every active code for the reservation — door codes, gate codes, wifi password, parking codes, anything attached to the property. Generate a new code, edit timing, deactivate, or push to the guest's portal — all without leaving the modal.

AI Lab — test what the AI would say

Every reservation modal includes an AI Lab panel where you can test how Vanio AI would respond to a hypothetical guest message in this exact reservation's context. You type a message as if you were the guest. The AI replies using the full context: this reservation, this guest's history, this property's knowledge base, this listing's check-in time, this stay's smart lock state, the cleaning status, everything.

This is how you tune the AI:

• Test edge cases before they happen ("what if the guest asks for a 6am check-in?")
• See what knowledge base articles the AI is pulling from
• Verify the AI knows about a specific house rule before going live
• Run the AI in voice mode — test as a phone call instead of a chat

The Lab uses the same context layer as the live AI, so what works in the Lab works in production. What doesn't work in the Lab tells you exactly what to add to the knowledge base or AI Skills.

Key features

• Single source of truth — Every event, message, and action for a reservation in one chronological view • Fast loading — Optimized performance for quick access to reservation details, especially under heavy team usage • Clear inquiry handling — Inquiries display 'N/A' for financial information instead of confusing zero amounts • Real-time updates — New events appear automatically without refreshing • Smart filtering — Show only messages, only tasks, only AI events, or any combination • Full-text search — Find any word across messages, events, notes, and AI reasoning • Thread grouping — Related events automatically cluster together for easier reading • Channel switching — Reply to guests on any channel from the same timeline • AI reasoning traces — Click any AI message to see exactly why it said what it said • Access code management — Generate, edit, and share property codes without leaving the reservation • AI testing lab — Test hypothetical scenarios with full reservation context • Export capability — Generate complete timeline reports for disputes or audits

Why this is a massive advantage

Every other tool in the vacation rental space treats reservations as a row in a database. Vanio treats reservations as a story. The difference shows up in how you actually work:

"Why did the AI tell the guest the WiFi was 'GuestNetwork-2024'?"

In Vanio: open the reservation → scroll to the AI message → click the message → see the exact knowledge base article it pulled, the exact context it had, the exact reasoning. 30 seconds.

In a traditional PMS: log into the AI tool, find the conversation, find the message, hope the AI tool stores reasoning, switch to the property knowledge base, search for the WiFi entry, manually compare. Maybe 10 minutes if you're fast.

"Did anyone tell the cleaner about the late checkout I approved?"

In Vanio: open the reservation → see the late checkout approval, the calendar change, the task update auto-rescheduling the cleaning, the SMS that auto-fired to the cleaner saying "checkout moved to 1pm", the cleaner's reply confirming. Top to bottom in 5 seconds.

In a traditional PMS: check the messaging tool to see if the late checkout was approved, check the calendar tool to see if the dates updated, check the task tool to see if the cleaning was rescheduled, log into your team Slack to see if anyone messaged the cleaner, ask the cleaner directly because you can't tell. Easily 15 minutes plus a phone call.

"A guest claims the door wasn't working at check-in. Was it actually broken?"

In Vanio: open the reservation → see the lock event timeline → "code attempted at 14:32, success", "door unlocked at 14:33", "door locked at 14:35", "code attempted at 14:42, success", "door unlocked at 14:42". Plus the AI message thread showing the guest never asked about it during the stay. Resolved in 60 seconds.

In a traditional PMS: log into the lock vendor's app, find the device, find the date, scroll lock events, screenshot them, paste them into the messaging tool. 10 minutes. And if your lock vendor doesn't expose detailed events at all, you have no answer.

"Show me everything that happened on this reservation before I refund the guest."

In Vanio: open the modal, that's the screen.

In a traditional PMS: it's a 30-minute reconstruction project.

"Is this an inquiry or a confirmed booking?"

In Vanio: open the reservation → financial summary shows either actual amounts (confirmed) or 'N/A' (inquiry). Instantly clear.

In a traditional PMS: check the booking status field, cross-reference with payment status, maybe check multiple tabs to understand what stage you're looking at.

Filters and search

The timeline has built-in filters across the top so you can scope the view:

• Messages only — just the guest/host/AI/internal conversation
• Events only — just lifecycle, payments, tasks, locks, no messages
• Tasks — cleaning, maintenance, inspection events only
• Issues — flagged problems only
• Automations — workflow runs only

Plus a search bar that searches across the entire timeline — message bodies, event metadata, payment reasons, task notes, AI reasoning. Type any word and find every place it appears in the reservation's history.

Tips & best practices

For faster timeline navigation: • Use filters to focus on specific event types when troubleshooting • Bookmark frequently-accessed reservations for one-click access • Use the search function to jump directly to specific conversations or events

For team collaboration: • Add internal notes for context that needs to persist between shifts • Use @mentions in internal notes to notify specific team members • Export timeline reports for complex disputes or insurance claims

For AI optimization: • Test edge cases in the AI Lab before they happen in real conversations • Click AI reasoning traces to understand and improve knowledge base articles • Use the Lab's voice mode to test phone call scenarios

For inquiry management: • Look for 'N/A' in financial summaries to quickly identify inquiries vs confirmed bookings • Use the clear visual distinction to prioritize follow-up on pending inquiries • Filter timelines to focus on inquiry-to-booking conversion events

Common questions

How fast does the timeline load for large reservations with lots of history? Recent performance improvements have significantly reduced loading times, especially when multiple team members are accessing reservations simultaneously. Most timelines load within 2-3 seconds regardless of the amount of history.

Can I export the entire timeline for legal or insurance purposes? Yes. Click the export button at the top of any reservation timeline to generate a complete chronological report with all messages, events, timestamps, and actor attribution. The export includes AI reasoning traces and internal notes for complete documentation.

What happens if I'm looking at a reservation and something new occurs (guest messages, payment processes, etc.)? New events appear automatically on the timeline without needing to refresh. The system updates in real-time, so you'll see guest messages, payment confirmations, smart lock events, and AI responses as they happen.

Why do some reservations show 'N/A' in the financial summary? This indicates you're looking at an inquiry rather than a confirmed booking. The 'N/A' display makes it immediately clear that financial information isn't applicable until the booking is confirmed, eliminating confusion with zero-dollar confirmed bookings like comp stays.