Your team works across every property from one place, and each hotel keeps its own people, channels and standards — even its own PMS. Use it as soon as the second hotel means a second login, a second inbox and a second set of numbers that never line up.
You run hotels you do not own. Every owner wants their own reporting, and no owner should ever see another's numbers.
Several properties under one company, and one set of standards you want followed in all of them without visiting each one to check.
Two or three hotels you own and run yourself. No head office to lean on, and no budget for one.
A hotel that ran fine on its own becomes a second login, a second inbox and a second set of numbers. The industry has already measured what that costs.
One hotel can carry this. A group pays it once per property, every day.
A workspace holds a set of hotels with their own people and settings. Use one for the hotels you run together, and give a separate company or brand a workspace no one else can see.
Nothing crosses between workspaces — not a message, not a task, not a number. Two owners on the same platform never see each other.
For each hotel a person works in, every module is set to Admin, User or No access, and each hotel is set on its own. The same person can manage one hotel and only read another.
Add a reservations manager to every hotel and they answer for the whole group. Add a housekeeping supervisor to one hotel and that is the only hotel they see.
A reservations manager covering several hotels keeps a browser tab open for each one, and sometimes replies from the wrong one. One account covers them all, and the housekeeping supervisor still sees only hers.
Guest messages from every hotel arrive in the same inbox, each one marked with the hotel it came from, and you can show one hotel or all of them. Every reply is sent from that hotel's own channel.
A guest who writes to one hotel gets the answer from that hotel, not from head office and not from a hotel they have never stayed in.
A guest writes to the resort and gets an answer signed by head office. Every reply now leaves from the hotel they wrote to.
A person works across several hotels from a single login, and every task, checklist and message stays attached to the hotel it belongs to.
A maintenance engineer who covers three hotels, or a night manager on duty for the group, stops carrying three accounts and three passwords.
An engineer covering three sites carries three logins and three passwords. One now, scoped to his hotels, with every task still filed to its property.
One price for the layer that runs across the group, plus a flat price for each hotel in it. Every hotel includes Hotel services, Guest communication, Team chat and Tasks.
2+ hotels — one layer across every property, with roles set per hotel.
Book a group demoLarge estate — custom modules built to how you operate.
See how it worksEvery group starts with a free trial — 30 days for one hotel, 60 days for the group.
Yes. For each hotel a person works in, every module is set to Admin, User or No access, and each hotel is set on its own. Admin in one hotel does not make them Admin in the next. There is also a workspace level for the people who work across the whole group.
Yes. Treema sits on top of the booking system each hotel already runs, so hotels on different systems can sit in the same workspace. You do not have to move every property onto one PMS first.
Yes. Give each one its own workspace. Nothing crosses between workspaces — not a message, not a task, not a number.
Add the property, then add the people who work in it. The hotels a person covers can be changed at any time, and the price is a flat amount per hotel.
Set the person to inactive. Access stops at once, and their hotels and roles are kept, so bringing them back next season takes one click instead of setting everything up again.
$179 a month for the layer that runs across the group, plus $89 per hotel per month. Every group starts with a 60-day free trial.
Meet our team to talk through what running Treema at your hotel would look like.