Team Chats
Team channels and one-to-one conversations that already know the guest, the booking, and the session — so internal coordination stops living in personal group chats.
Why Internal Coordination Breaks Down
At 11 PM the night manager takes a call: the family arriving tomorrow has a child with a severe nut allergy. He posts it in the staff group chat, which is the only place anyone posts anything. The kitchen lead is not in that group — she is in the kitchen group. Breakfast happens. Somebody apologises to a frightened parent, and everyone agrees they should be more careful next time.
Nothing about that story is unusual, and the fix is never 'be more careful'. Multiply it across housekeeping finding a broken shower, a driver whose airport pickup has shifted by two hours, an instructor moving a session because the swell dropped, and a front desk agent who promised a late checkout. Every one of those is a message that matters to somebody who is not in the group, about a guest, a room, a session, or a booking that the chat knows nothing about.
The deeper problem is that a group chat has no memory attached to anything. A message about room 4 is just text in a scroll. Six weeks later, when a guest disputes what was agreed, nobody can find it — and if the person who sent it has left, it may not exist at all. Experience hospitality is seasonal by nature, so this is not an edge case. It is May and October, every year.
Team Chats moves internal communication inside Artidal, where it sits next to the operation it is actually about.
Team Channels and Private Conversations
Staff get channels the way an operation is actually organised: one per property or branch, one per department — housekeeping, kitchen, instructors, transfers, front desk — and as many extra channels as a season needs, such as a channel for a specific retreat week or a group booking that involves everyone.
Alongside channels, any two people can hold a private one-to-one conversation. A manager raising a performance issue, an instructor asking about a guest's ability level, or a driver confirming a pickup does not belong in a room with fifteen people in it. Those conversations stay private, but they stay inside the system rather than moving to somebody's personal phone.
All of it runs on the login staff already use for everything else in Artidal. There is no separate account to create, no separate app to install on a seasonal worker's phone in week one, and no second system to remember to close down in week twenty.
Conversations Attached to Guests, Bookings and Sessions
This is the part a general-purpose chat tool cannot do, and it is the reason the module exists. Any conversation can be attached to the thing it is about: a guest, a booking, a room, an activity session, or a transfer.
The link works in both directions. Open tomorrow's booking and the discussion about that family's dietary requirements is on it. Open the conversation and the booking is one click away, with dates, room assignment, package, and the guest's history already visible. Nobody retypes a booking reference into a chat, and nobody searches a scroll for a message about a guest whose name they are not sure how to spell.
Because the conversation belongs to the booking rather than to a group of phone numbers, it survives the shift, the week, and the season. The kitchen lead who starts in June can open the same booking and read what was agreed in May.
Handover, Tasks, and a Record That Survives the Season
Shift handover is a structured note rather than a wall of messages scrolled through at 6 AM. The outgoing shift records what the incoming shift needs to know, attached to the property and the date, so it can be read once and found again later.
Any message can become a task with an owner and a due date. 'The shower in 4 is leaking' stops being a message somebody might act on and becomes an assigned job with a name against it. The message stays linked to the task, so the context travels with the work instead of being summarised badly into a to-do list.
Everything is searchable across the full history — by guest, by booking, by channel, by person, by date. The record belongs to the property, not to whoever happened to be holding the phone.
Why Personal Group Chats Are the Wrong Tool
Group chats on personal messaging apps are genuinely good at what they were built for: deciding who is bringing the van keys. They are a poor foundation for running a hospitality operation, for four reasons that get worse as a business grows.
- No context. The chat knows nothing about the guest, the booking, the room or the session, so every message has to carry its own explanation — and usually does not.
- No record. When a guest disputes what was agreed, or a manager asks what happened on a particular night, there is nothing to look at but a scroll on somebody's phone.
- No way to remove people. Seasonal staff leave in October and stay in the group for years. Nobody wants to be the person who removes them, so nobody does.
- Guest data on personal devices. Names, allergies, room numbers and arrival times end up on private phones the business does not control and cannot wipe — which is a data protection problem, not an inconvenience.
What it does
Channels organised the way the operation is — by branch, by department, or for a specific retreat week or group booking — so the right people see the message and the rest are not buried.
Direct messages between any two staff members for the conversations that do not belong in a room of fifteen people, kept inside Artidal rather than on a personal phone.
Attach any conversation to a guest, booking, room, activity session, or transfer. Open the booking and the discussion is there; open the discussion and the booking is one click away.
Any message becomes a task with an owner and a due date, with the original message still attached, so the context travels with the work instead of being summarised badly.
The outgoing shift records what the incoming shift needs to know, attached to the property and the date — read once at 6 AM, and findable again weeks later.
Search by guest, booking, channel, person, or date across everything ever said. The record belongs to the property, not to whoever was holding the phone.
Staff accounts are the ones already used for the rest of Artidal, so when someone leaves, their access to internal conversations and guest details ends with them.
What changes
Coordination happens in a messaging app the business does not control, where the right people are usually in the wrong group. Team channels put the message where the work is.
What the night shift knew is a scroll the morning shift never reads. Structured handover notes attached to the property and date are read once and found again later.
Seasonal workers finish in October and remain in the group chat for years, still reading guest details. Access is tied to employment and ends with it.
Names, allergies, room numbers and arrival times sit on private devices the business cannot wipe or audit. Keeping the conversation inside Artidal keeps the data where it belongs.
When a guest disputes what was agreed, there is nothing to check but somebody's phone. A searchable history tied to the booking answers the question in seconds.