Run serviced-apartment bookings and guest requests on WhatsApp
Track availability across every unit, send arrival instructions before check-in, and handle in-stay requests — from one shared WhatsApp number, not a personal phone split across staff or a spreadsheet nobody keeps current.
Discover
Convert
Order
Fulfil
Support
Retain
Feedback
What breaks when units run on phones and spreadsheets
A serviced-apartment operator manages more units than one person can track from memory. Split across a personal phone and a shared spreadsheet, availability and guest requests fall out of sync fast.
- A staff member's personal WhatsApp holds guest threads no one else can see once they're off shift
- Two staff members quote the same unit to two different guests because the spreadsheet wasn't updated in time
- Arrival instructions get typed out by hand for every guest, so a rushed message skips the gate code or the parking note
- An in-stay request — an extra towel, a broken AC — sits in a chat thread with no one assigned to it
What the unit and guest record holds
One catalog for every unit, one thread per guest, both visible to the whole team.
- Unit catalog
- Every unit's photos, floor, amenities and capacity, kept in one catalog instead of a shared spreadsheet.
- Availability
- Which units are open for which dates, checked before a booking is confirmed.
- Guest thread
- One WhatsApp conversation per guest, with the full history any staff member can pick up.
- Arrival instructions
- Check-in, check-out and post-stay messages sent from a saved template, not retyped by hand each time.
- Service request
- A guest's in-stay request, logged with a status and an owner until it's closed.
From enquiry to a handled stay
The same sequence for every unit and every guest.
Guest messages the property
A prospective guest asks about dates and a unit on WhatsApp.
Availability is checked
Staff check the unit catalog and calendar before quoting or confirming a date.
Booking confirmed
The guest gets a confirmation over WhatsApp, tied to their contact record.
Arrival instructions sent
Check-in details go out before the stay, from a saved template rather than typed fresh.
In-stay requests logged
A request during the stay becomes a tracked item with a status, not a message that gets lost.
What the guest sees
One thread from the first question to the request handled mid-stay.
What the team sees
Every unit, every guest thread and every open request in one shared view.
- A unit catalog the whole team reads from, instead of a spreadsheet that's out of date by the time it's shared
- Every guest thread visible to any staff member, with the conversation history attached
- A queue of open in-stay requests, each with a status and an owner
- Arrival, check-out and post-stay messages sent from saved templates instead of typed per guest
Who's in control
Every booking and message goes through your team, not automation deciding on its own.
- A staff member confirms availability and the booking; nothing books itself
- In-stay requests are closed by whoever picks them up, not automatically
- Message templates are set by the workspace admin, and staff choose which one to send
- Changing or cancelling a booking happens in conversation with the guest, not through a self-serve link
What this does not do
Morasel does not replace a full property-management system for accounting or cross-platform rate management. It holds the unit catalog, the guest conversation and in-stay requests, so your team stops working from a personal phone and a separate spreadsheet.
Run every unit's bookings and requests from one number
Start free and put your unit catalog, guest threads and in-stay requests in one shared inbox.
Serviced apartment questions
Can our whole team see the same guest conversation?
Yes. Every guest thread is shared, so any staff member can pick it up with the full history attached, not just the person who started it.
How do arrival instructions get sent?
From a saved template, sent before check-in — a gate code, parking note or WiFi password doesn't get retyped by hand for every guest.
What happens to a guest's in-stay request?
It's logged as a tracked item with a status and an owner, so a request for an extra towel or a repair doesn't sit unanswered in a chat thread.
Can we manage more than one building or unit type?
Yes. The unit catalog holds every unit's photos, amenities and capacity in one place, whatever building or floor it's on.
Does this replace our property-management system?
No. Morasel holds the unit catalog, the guest conversation and in-stay requests; accounting and cross-platform rate management stay in your existing system.
Can a guest book or cancel without a staff member?
No. A staff member checks availability and confirms every booking inside the WhatsApp thread; a change or cancellation is handled the same way, in conversation.
How is this billed?
Through your Morasel subscription — Core $79, Pro $179, Max $349, Custom on request. WhatsApp usage is billed separately, per delivered message, from a prepaid wallet at the rates in our published rate card — based on Meta's official WhatsApp pricing by country and message type, plus a Morasel service fee.