Pacho is now on WhatsApp

Short-term rental operations have two users with nothing in common.

On one side is the operations manager, running hundreds of units across a dozen buildings, watching bookings shift, mid-stays extend, and same-day turnovers collapse into each other. That person needs depth: a full picture, every exception visible, and a system that acts without being asked.

On the other side is the cleaner standing outside apartment 4B at 11:40 with a key in one hand and a phone in the other. That person needs one thing: what am I doing, and where.

Most field software is built for the first user and then handed to the second. That's why adoption fails. The manager gets a system of record and the cleaner gets a login they never use, so the real coordination migrates to a group chat — and the manager loses the one thing the software was supposed to give them.

Pacho splits the interface without splitting the operation.

Managers: coordination that runs itself

Pacho sits between the revenue stack and the field. Bookings, cancellations, extensions and gaps arrive as signals, and Pacho turns them into dispatched work on its own — the right task, the right window, the right provider, without a human building a schedule.

That means the manager's job changes shape. Instead of assembling the day, they supervise it:

• Work is generated from booking signals, not from a weekly plan someone maintains by hand
• Assignment respects provider capacity, travel, and the window the property actually allows
• Changes propagate. A late checkout moves the clean; a cancellation releases the slot
• Completion is verified, not assumed, and exceptions surface as they happen rather than at the end of the day
• Reporting, provider performance and cost roll up without anyone compiling anything

This is the part of Pacho that is deliberately comprehensive. Everything — properties, providers, task templates, checklists, escalation rules, invoicing — is configured and controlled in one place. Our customers run up to 400 units per operations manager on this model.

The field: WhatsApp, no installation

None of that reaches the guest unless the person doing the work actually reports.

So field staff don't install anything. Pacho dispatches directly into WhatsApp.

Onboarding a cleaner is adding their phone number. Nothing else.

The cleaner receives the assignment as a message: property, cleaning type, time window, address. Three replies sit underneath it — Start, Instructions, Report issue. Tapping Start opens the checklist, which they work through item by item. If something is wrong — a broken appliance, a missing key, a guest still in the unit — they report it in the same thread, with a photo.

Everything comes back structured. Who started, when, which items were completed, what broke, with proof attached. The manager sees a verified task in Pacho. The cleaner saw a conversation.

No download. No password. No onboarding session. It works for a cleaner hired yesterday and for a subcontracted crew you don't employ.

One thread, every language

Every message arrives in the language that person reads. The manager writes the checklist once, in their own language; each cleaner receives the dispatch, the instructions and every item in theirs, and what comes back is translated the other way before it reaches the manager. Our customers run Finnish, Spanish and English crews across the same properties without maintaining three versions of anything — and adding a fourth language costs nothing but a new phone number.

And the mobile app, when you want more

WhatsApp is the zero-friction floor, not the ceiling.

For in-house teams and long-term service partners, the Pacho mobile app goes considerably further: full task history, photo-verified inspection flows, offline handling, richer issue reporting, maintenance workflows, and visibility into their own upcoming schedule and performance. Teams that work for you every day usually want that, and they adopt it because it makes their own work easier.

The point

Field operations software fails on the last hundred meters. Not in the scheduling logic, but in whether the person holding the keys reports what they did.

Pacho solves the manager's side by removing the coordination work entirely, and the field's side by removing the software entirely.