Getting started.
What Treema is, how a workspace is put together, and what happens between the first walkthrough and your first live shift.
What Treema is
Treema is an operations platform your staff log into. It holds the shift a person is on, the tasks they own, the guest conversations waiting for a reply, and the procedure they need at two in the morning. Managers read the same record without having to ask anyone for it.
It is not a property-management system. Rooms, rates and reservations stay in the PMS. Treema is where the work around them happens — the handover, the task, the answer, the reply — and it is meant to replace the group chat, the printed rota and the shared folder nobody can find twice.
Signup is not self-serve. We set every property up ourselves: we build the workspace, load your procedures, and stay on the rollout until a department has run a full week on its own. Setup starts on the walkthrough call.
There is nothing to install
Treema runs in a browser. The laptop at the front desk, the tablet on the housekeeping trolley and the phone in a supervisor's pocket open the same address and see the same workspace, sized for the screen. There is no download, no app store, and no software to put on a hotel machine.
What each person needs:
- A work email address, one per person. Shared department logins are the fastest way to lose the handover record, because "front desk" cannot be asked what it meant.
- A browser kept reasonably current.
- The department they belong to, and the property or properties they work at.
How a workspace is put together
The account for the whole company. Coastal Hospitality Group has one workspace, and everything below sits inside it.
A single hotel. Marina Bay Hotel is a property. Nearly all daily work — a shift, a task, a room, a conversation — belongs to exactly one of them.
Properties grouped the way the business already groups them, usually by region. A cluster has a director, and it is the level a standard is written at.
Worked through: Coastal Hospitality Group is the workspace. Marina Bay Hotel and Palm Suites sit in the UAE cluster; Riyadh Central and Desert Rose Resort sit in the KSA cluster. A procedure written once for the UAE cluster applies at both properties in it. A task raised at Palm Suites belongs to Palm Suites and appears nowhere else, unless the cluster director opens the portfolio view — the one place the four properties are read side by side.
If you run one hotel, you still get a workspace and a property. The cluster level is simply empty, and nothing in the product asks you about it again.
Setup, start to finish
- 01/05Walkthrough
A call, not a demo reel. We ask how the property runs today: where the rota lives, who writes the handover, what happens when a guest messages at 23:40, and which folder the procedures are in.
- 02/05We build the workspace
Properties, clusters and departments first, then people. You send a staff list; we create the members, put them in groups, and scope each person to the properties they actually work at.
- 03/05Your procedures go in
A new workspace arrives with 14 department knowledge bases seeded, and housekeeping already holds 69 procedures. Yours go in on top, in whatever shape they exist: a document, a PDF, a laminated sheet on the back of a door.
- 04/05One department goes live
Housekeeping, usually, at one property. A single department for a single week is enough to surface the three things your rota does that nobody ever wrote down.
- 05/05The rest follows
Department by department, then property by property. Nothing has to switch over on one night, and the old group chat can stay open until people stop opening it.
What to have ready
None of this has to be tidy. It only has to exist.
| What | Why it is needed | | ------------------------------------------- | --------------------------------------------------------------------------------- | | A staff list with roles and departments | Members and groups are created from it, and access is scoped from it | | The current rota, in whatever form it is in | The first schedule starts from your week, not from an empty grid | | Your procedures, however scrappy | They become the department knowledge bases the agents are allowed to cite | | One named owner per property | Someone has to decide when a department is ready to stop running the old way | | Your department list | Members and Groups organises staff into 9 departments; yours are mapped onto them |
What Treema is not
- Not a PMS. Reservations, rates and availability stay where they are.
- Not a booking engine or a channel manager. Nothing here sells a room.
- Not a payroll system. Shifts record who worked and when. What they are paid for it is a conversation with your payroll.
- Not a place to hide from a conversation. The product makes the handover legible; it does not make the difficult call for you.
Where to go next
- Core concepts — the three layers, and what an agent decides on its own.
- Knowledge bases — where your procedures live once they are in.
- Shifts and tasks — the surface most of your staff will meet first.