Stop running your hotel out of WhatsApp groupsStop running your hotel out of WhatsApp
Guest messages, shift handovers, tasks and department SOPs in one place — with three agents that read your hotel's own data and act on it.
- SK2mSarah Kleinmarina bay · room 412
- RA9mRami Azizpalm suites · arrival
- JD26mJulia Duboisdesert rose · billing
- LM41mLena M.housekeeping · handover
- KR1hKarim R.maintenance · escalation
- Housekeeping38%
- Front office21%
- Maintenance14%
- Food & beverage11%
- Spa9%
- Other7%
- LMLena M. closed the night handover2m ago
- KRKarim R. assigned four rooms to housekeeping8m ago
- CMCarlos M. cited the turndown SOP on a task14m ago
- LMLena M. escalated a thread to the duty manager22m ago
- KRKarim R. published the evening briefing31m ago
- CMCarlos M. closed a maintenance task at Palm Suites45m ago
Treema, at a glance.
- A.
- One place for guests, tasks and shiftsEvery property in the group on the same screen.
- B.
- 14 department knowledge basesHousekeeping alone holds 69 procedures. Staff get the passage and the citation, not a folder.
- C.
- The night shift hands over in writingBriefings, open tasks and escalations carried to whoever comes on next.
- D.
- GEX, LORA and SAM work on your own dataGuest experience, internal operations, and assets and finance — one each.
- E.
- 16 flow templates to start fromArrival, complaint, maintenance call-out. Edit them or build your own.
- F.
- 9 departments, one structureMembers, groups, shifts and SOPs line up with how the hotel is actually staffed.
Ships with the procedures already written.
A hotel's procedures usually live in a folder nobody opens and a chat group nobody scrolls back through. Treema arrives with the department knowledge bases and the flow templates already in it, and puts the procedure next to the task it belongs to.
- 16
- 14
- 69
Answered at two, handed over by seven.
A guest writes at 02:14.
GEX reads the message, works out what it actually asks for, and drafts the reply. The night auditor approves it or hands it to the duty manager.
One board for the whole night.
Arrivals still to come, rooms out of service, what the evening shift left open. On one screen, instead of scrolled back through a chat.
The handover writes itself.
The late arrival, the maintenance call, the reply that went out — collected into the morning briefing, with an owner and a procedure against each line.
The morning starts already briefed.
Nothing is retold from memory. Every action from the night carries a time and a name in the activity log, so the day begins from the record.
What got lost
what got done
Every one of these started as somebody telling somebody else — in the WhatsApp group, on the radio, on a rota printed before the shift began. Treema keeps the request, the owner and the procedure in one place, so the evening ends with a record instead of a memory.
| Time | Floor | Hops | Where | Note |
|---|---|---|---|---|
| 19:42 | L2 | 2 | Room 214 | late checkout ask |
| 19:58 | L1 | 3 | Lobby | spill by the lift |
| 20:11 | L3 | 5 | Room 312 | a/c not cooling |
| 20:24 | L2 | 2 | Restaurant | allergy at dinner |
| 20:47 | L1 | 4 | Front desk | passport mislaid |
| 21:03 | L3 | 6 | Room 340 | shower leaking |
| 21:19 | L2 | 3 | Room 227 | extra towels |
| 21:36 | L1 | 2 | Valet | car on the ramp |
No quotes on this page. Only the rules we hold ourselves to.
- The work
- One place, per property.
- A group chat and a sheet.
- Handover
- Written while the shift runs.
- Whatever the last person remembers.
- Procedures
- The SOP cited on the task.
- A binder nobody opens.
- Messages
- Triaged, drafted, then approved.
- Whoever sees it first replies.
- Rota
- One board, always current.
- Printed Monday, wrong by Tuesday.
- Ownership
- Every task carries a name.
- Everyone saw it, nobody owns it.
- Group view
- Every property, one view.
- A phone call to each GM.
One place, per property.
A group chat and a sheet.
Written while the shift runs.
Whatever the last person remembers.
The SOP cited on the task.
A binder nobody opens.
Triaged, drafted, then approved.
Whoever sees it first replies.
One board, always current.
Printed Monday, wrong by Tuesday.
Every task carries a name.
Everyone saw it, nobody owns it.
Every property, one view.
A phone call to each GM.
The floor runs on the phone already in their hand.
AC out. Maintenance has it, and a reply to the guest is drafted.
Two names from outside. The rest already ships inside.
- Oracle OPERA
- Stripe
- Smart Inbox
- Knowledge Bases
- Flows Builder
- Shifts
- Internal Chats
- Storefronts
Hover any cell for what it does.
One price per hotel.
Everyone at the hotel is included.
Under 50 rooms, and nobody to spare.
- ·One hotel, under 50 roomsincl.
- ·The whole product, nothing held backincl.
- ·GEX, LORA and SAM on your own dataincl.
- ·We set the property up ourselvesincl.
- ·30-day trial once you are liveincl.
- Monthly$69.00
- Annual, per month$55.20
Every department on one board.
- ·One standalone hotel, any sizeincl.
- ·Everything in Small or Boutiqueincl.
- ·Every department, every shiftincl.
- ·We set the property up ourselvesincl.
- ·30-day trial once you are liveincl.
- Monthly$149.00
- Annual, per month$119.20
Every property, plus the layer across them.
- ·Every property in the groupincl.
- ·Everything in Standard, per propertyincl.
- ·The cross-property layer over all of themincl.
- ·The chain fee is what that layer costsincl.
- ·60-day trial once you are liveincl.
- Chain level$89.00 / mo
- Each property$149.00 / mo
- Annual billing−20%
When the rollout needs a plan of its own.
- ·Implementation and onboardingincl.
- ·Migration from what you run todayincl.
- ·Single sign-onincl.
- ·A rollout schedule per propertyincl.
- ·Training for department headsincl.
- ·A named contact through go-liveincl.