Built for
Teams running repeat guest guidance across multiple properties
For operators who need one place to manage guest guidance, property rules, and repeat questions across listings.
QR-first guest lane·Automate check-in guidance·Verified information only
Automate guest messaging for vacation rentals. Hand off only the cases that need judgment.
Hinoki is a guest-operations system for vacation-rental teams. It starts with an in-room QR guide after check-in, can add optional voice support inside the same guest session, keeps replies grounded in verified guidance, and adds Beds24 only when booking-linked workflows are worth the extra integration.
In-room QR guide · Verified replies only · Optional voice support
Verified information only
Hand off when judgment is needed
Hinoki workspace
Today's guest messaging
Inquiry queue
24 activeLate check-in request
Parking clarification
Damage complaint
Rule review
2 pendinghouse_rules.quiet_hours
Quiet hours are from 22:00 to 07:00. No rooftop access after 21:00.
ApproveEditReject
Operator handling
Handled by operatorReasonRefund after noisy-night complaint
ActionHand off to an operator and keep the audit trail
BillingCases that need extra handling
Operating model
Automated replies use verified information only
Guidance and rules are reviewed before they are used, so the system does not improvise with unverified information.
Launch lane
Start with the in-room QR guide
The first workflow is the guide guests open after arrival for access steps, stay FAQ, and repeat requests.
Human handoff
Refunds and guest issues stay with a human
Damage, complaints, and refund-related cases are handed to an operator instead of being forced through automation.
Setup Chat
Import manuals and message templates, then turn them into usable operating information.
Rules
Manage the guidance and rules used in automated replies.
Desk
Hand off only the cases that actually need a person.
Activity log
Review why a message was sent, held, or handed off.
How it works
More than a chatbot. Built around the way vacation-rental operations actually run.
Hinoki automates the repeat work in vacation-rental operations: QR guidance after check-in, common questions, and property rules. Optional voice support stays inside the same controlled guest session, and anything that needs confirmation or judgment can be stopped and reviewed before it reaches the guest.
01
Verify and organize information first
Guidance and operating rules are reviewed before they are used in replies.
02
Publish the QR guide and optional integrations
Guests enter from an in-room QR and short PIN, then Beds24 is added later only where booking-linked workflows materially improve the operation.
03
Keep voice inside the same safety boundary
Optional voice support uses the same approved knowledge, trace, and Desk handoff rules instead of becoming a separate unsupervised lane.
04
Hand off the difficult cases
Refunds, damage, and complaints move to an operator instead of being forced through automation.
Public guides
Review the QR-first guest lane, optional voice support, Beds24 foundations, and post-purchase setup before you activate the workspace.
These public pages are meant for early requirement-setting, internal review, and post-purchase setup planning. They explain how to structure the in-room QR lane first, where optional voice support fits inside the same guest session, and when to add a Beds24 webhook after the workspace is active.
Scan from the LP and open the canonical demo guide on your phone
Open the LP on desktop, scan this QR with your phone, and step through the sample guest lane directly. The sample PIN is 4826, and refund or complaint requests fail closed into a manual follow-up state.
Demo PIN 4826No tenant dataTranscript voice demo
Open demo guidefor manual / sales / guest preview
Demo
Try the canonical sample guest guide
Open the stable demo guide from a guest point of view without touching tenant data.
Read guideUsageSet up the Beds24 webhook after purchase
Review the workspace, endpoint, secret, Beds24 registration, and first test flow before go-live.
Read guideSolutionMake the in-room QR guide the main guest lane
A public guide on using QR after check-in, with optional voice support kept inside the same controlled session.
Read guideSolutionAdd Beds24 only when booking-linked workflows matter
A public guide on where reservation data should join the guest-guidance flow.
Read guideSolutionHow to manage the FAQ source of truth for vacation rentals
A public guide on keeping what text and voice can say aligned with approved operating guidance.
Read guideUse caseStructure post-check-in guidance around QR access
A public guide on check-in steps, short-PIN entry, and repeat guest questions after arrival.
Read guideHinoki Concierge MCP
Operate the same Hinoki workspace from Codex, Claude, or OpenClaw through a controlled local MCP.
Hinoki Concierge MCP is not a hosted autonomous agent. After payment, the owner issues a credential and each team installs the MCP locally on the machine that runs the client. The first release includes MCP in active paid plans, with the public MCP page routing operators to GitHub docs and releases.
CodexClaudeOpenClaw
Start local install from the public MCP guide
Install on Python 3.10+, then add the owner-issued token after payment. Downloading the package alone does not connect to a workspace.
Python 3.10+Local stdio MCPOwner-issued token
1. Activate the workspace
A paid workspace unlocks MCP entitlement while Hinoki backend remains the source of truth.
2. Issue a partner credential
The owner issues a tenant-scoped token for Codex, Claude, or OpenClaw from the operator console.
3. Install locally
Each client launches the same `hinoki-concierge-mcp` stdio server from the operator's machine.
Automation boundary
Automate the routine. Hand off the cases that need judgment.
The line is explicit. Automated replies use verified information only. Refunds, damage, complaints, and anything outside that scope are handed to an operator.
Handled automatically
Check-in steps, access instructions, and arrival guidance
Approved answers to repeat guest questions
House rules and property-specific guidance
Late check-out availability based on booking data
Repeat inquiries that match verified information
Handled by an operator
Refund requests and compensation questions
Damage reports and complaints
Questions outside the registered guidance
Cases that need operator judgment
Anything automated handling cannot answer safely
Pricing
Priced for guest operations, not basic PMS administration.
Every plan uses verified information, activity logs, and human handoff. QR self-service and voice-agent rollouts can be added as controlled workflows instead of being bundled as unlimited chatbot usage.
Starter
For operators running 1 to 3 properties, billed per property
¥3,800/ property / mo
- Reply with verified information only
- Human handling for refunds, damage, and exceptions
- Automated check-in guidance
- Automated replies for approved FAQs
- Alerts by Slack, Telegram, or email
- Activity log on every case
No setup fee. No peak-season surcharge.
Review Starter plan →Need broader coverage?
Support larger portfolios and custom workflows without changing the safety model.
| Capability | Small¥16,800/ mo | Standard¥27,800/ mo | Pro¥49,800/ mo |
|---|---|---|---|
| Rules + operator handoff + activity log | ✓ | ✓ | ✓ |
| Check-in guidance | ✓ | ✓ | ✓ |
| Approved FAQ auto-replies | ✓ | ✓ | ✓ |
| Properties | 4 to 5 | Up to 15 | Up to 30 |
| ECI / LCO workflow | — | ✓ | ✓ |
| Local recommendations | — | ✓ | ✓ |
| Luggage handling | — | — | ✓ |
| LINE connector | — | Add-on | ✓ |
| Visual dashboard | — | — | ✓ |
Need a custom rollout?
For operators that need deeper PMS integration, a Grok voice-agent pilot, QR self-service menus after check-in, or rollout across more properties.
Scoped project fee. Voice usage is capped or metered so the base plans stay predictable.
Get started
Activate the workspace when the plan fits your operation.
Review plans, enter your operator details, and move into secure payment when you are ready to activate the workspace.
01
Review plans
Review plans and enter the operator details you will use for workspace activation.
Review plans →02
See the QR lane
Review the QR-first guest guide and how optional voice stays inside the same safety boundary.
See QR lane →03
Talk through fit
We review your property count, workflow, and pricing before launch.
Request a fit check →