I am opening this topic to request a feature regarding the “Reply in thread” (inline threading) option in Google Chat, which is currently causing significant communication gaps within our organization.
While inline threading might work for some teams, it leads to scattered parallel conversations in others. Critical operational updates often get buried inside sub-threads, causing team members to miss important context and instructions.
The ideal solution would be allowing room creators or managers to define this setting per chat (group or space).
We really need a configuration toggle when creating or managing a Space/Group to disable inline threading and enforce a single, linear conversation flow for that specific chat when needed.
Is anyone else struggling with this room-by-room tracking issue? Please upvote and leave your comments so the product team can see this request.
This was discussed before Google changed the old way of having all messages in the stream (when shutting down Google+ and migrating everyone to Chat), and Google decided that was not how they wanted it. It is alsonot a technical problem; it’s a people problem.
If everyone follows the simple instruction to always reply in a thread, this problem goes away.
Nobody misses any relevant comments, as they are always inside the same thread, and not spread across separate threads.
Everyone enables notifications for all posts, and they will see everything, regardless of where it is posted.
Use the tool as it is built, instead of breaking the logic.
Thanks for the historical context, but with all due respect, “just because it works for you doesn’t mean it works for everyone.” Shifting the blame to a “people problem” ignores how real-world businesses operate across different communication dynamics.
First, an Instant Messenger is NOT a social network. Conflating the workflow of Google Chat with the legacy architecture of Google+ is a fundamental misconception of business communication. Social feeds are for browsing; corporate chats are for immediate, often time-sensitive operations.
To give you a real practical example: in Brazil, we have a legally mandated workplace safety and compliance committee called CIPA (Internal Commission for Accident Prevention). In our “CIPA” Space, inline threading works beautifully. We use it all the time to track distinct safety audits and specific topics. It’s great there.
However, in fast-paced operational channels, it is a completely different story. Because the “Reply in thread” icon is positioned right next to the “Quote in reply” option, users frequently click it by accident. In a fast communication flow, this mistake causes critical alerts to get buried inside sub-threads, creating severe communication blind spots. Expecting dozens or hundreds of stressed operational employees to never misclick a UI icon is unrealistic.
Once again, I am NOT suggesting Google should kill the feature or “break its logic.” I am asking for flexibility. Give Space owners and managers the autonomy to choose the conversation flow that fits their specific team’s needs. One size does not fit all.
That is exactly why others have requested to either have the button for “quote in reply” removed, or at least moved, so people don’t click it by mistake.
On mobile/touch devices it’s less of an issue, since tapping the post brings you into the thread, and reply as qoute takes more conscious effort.
Sure, adding an option among which features are available for members would be nice.