Ubirimi ubirimi
CHT Hallway

The hallway is in the house. It is not the archive.

Chat is for deciding, not for storing the decision. Workspaces, group channels, direct messages. Members you manage. History fetched and saved through the Ubirimi API so it stays with the tenant. Then write it on PLATFORM-184 or DOC-12 before Thursday buries the useful sentence.

Start a 15-day trial Why Chat
Container
Workspaces
Rooms
Channels & DMs
History
Stays in the tenant
Job
Decide, then file

Why Chat

Keep fast conversations close to the work without mistaking chat for documentation.

Teams need a quick place to coordinate, but another messaging vendor adds another identity, another offboarding step, and another silo. Chat keeps everyday conversation inside the Ubirimi tenant and makes the boundary between discussion and durable knowledge explicit.

  1. 01
    Coordinate without leaving the suite

    Use workspaces, group channels, and direct messages with the same people who already work in Ubirimi.

  2. 02
    Keep membership under control

    Manage workspace and channel members as part of the tenant instead of maintaining a disconnected company directory.

  3. 03
    Put durable outcomes where they belong

    Discuss quickly in Chat, then record the action on a Yongo issue or the decision on a Documentador page.

CHT-WS

A workspace is the building. Channels are rooms.

Create a workspace, manage members, leave when you are done. The company hallway is not a personal Slack you cannot turn off when someone leaves.

  • Create & leave A workspace is an object you can exit. Offboarding is not “please remember to remove them from the other chat”.
  • Members Who is in the building. The same people who already have a Yongo account.

CHT-CH

Group channels and one-to-one messages.

Create a channel, rename it, leave it, manage members. Direct messages when it should stay small. #release is a room, not a product.

  • Group & direct The team channel and the quiet DM. Both in the same workspace.
  • Rename & membership Rooms change name. People join and leave. The history does not move to a private export.

CHT-MSG

Messages are fetched and saved in the tenant.

Persistence goes through the Ubirimi API. The scrollback is not a third-party inbox you will lose in a procurement cycle.

  • Fetch & save GetMessages, SaveMessage — the UI talks to your suite, not a chat island.
  • Then file it The best sentence in last Thursday’s channel is already gone unless you put it on a page or a ticket. Chat is honest about that job.

Same house

Talk here. Keep it on the ticket or the page.

YNG

Yongo

PLATFORM-184 is where the freeze becomes an issue, not a scrollback.

DOC

Documentador

DOC-12 is where the runbook survives. Chat is how you noticed it was wrong.

ANS

Answers

If the same question comes twice, it is not a channel topic. It is a thread with votes.

UBI

The suite

No separate chat vendor to forget on offboarding.

Index

Everything in this hallway

  • CHT-1
    Workspaces Create a workspace, manage members, or leave when you are done.
  • CHT-2
    Channels Group channels and direct messages, with rename and membership controls.
  • CHT-3
    Messaging Fetch and send messages through the Ubirimi API so history stays with the tenant.
  • CHT-4
    Team presence Talk in context instead of bouncing to a disconnected tool.

The deal

Chat is not an add-on SKU.

The hallway ships with the suite. Fifteen days, no card on the form.

Create an account See pricing

  • +Workspaces and membership you control
  • +Group channels and direct messages
  • +Message history stays with the tenant
  • +Updates stay free