The communication layer of Soupy.
The handover that everyone can find.
Give the team a shared place for conversations, shift updates and linked operational alerts. Keep the discussion beside the work it belongs to.
In the product today
Operational channels, direct conversations, threads, reactions, pins, files, mentions and message search that respects the person’s access.
See what’s nextTeam channels and their latest updates, showing the people and operational context attached to each conversation.
Current workspace layouts with sample data. Nothing is saved or sent.
08 · Work area
Messages
Team conversations with the shift and workplace context attached.
Team channels
Based on the current Messages workspace. Search and switch views using sample records. Nothing is saved, sent or charged.
On the other side of the shift
Less friction. More getting on with it.
- 01
Keep internal conversations out of scattered group chats.
- 02
Let Soupy post useful operational events into the right channel.
- 03
Open the underlying event, shift or issue from the message.
What’s included
Made for the job.
The practical details behind the promise. Built around the people doing the work, and connected to the information they need.
- 01
Operational channels
Publish organisation, venue and event updates to the people who can reach that scope.
- 02
Direct and group conversations
Use channels for teams and topics, and start direct conversations with people from the shared directory.
- 03
Operational messages
Let Ticketing, Rotas, Maintenance and other Soupy work areas publish useful linked events.
- 04
The right people, in context
Link the right Person and workplace scope without rewriting employment, contract or payroll history.
- 05
Optional shift context
Show an upcoming shift or brief only when Rotas is separately enabled and the person has the required access.
Part of the bigger picture
The context comes with it.
The guest, the venue, the team. Useful information should follow the work. Messages connects to shared records, with access controlled for your organisation and your people.
A clear picture
Today. And what’s next.
Operational channels, direct conversations, threads, reactions, pins, files, mentions and message search that respects the person’s access.
Messages follow channel membership and workspace access. Changing a conversation does not change a People or operational record.
Good questions
Messages FAQs.
Is Messages part of Rotas?
No. Messages is a separate product with its own entitlement, routes and capabilities. Rotas may publish linked updates when both products are enabled.
Does Messages replace People?
No. People owns employee identity, employment and documents. Messages only references that canonical person when someone participates in a conversation.
Can someone use Messages without managing People?
Yes. Viewing conversations, posting and managing channels are governed independently from People administration.
Does the product preview notify real staff?
No. It demonstrates the workspace boundary without sending a message or changing a People record.
Start with the pressure point