- Built from daily operations
- From stays to procedures
- A team that stays in control
Before: reconstructing the day across tools
A date changes, a guest asks a question and an intervention needs attention. The starting need was concrete: see the stay, property, conversations and work without piecing the story together every time.
After: start with the stay
The calendar opens the booking context. Messages, tasks and finances are accessible in one workspace. Folder-based navigation organizes each team’s work.
Ocho prepares, the team reviews
A briefing, a reply or a procedure no longer starts from a blank page. The team reviews the content, tests the steps and chooses the automations it authorizes.
What real operations bring to the product
Property teams do not work only in booking order. They switch between a guest and an owner, a field issue and a schedule, an amount and a conversation. The design challenge is to preserve context during those switches.
That guides Keyful’s choices: a stay opens its detail, the calendar stays dense, service inboxes are explicitly shared and navigation can use folders. The aim is to find information without learning a new route every time.
Four situations that explain the setup
These working situations explain what the product supports. Use them to plan your own workspace without assuming every business has the same team.
| Moment | Information needed | Starting point |
|---|---|---|
| Prepare arrivals | Stays, times, properties, open items | Calendar and dashboard |
| Take over a conversation | History, guest, property instructions | Messages and shared inbox |
| Plan an intervention | Owner, date, stay context | Task and calendar |
| Review the portfolio | Period, channel, amounts and export | Finance and widgets |
What to take into your own team
Start with three views: the day, requests to handle and figures for the period. Organize folders around actual responsibilities rather than every available module. Start with one shared service inbox and test access with a colleague.
Then choose a recurring procedure such as an arrival briefing. Describe it to Ocho, test it using your own recipient and ask the person using it to review it. A useful model is one the team can explain and maintain.