The layer that was missing. Every event in one place your whole team can see — and booking one holds the rooms in your PMS.
Running events todayBliss Terra Janna · Marrakech
Your property management system handles the rooms. Everything else about the event is on its own.
“Is the 14th free?” — asked in a WhatsApp group, answered from memory.
One list everyone can see: confirmed, pending, and what is coming.
Rooms counted by hand in the PMS, then held one at a time.
Book once and the rooms are held in your PMS, released if it moves.
The kitchen hears about 46 covers when somebody remembers to say it.
Each department gets its own tasks, on its own phone.
The quote is rebuilt from scratch, out of last year's file.
The quote becomes the invoice, off the same event.
Every night shaded by how full you already are. You are not reading a booking sheet — you are seeing which weeks you can still sell.
Cloudbeds stays the source of truth for rooms. What changes is that booking here does something there.
CloudbedsWhere the rooms live
Availability is checked at the moment you save, against Cloudbeds itself. If they are not genuinely free the booking is refused, and tells you which ones.

Everyone in this picture is working from the same event.
Usually three tools and two people. Here it is one screen — whether the event takes the whole property or six rooms and the rooftop.
Room types, what is genuinely free, and the rate your PMS publishes. Villas come through as the bundles they are.
Save, and the holds are written into Cloudbeds under the event name. They stop being sellable anywhere else.
Pushed to Cloudbeds14:32Released automatically if the event moves dates or is cancelled. The rooms go straight back on sale.
Named guests in specific rooms, two to a room where they share, dietary notes riding along.
A pending event already holds its rooms. Book it while they are still deciding. Confirm when the money lands.
The events everyone keeps asking about stop living in an Excel file and four WhatsApp groups.
Four stages, from the first enquiry to the final invoice. Each one hands off to the next.
One form: dates, headcount, the spaces, the organizer. It saves as pending and turns confirmed when you log the deposit.
Rooms, spaces and people — and the work that comes with them. Adding a service raises the task for the department that delivers it.
The run of show as a canvas. The task board and the event thread sit beside it, so every department works off one page.
Rooms, zones and extras are already priced on the event, so the document assembles itself. Rack price and agreed price, side by side.
Nobody types into a database while walking a venue. Dictate the brain-dump; it comes back as tasks, with the right role and the right date.

Confirm the corkage with the catererKitchen · yesterday
Move the ceremony chairs to the olive groveMaintenance · Friday · 3 subtasks
Late checkout for the four villa roomsFront desk · Sunday
One team wearing six hats. Each person gets the slice of the event they need, and nothing else.
| In the app | Department | Finance | Coordination | Admin |
|---|---|---|---|---|
| The events calendarDates, guests, what is happening when | ✓ | ✓ | ✓ | ✓ |
| TasksDepartment roles see their own | ✓ | ✓ | ✓ | ✓ |
| Prices, quotes and invoices | — | ✓ | ✓ | ✓ |
| Create and edit events, book rooms | — | — | ✓ | ✓ |
| Rooms, zones, service catalog, billing details | — | — | — | ✓ |
One person can hold more than one hat. A manager who also runs the kitchen keeps both, and always the wider access. Company access and who may change an event are enforced on the server.
Most venue software dies in the first two weeks because setup is the customer's problem. Here it is ours.
Not a generic tour. We walk through a real event of yours.
We pull your rooms, room types and rates. Nothing is written back until you say go.
Zones, menus, drink packages, AV, transport, tax — loaded from whatever you have.
Invitations, roles, the phone app, and your first live event. We stay on it.
One of your actual weddings — not a sandbox, not a demo account. Thirty days, our people on it, and you judge it on a real event instead of a slide deck. Keep going only if it earns it.
The wedding priced on this page comes to 232,320 MAD — one client, one weekend. A hold nobody wrote into the PMS, a room resold underneath it, a kitchen that hears the covers late: none of that shows up as a line on the invoice. It comes off the margin.
From 1,950 MAD per property per month (€180). Here is what moves it from there.
Three things, and you can tell us all three in one email.
The things other people charge you for, one line at a time.
Not listed? Write to us. We answer the same day.
We reply the same day. Before the call we rebuild one event you have already run inside Assif — your rooms, your zones, your run-of-show.
We reply the same day, from someone at Flairr who read what you sent.