Team chat with channels, direct messages, and video calls. Already connected to your files, your schedule, and your team.
Threads, voice and shared files on the same member model and the same file store as everything else your business runs on. Nothing to provision, nothing to connect.
Team chat that is part of the system, not beside it.
Equipo does not keep a second copy of anything. Its messages are the internal slice of the same store the customer conversations are written to. Its people are the account member model, not an imported user list. Its files are the account's files, tagged to a channel rather than uploaded twice. Its calls are the platform's own meeting and calling engines rendered inside the thread. There is nothing to connect, because nothing was ever separate.
0
Notification categories you tune yourself
0
Channel privacy states, open or private, nothing else
0
Actions on every person in the directory
0
KPIs computed live from the messages
Channels, threads and direct messages. One stream.
The screen your team sits in all day. Conversations on the left with unread counts and presence dots, the open thread on the right, and the composer under it. Rich text, reactions, pinned messages, edit and delete your own, a live typing indicator and search across the list. The header carries voice, video, members and files.
A reply stays with the message it answers. The feed stays clean.
A file shared in a channel is stored once, in the account file store.
A mention and an ordinary message are separate notification categories.
Team conversations can never return a customer thread.
Open, private and archived. One channel registry.
Every channel the account has, in one browsable list with its topic, its member count and a way in. Create one from the same screen. Rename it, retopic it, flip it between open and private, or archive it once it has done its job.
An open channel is visible to everyone in the account, a private channel is invite only, and there is no third state.
Archiving drops a channel out of the live list and keeps everything said in it.
Purview creates, renames and archives the same channels, from the screen where the business unit is set up.
A message is a message. A call is a call.
Voice and video start from the conversation you are already in. No invitation, no room to book, no link to send to the people standing in the room with you.
Video, voice and a room that opens where you already are.
A call is not a separate product with its own invitation, its own link and its own login. It is a button on the conversation header, and the call belongs to the channel it started from. Mute and the running duration sit in the header while it is up.
Voice and video are two buttons on the conversation header, with no invitation to send and no link to distribute.
Starting a call posts a line into the conversation, so somebody who was away can see that it took place.
Every row of the people directory carries message, voice and video.
Incoming call is the one notification category marked critical, so it is the only one that rings through.
Every shared file is the file. No second copy.
When somebody shares a document in a channel it is stored once, in the account file store, and tagged to that channel. Upload straight to a channel from this screen, with a type glyph and a real size on every row. The file a message points at and the file the rest of the business works from are the same object.
What the message carries is a reference to the one file, never a second copy of it.
A file shared here counts against the same account storage as every other file.
The files screen groups every shared file by the channel it was shared in, with who shared it and when.
The conversation, the call and the file all point at the same person. Here is who that is.
The directory is the team. Same database, same people.
The people screen is not an address book Equipo keeps. It is the account member model, filtered to the people who hold Equipo, with live presence on every row: online, away, busy or offline, set by you or inferred from your activity, with a custom status in your own words. The person you send a direct message to is the same person the schedule, the payroll and the assignment lists are about.
The list of people you can message is the same member table the rest of the platform reads.
Three actions on every person, without leaving the directory.
Pick your days and your hours, and outside them you show as away in your own timezone.
Set do not disturb until a moment rather than until you remember to turn it off.
Measured from the messages, not from a guess.
Channel governance, a usage dashboard computed on read, and notification preferences that belong to each person rather than being set for everyone at once.
Channel governance, usage analytics, notification controls.
What the person who runs the account needs: the channel list with rename and archive on every row, a usage dashboard computed from the messages themselves, and preferences that belong to each person rather than being imposed on everyone at once.
- #general1,842
- #shift-handover1,306
- #maintenance894
- #suppliers612
- #finance178
A manager view of the same channel list, with rename and archive on every row.
Notification settings belong to the individual, not to the account.
Channels, direct messages, messages over thirty days and active people over seven, with a fourteen day volume bar and the busiest channels under them.
One bell for the whole account, and you decide what rings it.
A message, a mention, a channel invitation, a missed call and an incoming call are five separate categories, and each one is yours to tune per delivery channel. Nothing here emails or texts you: team chat reaches you in the app or on your phone, and the incoming call is the only category marked critical, so it is the only one that rings through. The centre it files into is the same one carrying your mail, your customer conversations and your meetings, because Equipo did not bring its own.
The team is talking. Here is what it is talking on top of.
Your team is already hired. Equipo knows.
The directory is the member model. When you hire someone and grant them Equipo, they appear in the chat. When they leave, they disappear. There is no user provisioning step, no import, no sync, and no directory that can fall out of step with the truth.
A file shared here is a file everywhere.
The attachment goes to Depot, tagged to the channel. It is the same file the rest of the business works from, counted against one storage quota. A document does not get duplicated into a chat silo that nobody outside the conversation can reach.
A call starts where the conversation is.
Voice and video are buttons on the conversation header. The meeting engine mints a room inside the thread. Nobody leaves the chat to join a call, and a line in the channel records that it happened.
Internal and external are one store.
A message to your team and a message to your customer are the same object, rendered by the same engine, stored in the same tables. Link shows both. Inbox shows both. Search finds both. Equipo is the internal slice of one message store, not a second product with its own data.
The Team
Equipo → Workforce · Purview
The directory is the account member model, listing the people who were granted Equipo when they were hired, and every administrator. Nobody is provisioned twice and no second list can fall out of step with the first.
Files
Equipo → Depot
A file shared in a channel is stored once and tagged to that channel, so the document a message points at is the same object the rest of the business works from, counted against one storage allowance rather than two.
Calls
Equipo → Live · Voice
Video asks the meetings engine for an instant room and renders it inside the conversation, and voice connects through the shared calling engine, both resolving the person by the same user id the presence dot uses.
One Message Store
Equipo → Link · Inbox
Team messages are the internal slice of the same tables the customer conversations are written to, rendered by the same renderer, which is why the unified inbox can show a colleague and a customer without either engine copying the other.
Notifications
Equipo → Notification Centre
A message, a mention, a channel invitation, a missed call and an incoming call arrive in the same bell as mail, calls and meetings, each a category the individual can tune for themselves.
Search
Equipo → Platform Search
Every message is indexed as it is written and deep links back to its conversation, so the sentence somebody remembers is findable from the same box that finds a file, a record or a document.
Governed from the same place as everything else.
Purview creates, renames, and archives channels. Channel governance is part of business-unit setup, not a separate admin console in a separate product. The same place you set up the team's schedule, identity, and permissions is where you set up their communication.
The same channels on the device the team actually carries.
Conversations, direct messages and calls reach you in the app or on your phone.
Secured like the rest of the account.
Every read and write is scoped to your account, and removing somebody from the member record closes their chat, their files and their calls in one action.
Where Equipo touches everything else.
7 of these 8 connections are in your plan today. The rest stay visible so you know the instrument is there before you need it.
The people you can message are the shared member model, and the Equipo grant written when a person is hired is what puts them in the directory.
A file shared in a conversation is a Depot asset tagged to that channel, not a second copy in a chat store.
The video button creates a Live instant meeting and renders the room inside the conversation rather than sending anyone to a link.
A voice call from a conversation or a directory row connects through the shared internal calling engine, which resolves the person by user id.
Equipo writes the internal slice of the same messaging tables Link reads, through the same message renderer, and Link Team Config opens Equipo channels and settings.
Inbox carries the conversation with a customer and Equipo carries the one with your own team, on the same tables under a different audience type.
Built for these industries
2 customer types run Equipo today.
No setup cost. Pay when you start using.
Team chat for internal work.
Recommended for you
Use one app or many. Works well together.
Everything included in Calisto Equipo.
- Two-pane surface: conversation list and the open thread side by side
- Channels and direct messages in one list, or filtered to direct messages only
- Search across the conversation list
- Unread counts on the list, in the rail and on the platform menu badge
- Threaded replies with a reply count on the parent and a slide-in reply panel
- Emoji reactions on any message
- Pinned messages
- Edit and delete your own message, refused on anybody else
- Rich text composer with a file attachment button
- Typing indicator, live over the stream
- Members and files panels that open over the thread
- Deep link to any single conversation by id
- Open channels, visible to everyone in the account and joinable from the browser
- Private channels, invite only and hidden from non-members
- Channel browser with member count, topic and a join action per row
- Create a channel with a name, a description and a visibility in one dialog
- Edit name, description and visibility through the shared identity dialog
- Archive a channel: it leaves the live list and keeps its history
- Manager view of the same list with archive on every row
- The same channels administered from Purview through Equipo own API
- No permission tiers: open versus private is reachability, not access control
- Directory built from the shared account member model
- Listed only for members holding an Equipo grant, plus every administrator
- Search by name or email
- Four presence states: online, away, busy, offline
- Visibility on automatic, or held at busy, away or appear offline
- Custom status message with an emoji
- Do not disturb until a chosen moment, self clearing
- Working hours by day, start, end and timezone, appearing away outside them
- Message, voice call and video call from any directory row
- Presence dots on the direct message rail
- Voice and video buttons on every conversation header
- Video creates an instant meeting room and renders it inside the conversation
- The meeting is created against the conversation it started from
- Running call duration with mute and end in the header bar
- Starting a call posts a line into the thread
- Click to video from a directory row opens the direct message and starts the call
- Callee resolved by user id, the same key presence writes under
- Capability buttons always visible, with an empty state on failure rather than hiding
- A shared file is an account file store asset tagged to the channel it was shared in
- Attachment upload and channel tagging in a single action from the composer
- Files screen listing every channel scoped file, grouped by channel
- Shared by attribution, timestamp and size on every row
- Type glyphs for documents, images, audio and video
- Upload straight to a chosen channel from the files screen
- Sending a message also deposits the conversation into the file store gravity
- One account storage quota, not a second chat allowance
- Server sent events stream per conversation
- New message and typing frames published on send
- Cross replica delivery over pub/sub when a cache is configured
- A poll underneath the stream so a dropped connection never loses a message
- Conversation list refresh on a twenty second cycle
- Every message indexed into the platform search index on write
- Search results deep link back to the conversation
- Indexing is best effort by contract and can never fail a send
- Five categories: new message, mention, channel invitation, missed call, incoming call
- Incoming call is critical and transactional, so it rings
- Mentions fire a different category than ordinary messages
- Delivered into the same notification centre as mail, messaging, calls and meetings
- Preferences per person and per delivery channel
- Notification firing is non-blocking and never delays a message
- Channel management screen with the identity dialog and archive per row
- Four totals: channels, direct messages, messages over thirty days, active people over seven
- Fourteen day message volume series
- Busiest channels over thirty days
- Computed from the message tables on read
- Presence configuration screen
- Notification preferences screen
- Shared business identity and contact configuration rendered inside Equipo
- Quick actions into channels, people, presence and notifications
- The internal slice of the same messaging tables the external engines write
- Internal pinned at the route boundary, never trusted from a query parameter
- Channel versus direct message carried on existing columns, not a parallel schema
- Threading carried by a parent message reference
- One identity: every person is a user id inside an account
- Every read and write scoped to the account
- The conversation list narrows to the active business unit and reloads when it changes
- No intra-account roles, because Calisto has none
- Workforce (the member model, and the grant that puts a person in the directory)
- Depot (shared files, and conversation gravity)
- Live (the instant meeting room a video call renders)
- Voice (the shared calling engine a voice call connects through)
- Link (the same messaging tables and the same message renderer)
- Inbox (the external half of the same conversation store)
- Purview (channel administration and business unit scope)
- University (granted alongside Equipo in the same hiring step)
Questions about Calisto Equipo
Because the team is already in the system. Equipo runs on the same member model and the same file store as everything else, so there is nothing to provision, no second directory to keep in step and no file that exists in two places.
No. One message store sits behind team chat and the customer channels, which is why a conversation can be read in Link as one stream per person rather than as five apps.
They are removed once, on the member record, and that closes chat, files and calls together. The usual failure with a bolted-on chat tool is the account nobody remembered to disable.
Channels and messages import where the source exposes an export. Most teams bring the last year and archive the rest.
The pricing section on this page reads the live catalogue and is the authority. There are no per-seat fees, which is usually the reason a business rationed chat accounts in the first place.
Yes, exportable in standard formats along with the shared files.