Google Workspace has the pieces for a shared inbox, why no solution, Google?

1•mareksotak•2mo ago

Google Workspace has had all the primitives needed for a proper shared inbox for years... labels, filters, threads, Drive, permissions, Groups,... Everything you’d expect as the foundation for a collaborative support workflow already exists.

But for some reason, Google has never shipped an actual shared inbox product that ties these pieces together.

Most teams I know end up with the same workaround: forward emails out of Gmail into yet another vendor. And with each hop, another third party gains access to customer data. It’s a strange situation, considering Workspace is supposed to be the communication core for companies.

Recently Google “announced” a shared inbox feature, but after digging into it, it looks like the same mailbox delegation system that has been around for years, simply repackaged as something new. Google does this surprisingly often.

What’s frustrating is the announcement itself, and the fact that Google has already built 95% of what’s needed for a real shared inbox. The last 5%, the part that would make it coherent and genuinely useful, never seems to arrive (like with other use cases).

That’s why we don’t really use Google Workspace to get actual team work done. All the pieces exist, but they’re not connected into anything that supports real collaboration or aligns with how modern teams actually work.

I’m not sure what the product philosophy behind Workspace is these days, but from the outside it feels increasingly disconnected from how teams actually work, and often seems to be trying to catch up in the wrong way, rather than being innovative. Has Google lost the plot here?

Comments

mareksotak•2mo ago

For context, this post comes out of a mix of frustration and curiosity. I work in product, and what drives me a bit crazy here is that all the foundational pieces for a shared inbox are sitting right there in Workspace. You can almost see how it could click together with "relatively small connective tissue" (of course, easy to say, I know nothing about their architecture).

It’s genuinely hard to understand the product reasoning when the missing pieces seem more about integration than invention.

Would actually love to hear from people who’ve worked inside Google or on Workspace: What stops this from becoming a real product targeting use cases people want? Is it technical debt, org structure, misaligned incentives, or something else?

akagusu•2mo ago

They don't care about this particular feature and many other features because this is not how they make money. The lack of this feature has zero impact in Google revenue and having or not having this feature also has zero impact in new users signup.

mareksotak•2mo ago

I get the revenue point, but it doesn’t entirely feel that way from the outside. Google does try to sell Workspace as a coherent, modern collaboration suite, yet some of the decisions make it look like the product direction isn’t really thought through end-to-end.

What adds to the confusion is how often Google seems to re-surface or re-announce features that have been in Workspace for years, even though they’re not really polished for what teams need today or anywhere near on par with the competition. The recent “shared inbox” announcement is a good example: it’s basically mailbox delegation with a new coat of paint, but still not viable for real shared workflows.

And I keep seeing comments from people saying things like: “We’re looking for this feature so we can finally move off Microsoft 365.”

So there is demand. And not just for this feature alone. There are multiple areas where users clearly want functionality that keeps them inside Workspace instead of pushing them toward third-party tools or competitors’ ecosystems.

akagusu•2mo ago

Google is in a position where it doesn't need to offer good products; an ok-ish product is more than enough to keep people using it and the "re-announce features" is the marketing part that keep people signing up for the service; once they have signed their data is trapped and they will keeping using the product not because the product is good, but because it is so hard to leave.

Study confirms experience beats youthful enthusiasm

The Big Hunger by Walter J Miller, Jr. (1952)

The Genus Amanita

We have broken SHA-1 in practice

Ask HN: Was my first management job bad, or is this what management is like?

Ask HN: How to Reduce Time Spent Crimping?

KV Cache Transform Coding for Compact Storage in LLM Inference

A quantitative, multimodal wearable bioelectronic device for stress assessment

Why Big Tech Is Throwing Cash into India in Quest for AI Supremacy

How to shoot yourself in the foot – 2026 edition

Eight More Months of Agents

From Human Thought to Machine Coordination

The new X API pricing must be a joke

Show HN: RMA Dashboard fast SAST results for monorepos (SARIF and triage)

Show HN: Source code graphRAG for Java/Kotlin development based on jQAssistant

Python Only Has One Real Competitor

Tmux to Zellij (and Back)

Ask HN: How are you using specialized agents to accelerate your work?

Passing user_id through 6 services? OTel Baggage fixes this

DavMail Pop/IMAP/SMTP/Caldav/Carddav/LDAP Exchange Gateway

Visual data modelling in the browser (open source)

Show HN: Tharos – CLI to find and autofix security bugs using local LLMs

Oddly Simple GUI Programs

The New Playbook for Leaders [pdf]

Interactive Unboxing of J Dilla's Donuts

OneCourt helps blind and low-vision fans to track Super Bowl live

Rudolf Vrba

Autism Incidence in Girls and Boys May Be Nearly Equal, Study Suggests

Wellness Hotels Discovery Application

NASA delays moon rocket launch by a month after fuel leaks during test