Personal chats that feel like home
Heyno gives every person their own quiet, private thread, and gives the assistant a place to stand inside it.
Most work software treats a message as a record. Heyno treats it as a place. A personal chat in Heyno is a single continuous thread between you and one other person, with your assistant sitting in it, able to read what was agreed, produce the thing that was asked for, and stay quiet the rest of the time.
It looks like the messaging you already use. It behaves like a colleague who has read everything.
What a personal chat is
A personal chat is a durable one-to-one thread. It does not expire, it does not fragment into channels, and it does not lose the file you sent four months ago. Everything that has ever passed between two people lives in one scrollback: messages, attachments, voice notes, decisions.
The design goal was that opening a chat should feel like walking back into a room you were already in, not like launching an application.
One thread, one memory
The assistant reads the thread as continuous context rather than as the last few messages. When you say “send them the revised version,” it knows which version, because it watched the revision happen.
Memory is scoped to the thread by default. What you discuss with one person does not silently become context in a conversation with someone else, but you can promote something into shared or workspace memory when it should apply everywhere.
Thread memory is the default scope. Shared and workspace memory are explicit promotions, and every promotion is visible in the thread where it happened.
The assistant is a participant
Heyno does not bolt a chatbot onto a messenger. The assistant is addressable inside the thread, sees the same history both people see, and can act without either person leaving the conversation: draft the reply, build the document, price the item, put the thing on a calendar.
Where an action leaves the account, it stops and asks. The approval happens inline, in the thread, so the person approving can see exactly what prompted it.
Privacy inside a shared workspace
A workspace is shared; a personal chat is not. Personal threads are not visible to administrators by default, are not indexed into team channels, and are not used to answer other people’s questions.
Where an organization requires retention or legal hold, that is configured explicitly and shown to participants rather than applied silently.
What it replaces
In practice Heyno collapses three tools: the messenger where the conversation happened, the drive where the file ended up, and the assistant window where the work got done. Keeping them apart is what creates the “which version did we agree on” problem.
One thread, one memory, one place the work is produced.
More in Communicate