There is a special kind of noise in work chats: short replies that add nothing to the content but overload the dialogue.
Ok
Understood/Accepted
Yeah
Inprogress
Yes
I see
Thank you
Such messages are normal as they are. They confirm that a person saw the task, agreed to complete it, checked it, and took it to work. The problem begins when there are 20 people in the conference, and an important message is drowned in hundreds of “OK”, “yes”, “in progress”, etc.
MyChat’s quick reactions solve this neatly: the confirmation remains, and the unnecessary message does not appear in the message history.
The shortest way to react: double-click on a message
If quick double-click reactions are enabled in the settings, everything works very simply: double-click on a message to give it a thumbs up.
This is helpful for cases when you need to quickly show: “seen”, “in work”, “fixing”. We see how many people react: hover the mouse cursor, see who and when. It’s effective, especially in conferences, where the manager writes a short order like:
A meeting is at 5:30 p.m. Attendance is mandatory, it’s important, 10-15 minutes.
Everyone involved leave a reaction. The feed remains with one message and a clear picture around it, rather than a long tail of identical responses. All win: the boss doesn’t annoy anyone, and communication is established.
Quick keyboard reactions
This method is even more interesting and faster: you can send a short character or combination to a chat, and MyChat will turn it into a reaction to the last relevant message in the current chat, not a new message. No need to click around with the mouse.
For example:
| Type | Reaction |
|---|---|
| + or ++ | thumbs up |
| – or — | thumbs down |
| * | heart |
| ! | light smile |
| !! | grinning face |
| !? | amazement |
| .. | eye, “seen” |
| v or V | check mark |
| x or X | cross |
| 100 or 100% | “100%” |
| >> | “writing” |
| [] | “beer” for informal chats |
A person types a familiar short response, and MyChat understands the intent. This is similar to real-life behavior: many people respond with pluses and minuses anyway.
What does this look like in real work?
Let’s imagine a conference of the on-duty shift.
The operator writes:
Have you checked all new features?
Employees don’t write ten identical “checked” in the chat. They react:
- x — does not work for me.
- 100% — all good.
- + — everything is OK.
- .. — still checking.
As a result, the important message remains at the center of attention, and the reactions around it provide a quick status. It’s closer to a work board than a cluttered chat. And it’s visually easy to see the whole picture.
Why is this better than “OK” in a separate message
First, reactions do not break the context. If there are ten pluses under the message, then it is clear what they relate to. If in a minute there are ten “OK” messages in the feed, then files, questions, and new topics can be lost between them.
Second, reactions are easier to view. The brain processes icons instantly: agreed, disagreed, seen, and accepted. This is especially useful on shifts, in technical support, in production, and in distributed teams.
Third, it reduces the social pressure to “be forced to write something”. Sometimes it is enough for a person to show presence and agreement. Reaction does this without unnecessary text and stress for introverts.
Access rights and clean formatting
Quick reactions are controlled by settings and rights. If reactions are prohibited in a group, MyChat will not allow you to silently bypass the restriction using the “+” symbol. This is important for companies where chat is used not only as informal messaging, but also as a work journal.
There is another nice detail: if the same reaction is already set, MyChat will not endlessly duplicate it after subsequent clicks. In normal work, this is perceived naturally: click to set it, accidentally click the same reaction — the feed does not turn into a mess.
It is easy to remove an accidentally set reaction: just click on it again with the mouse. Alternatively, if you do not need the feature, disable it in the program settings (Alt+O):
Where is it especially useful?
Quick reactions work well where you need to quickly collect “seen/accepted/checking” statuses:
- shift and dispatch;
- IT support and administrators;
- sales department, where changes to the client need to be confirmed quickly;
- accounting before deadlines;
- production conferences;
- teams, where there are many short operational messages.
If the message really needs a response, a reaction doesn’t get in the way. It simply closes off those cases where a response would be a one-syllable word.
Related features
Quick responses work perfectly with F4 in conferences: a response shows voluntary feedback, and F4 helps you check whether the message was delivered and read. And if there was an error in the short response, see the article about quick message editing.