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.

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
• 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

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

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.

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.

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.

Why this is technically possible (and why competitors can't catch up easily)

Vanio is built on a single unified reservation context that every subsystem reads from and writes to. Messages, payments, tasks, locks, AI, workflows, calendar, portal — they don't have their own siloed databases. They all live alongside the reservation as events on a shared timeline.

Most other tools in this space were built in pieces. The PMS came first, then a messaging tool was bolted on, then an AI add-on, then a tasks integration, then a lock integration, then a payments integration. Each piece has its own data model, its own UI, its own user account. Stitching them into a single chronological view is impossible without rewriting the foundation.

We built the foundation that way from day one. That's why a guest message and a smart lock event and an AI reply and a payment event can all sit next to each other on the same timeline with consistent metadata and full search.

What this enables

Because everything is on one timeline:

1. The AI is smarter — it has full reservation context, not just the message history. When a guest asks about their stay, the AI knows the lock state, the cleaning status, the payment history, the past messages, the current calendar — all from the same context layer.
2. Workflows are smarter — they can trigger off any event type. "When a noise alert fires AND the reservation is in mid-stay AND there's an unresolved guest complaint in the last 24 hours, escalate to the host on Slack." Try that across 5 separate tools.
3. Audit trails are complete — every action by every actor (human, AI, channel, system) is logged in one place with attribution. Zero guesswork about who did what when.
4. Onboarding new staff is faster — they don't learn 8 tools, they learn one screen. The reservation modal IS the job.
5. AI training improves continuously — every interaction is paired with its outcome on the same timeline, so Vanio can learn from what worked and what didn't without manual data labeling.

Common scenarios

"I'm reviewing a refund decision and I need every detail." Open the reservation. Scroll. Everything is there: the original booking, every guest message, every house rule acknowledgment, every payment, every problem flagged, every conversation with the cleaner, every AI reply, every workflow run. The full story, in order, in 60 seconds.

"My team manages 200 properties and I need everyone to see the same context on every reservation." Open the reservation. Whoever's looking at it sees the same timeline — same messages, same events, same AI history, same notes. No "I forgot to copy you on that Slack thread," no "I checked the wrong tool," no "the assistant didn't see what I told the cleaner."

"A guest is escalating a complaint and they're CC-ing the channel rep. I need to be ready." Open the reservation. You have the complete defensible record of every interaction, every code, every charge, every cleaning, every payment, every reply — yours and the AI's — in chronological order, exportable as a timeline. You're already ready.

"I want to see what the AI was thinking when it told the guest the wrong check-in time." Open the reservation, find the AI message, click it. The full reasoning trace shows: which knowledge base article it pulled, what context it had, what it considered, what it ruled out, what it concluded, what it actually said. Then update the knowledge base article in 30 seconds and the next AI reply uses the corrected version.

"How do I show this to a customer who's evaluating Vanio?" Open any reservation in your demo account. The screen sells itself. The contrast with whatever they're using today is instant.