Resolve what is done
Open is what still needs a person; Resolved is everything else. The customer sees nothing, and their next reply moves it straight back to Open by itself.
Know what still needs somebody, hand a conversation over with the context attached, and stop explaining customers to each other in a different app.
Without a way to finish with a conversation, every thread you have ever had sits in the same place and nobody can tell which still need a person. The ones that matter get lost among the ones that are done.
Left in the thread, where the rest of the context already is.
Heads up @dana — card on file bounced. Take payment on the day, do not invoice.Dana was told Resolved by Dana · a reply reopens itAll of them are about the moment somebody who was not there opens the conversation.
Open is what still needs a person; Resolved is everything else. The customer sees nothing, and their next reply moves it straight back to Open by itself.
A whisper sits in the thread where the context is, in yellow. It is stored apart from everything that sends, so there is no route by which one reaches the person it is about.
Type @ and a name. They get a notification in the app and an email, both linking straight to the conversation rather than dropping them at the inbox to hunt.
The handover note lives on the conversation it is about. No switching to Slack to explain which customer you mean, and no explanation that outlives the thread.
What used to be a message in another app, about a customer whose name the next person has to search for.
On the conversation, not in a channel. Whoever opens it next reads it before they reply.
@ a colleague and they are told, with a link straight to the thread.
It leaves Open. The team can see what is actually outstanding.
It reopens by itself. Nobody has to remember to check.
Resolving is a moment, and moments are what automations run from — so a survey or a follow-up can go out while the visit is still fresh.
No. Nothing is sent and nothing changes on their side. It is not blocking, archiving or deleting — it is a filter for your team, and their next reply reopens it automatically.
No. Whispers are stored separately from everything that sends, so there is no code path by which one becomes a message. That separation is the safety property: a note cannot be delivered by code that does not know it exists.
For everybody. That is the point — the team needs one answer to “does this still need somebody”. Two people pressing Resolve at the same moment resolves it once.
They get a notification in the app and an email, both linking straight to that conversation. The email does not quote the note: whispers are what one colleague says to another about a customer, and the candid ones are the useful ones — putting that text in an email puts it somewhere nobody chose.
Only the person who wrote it. A note is somebody's words to their colleagues, and letting anybody remove anybody's turns the record of a handover into something that can be quietly edited afterwards.
No. A mention is a link to a customer conversation, so only people who can already see that project can be tagged.
Not generally — but it replaces the part of it that is people explaining customers to each other. The note lives on the conversation, so nobody has to say which customer they mean.
Build two-way blue-bubble conversations into your product or agent.
Use a complete shared conversation platform without writing code.
Call from your blue line without carrier Spam Likely labels.
Call any dialable number from your Miss Blue business line.