Chat is in the areas menu, under Team conversations. It is direct messaging between people in your organisation, inside DOK Genius.
What it is for
The conversation that happens around a case. "Is this the right certificate?" "Did the broker ever send the second form?" "I'm handing you claim 0184, the estimate looks off."
Those exchanges happen anyway. The question is only whether they happen where the work is or in a separate application with a separate history — and a decision explained in a chat thread nobody in the organisation can find later is a decision with no explanation.
What it is not
It is not a comment on a dossier. Cases carry their own comments and their own state history, and those are part of the record. Chat is between people.
The practical rule: if it explains a decision, it belongs on the case. If it is asking a colleague a question, it belongs here. A rejection reason typed into Chat is a rejection reason nobody will find.
Using it
The left side lists your conversations, with a search box. The right side is the conversation you have open.
Two counts at the top: how many conversations you have, and how many unread messages are waiting.
- Search for a colleague by name to start or resume a conversation with them.
- Write message focuses the composer on the conversation you have open.
- Refresh re-reads the list.
Conversations are between people in your own organisation. Like everything else in the product, another tenant's people are not reachable and not visible.
The one thing it does not tell you
There is no presence indicator, and its absence is deliberate.
An earlier version showed a count of contacts who were "online". That figure was computed from the person's display name rather than from any signal about whether they were actually there — so it was a count of nothing, presented as if it meant something.
It was removed rather than repaired, because there is no presence signal in the product to repair it with. A number that looks like information and is not is worse than a blank space, and this is the clearest small example of it in the whole application.
So: nobody in Chat is shown as available. If you need to know whether a colleague is at their desk, Chat will not tell you, and it does not pretend to.
What you should have now
- One conversation with a colleague.
- A rule agreed with your team about what goes in Chat and what goes on the case — the distinction above is the one worth writing down, because it decides what is findable in a year.