Tasks — cleaning and maintenance

Tasks is one screen for the work that has to happen in the physical world: cleans and maintenance jobs.

The cleaning board

Cleans are laid out in day columns — today, tomorrow, the day after. Each card is one turnover: the room, the checkout time, the next arrival, and the cleaner assigned.

Turnover tasks are created automatically the night before a checkout. Nobody has to remember to make them, and they are created for that date only — the board is a rolling few days, not a year of pre-made rows.

For each task you can:

• Assign a cleaner — or leave the room’s default assignment to do it.
• Mark it done, optionally with a photo as evidence.
• Skip it, with a reason, when a guest stays on or the room was not used.

Default cleaner per room

Set the primary cleaner per room under the cleaning settings. There is no building-wide default, deliberately: in practice one villa’s rooms are covered by different people, and a building default silently mis-assigns them.

Cleaning clusters

A cleaning cluster is a group of properties one person covers — usually because they are within a few minutes of each other. Set a property’s cluster on its own page.

Clusters change two things: the board groups by them, and the daily brief produces one WhatsApp message per cluster listing only that cluster’s jobs. That message is what you send to the cleaner — it contains their work and nothing else about your estate.

What a cleaner sees

A team member with the cleaner role sees the cleans assigned to them, and enough about the property to find it. Not your bookings, not your revenue, not your door codes for other buildings. See Team and roles.

Tickets

A ticket is anything that needs fixing or chasing: a broken air-conditioner, a guest complaint, a supplier to call.

Tickets open by themselves from guest messages that read as complaints or maintenance issues, and you can create one by hand from the ticket screen or straight from the calendar.

Three things about the automatic ones are worth knowing, because they are what stop the list becoming noise:

• One thread, one ticket, ever. However many times the classification runs, a conversation that already produced a ticket never produces a second.
• Only the last fortnight. A thread nobody has touched in two weeks is history, not a job.
• They do not flood on day one. Connecting a year of message history does not open three hundred tickets; only the recent ones somebody can still act on are raised.

Each ticket has:

• A status — open through to done.
• An assignee — a teammate.
• A schedule — give it a date range and it is drawn on the calendar, so a two-day repair is visible against the bookings around it.
• An AI resolution plan, on request — a likely cause and a step-by-step plan, generated from the ticket and the property’s history. It is a starting point for whoever does the work.

Tickets are internal. Guests never see them, even the ones opened from their own message.

Team chat

Beside tasks there is a team chat for the people working the property — the conversation that otherwise happens in a WhatsApp group nobody can search later. It is separate from guest messages, and guests cannot see it.