---
title: "Kiyo Product Tour | From Booking to Follow-up"
url: "https://kiyohq.com/demo/"
description: "A crawlable walkthrough of how Kiyo connects bookings, guest communication, daily operations, payments, checkout and follow-up."
---

![Kiyo daily workspace showing property priorities](https://kiyohq.com/kiyo-assets/provided/homepage/daily-workspace.webp)

![Kiyo daily workspace showing property priorities](https://kiyohq.com/kiyo-assets/provided/homepage/daily-workspace.webp)

Kiyo product tour

# See how a stay moves through Kiyo.

Follow the booking workflow, then open the interactive demo to explore the Kiyo workspace with sample data. Changes in the demo are not saved.

[Home and daily priorities

Start with the property overview and the work that needs attention today.](https://demo.kiyohq.com/dashboard/home)

[Bookings and calendar

Inspect how reservations, rooms, dates and booking context meet in one workspace.](https://demo.kiyohq.com/dashboard/home)

[Guest inbox

See how a guest conversation stays close to the relevant reservation context.](https://demo.kiyohq.com/dashboard/home)

[Revenue view

Review the interface used to understand property performance and trends.](https://demo.kiyohq.com/dashboard/home)

Technical product tour

## A stable guide to the Kiyo workspace.

Explore how bookings, guest conversations, daily work and property performance appear in the Kiyo workspace. This tour uses sample data and can be read without signing in.

### Home and daily priorities

**Purpose:** See the property overview and the work that needs attention today.

**Inputs:** Recorded bookings, guest activity and configured workspace data.

**Output:** A prioritised view for the property team.

**Availability:** The public tour shows fixture data; a property workspace depends on its enabled product access and recorded data.

### Bookings and calendar

**Purpose:** Keep reservations, rooms, dates and stay context in one calendar.

**Inputs:** Direct and manually entered bookings, plus reservations from connected and mapped OTA channels.

**Output:** A live calendar and reservation record for the property team.

**Availability:** Channel reservations require an active connection and correct room and rate-plan mapping.

### Reservation record

**Purpose:** Keep the guest, stay and recorded payment status close together.

**Inputs:** A booking recorded in or returned to Kiyo.

**Output:** One record for reviewing stay context and related operational work.

**Availability:** A payment taken outside Kiyo must be recorded before its status can appear in Kiyo.

### Guest inbox

**Purpose:** Review supported guest conversations next to reservation context.

**Inputs:** Connected, eligible messaging or OTA accounts and guest-initiated messages where required.

**Output:** A guest thread kept close to relevant booking information.

**Availability:** Channel coverage, account eligibility and platform rules vary; verify the exact messaging setup for a property.

### Guests

**Purpose:** Review guest records and the stay context held with each recorded booking.

**Inputs:** Guest and stay details recorded with a booking.

**Output:** A place for the property team to review guest context before follow-up work.

**Availability:** The public tour shows fixture records only; the details available for a live property depend on its recorded bookings and permissions.

### Workspace and team work

**Purpose:** Keep private team coordination and operating work separate from guest replies.

**Inputs:** Property-team work, private notes and recorded stay context.

**Output:** Internal context for handovers and follow-up work.

**Availability:** Private team communication is not a guest-delivery channel, and the fixture tour does not prove a live team workflow.

### Daily operations

**Purpose:** Bring arrival, departure, tasks, requests and handovers into the property workspace.

**Inputs:** Recorded stays and the property team’s operating work.

**Output:** A shared view of work around the stay.

**Availability:** The fixture tour illustrates the interface, not a live property handover.

### Revenue workspace

**Purpose:** Review revenue, occupancy, ADR, RevPAR and booking-performance trends.

**Inputs:** Recorded booking, channel and rate data within the property’s permission and date window.

**Output:** Performance measures for operating decisions.

**Availability:** These measures are not accounting profit or cash received, and forecasts are estimates rather than guarantees.

### Kiyo AI Assistant

**Purpose:** Explore the interface intended for practical questions about current property work and data.

**Inputs:** The property context and data available to the enabled assistant.

**Output:** A response that supports human review and follow-up work.

**Availability:** The fixture tour does not prove a live AI result, and the assistant is not a replacement for human judgment, audited accounting or tax advice.

### Website and direct booking

**Purpose:** Present configured rooms and hand a guest into a direct booking journey.

**Inputs:** An enabled property website, configured rooms, rates and availability.

**Output:** A guest-facing room-discovery and checkout path.

**Availability:** Direct checkout and website controls are enabled per property; payment collection requires the applicable payment setup.

### Payments and confirmation

**Purpose:** Keep payment results connected to the relevant booking context.

**Inputs:** An eligible property, configured payment methods and an external provider response where payment is collected.

**Output:** A recorded payment result alongside the reservation.

**Availability:** Methods, merchant activation and market eligibility vary; a provider can delay, reject or expire a payment.

### Reviews and follow-up

**Purpose:** Review stored guest feedback and support post-stay follow-up.

**Inputs:** Connected and authorised review sources or enabled follow-up journeys.

**Output:** Review context and configured follow-up work for the team.

**Availability:** Source coverage, history and available actions vary by platform and property setup.

### What this public evidence does not expose

- It does not expose customer data, credentials, provider payloads or private security architecture.

- It does not prove a specific property has an active channel, payment or messaging connection.

- It does not turn the interactive dashboard into an indexable application or bypass its email-gated exploration path.

 [Open the interactive desktop demo](https://demo.kiyohq.com/dashboard/home)

The demo uses sample data and changes are not saved. Ask Kiyo to confirm the exact channel and payment connections available for your property.

Workflow walkthrough

## What the demo proves, and what it does not.

These steps separate what Kiyo publicly supports, what depends on a configured connection and what the public demo cannot verify.

### Ready to inspect the real setup?

Use the fixture-only demo for the interface, or talk with Kiyo to verify the exact channels, payment methods and onboarding path for your property.

 [Open the interactive demo](https://demo.kiyohq.com/dashboard/home)

### Booking to arrival

1. Receive a reservation

Explicitly supported: direct, manually entered and supported OTA reservations can meet on the same Kiyo calendar. The exact provider connection must be active and correctly mapped.

2. Update inventory and rates

Conditionally supported: eligible, mapped channel connections can receive availability, rates and supported stay rules. Reservation changes can return through the connection, but provider timing and controls vary. Review the booking and channel state before relying on the update.

3. Review the stay

Explicitly supported: the booking calendar and reservation record keep room, dates, booking status and related guest context together.

4. Contact the guest

Conditionally supported: Booking.com, Airbnb and Expedia replies, plus configured WhatsApp Business, Telegram, Outlook, Messenger and Instagram accounts, can be handled inside Kiyo. Other OTA conversations may still require the channel extranet.

5. Prepare arrival

Explicitly supported: daily operations can bring arrivals, departures, tasks, requests and handovers into the property workspace.

### Stay to follow-up

6. Collect payment

Conditionally supported: cards, QRIS, e-wallets and virtual accounts depend on the property market, merchant activation and configured payment methods. Payment, reservation and payout status remain separate facts.

7. Coordinate the team

Explicitly supported: private notes and Kiyo Team Chat are kept separate from guest replies so internal handovers are not sent to the guest.

8. Complete checkout

Reasonable interpretation: the stay can move through departure and checkout work, but the public demo does not prove a live end-to-end payment settlement or OTA update.

9. Follow up

Explicitly supported: configured post-stay email journeys, guest feedback and review follow-up are described on Kiyo product pages.

10. Review performance

Explicitly supported: revenue, occupancy, ADR, RevPAR, trends and room or channel performance can be viewed from property booking records.

### Demo boundaries

Can the demo save changes?

No. The public demo is fixture-only and changes do not save. It must not be treated as proof that a live provider or payment account is connected.

Why is the dashboard not indexed?

The interactive application contains mock operational records and application controls. Kiyo keeps it out of search results while this crawlable tour explains the product in stable text.

Does the demo prove every integration?

No. A visible channel name, menu or image does not prove reservations, rates, restrictions, messages, reviews and payments are all supported. Verify each capability separately.

What should a buyer verify?

Confirm property eligibility, current rollout status, supported OTA operations, messaging coverage, payment activation, onboarding, support, data migration and the exact commercial terms.

Where is the machine-readable product summary?

Use Kiyo llms.txt for the canonical company briefing and sitemap.xml for the complete public URL inventory.

```json
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://kiyohq.com/"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Kiyo Product Tour | From Booking to Follow-up",
      "item": "https://kiyohq.com/demo/"
    }
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "WebPage",
  "name": "Kiyo Product Tour | From Booking to Follow-up",
  "url": "https://kiyohq.com/demo/",
  "description": "A crawlable walkthrough of how Kiyo connects bookings, guest communication, daily operations, payments, checkout and follow-up.",
  "isPartOf": {
    "@type": "WebSite",
    "name": "Kiyo HQ",
    "url": "https://kiyohq.com/"
  }
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "Kiyo HQ",
  "applicationCategory": "BusinessApplication",
  "operatingSystem": "Web",
  "description": "Kiyo HQ is a property management system (PMS) and channel manager built in Bali for independent hotels, villas, guesthouses and hostels across Indonesia. It connects to 75+ OTAs, including Booking.com, Agoda, Expedia, Airbnb, Traveloka, tiket.com and Trip.com, keeping rates and availability in sync to prevent double bookings. Kiyo brings reservations, a calendar, a direct booking engine, guest messages and revenue reports into one dashboard, in English and Bahasa Indonesia. Founded in 2025, Kiyo is run by a team of 7 and supports every property directly on WhatsApp.",
  "url": "https://kiyohq.com/demo/",
  "publisher": {
    "@type": "Organization",
    "name": "Kiyo HQ",
    "url": "https://kiyohq.com/"
  }
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "ItemList",
  "name": "Kiyo product areas in the public tour",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home and daily priorities",
      "description": "See the property overview and the work that needs attention today.",
      "url": "https://kiyohq.com/demo/#demo-home"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Bookings and calendar",
      "description": "Keep reservations, rooms, dates and stay context in one calendar.",
      "url": "https://kiyohq.com/demo/#demo-calendar"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Reservation record",
      "description": "Keep the guest, stay and recorded payment status close together.",
      "url": "https://kiyohq.com/demo/#demo-reservation"
    },
    {
      "@type": "ListItem",
      "position": 4,
      "name": "Guest inbox",
      "description": "Review supported guest conversations next to reservation context.",
      "url": "https://kiyohq.com/demo/#demo-inbox"
    },
    {
      "@type": "ListItem",
      "position": 5,
      "name": "Guests",
      "description": "Review guest records and the stay context held with each recorded booking.",
      "url": "https://kiyohq.com/demo/#demo-guests"
    },
    {
      "@type": "ListItem",
      "position": 6,
      "name": "Workspace and team work",
      "description": "Keep private team coordination and operating work separate from guest replies.",
      "url": "https://kiyohq.com/demo/#demo-workspace"
    },
    {
      "@type": "ListItem",
      "position": 7,
      "name": "Daily operations",
      "description": "Bring arrival, departure, tasks, requests and handovers into the property workspace.",
      "url": "https://kiyohq.com/demo/#demo-operations"
    },
    {
      "@type": "ListItem",
      "position": 8,
      "name": "Revenue workspace",
      "description": "Review revenue, occupancy, ADR, RevPAR and booking-performance trends.",
      "url": "https://kiyohq.com/demo/#demo-revenue"
    },
    {
      "@type": "ListItem",
      "position": 9,
      "name": "Kiyo AI Assistant",
      "description": "Explore the interface intended for practical questions about current property work and data.",
      "url": "https://kiyohq.com/demo/#demo-ai-assistant"
    },
    {
      "@type": "ListItem",
      "position": 10,
      "name": "Website and direct booking",
      "description": "Present configured rooms and hand a guest into a direct booking journey.",
      "url": "https://kiyohq.com/demo/#demo-websites"
    },
    {
      "@type": "ListItem",
      "position": 11,
      "name": "Payments and confirmation",
      "description": "Keep payment results connected to the relevant booking context.",
      "url": "https://kiyohq.com/demo/#demo-payments"
    },
    {
      "@type": "ListItem",
      "position": 12,
      "name": "Reviews and follow-up",
      "description": "Review stored guest feedback and support post-stay follow-up.",
      "url": "https://kiyohq.com/demo/#demo-reviews"
    }
  ]
}
```