Kirako connects your inboxes, calendars, per-listing rules and contractors. The agent replies inside the frame. The team only sees what needs a decision.
A guest message, a booking, a checkout is enough to wake the flow. We start with a slice of the portfolio, not the whole book at once.
We pick one repetitive job across the portfolio, with the channels already there. We set what the agent is allowed to do. Then we let it move.
Messages
Check-in, house rules, a cot, a late arrival. Each listing has its rules, each owner their exceptions. The inbox mixes them all.
What runs
The agent reads the message, applies the listing rules, prepares the reply. A refund or a dispute stays human.
Read the Airbnb articleCalendar
Airbnb, Booking, owner calendars, one iCal per listing. One night left open and you are catching a double booking in the heat.
What runs
The booking is read, the reference calendars are checked, an alert goes out if a sync is missing. Nothing gets locked in the fog.
See HermesCleaning
Checkout at 10, check-in at 16, a cot, a guest remark. The fact lives in the thread. The contractor cannot see it.
What runs
The brief goes out with the useful facts. Exceptions stay under the team's approval.
See the AI agentsAirbnb, the calendar, WhatsApp, the rules of each listing stay. Kirako scopes a flow: what can be answered on its own, what gets prepared, what stays human. A server in Europe, your keys, a readable frame.
We start from the messengers, calendars and rules already there. Not another app for the guest.
Dispute, refund, pricing exception: the agent prepares, a human approves.
What was read, prepared, sent stays inspectable. You can take back control.
Gauthier built us an autonomous AI agent that handles all our Airbnb guest messages on its own, following our rules. It alerts us whenever a decision or an issue calls for it. We've saved enough time to start planning the expansion of our rental portfolio.
Yes, inside the frame you approve: channels, tone, listing rules. Sensitive cases stay as drafts.
ChatGPT waits until someone pastes the message into a tab. Here the message arrives, the listing rules apply, the reply is prepared in the channel.
We check the reference calendars and alert if a sync is missing. We do not promise to fix a calendar tool we do not control.
No. It gathers the context and prepares. Deposit, damage, neighbours, refund: a human decides.
This page is for a concierge team that runs a portfolio. A host working alone can ask the same questions; scoping still starts with one flow, not the whole operation.
Your keys, your access, a dedicated server in Europe. The AI model is chosen during scoping. The detail is in the proposal.
One channel, one type of message, a slice of the portfolio. We expand if the first results hold.
In 20 minutes, we look at the portfolio, your channels, your calendars, and the requests that come back too often.
See how Kirako runs
