TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ask HN: How to manage shared Email inboxes?

3 点作者 sudders超过 6 年前
Next to our private company email addresses, we have 2 shared email inboxes (info@...) that are being worked on by multiple people at the same time.<p>This is currently done in GSuite, simply by multiple people logging in at the same time. The volume of the emails in these inboxes are starting to get out of hand, and we are looking for a way of managing this differently.<p>The conversation view in Gmail is becoming somewhat of a hassle for certain situations, as its not always clear when a client replies to an email multiple times in a conversation flow, to what the client was replying in the first place. We tried not using conversation folding at all, but this is completely unmanageable as we are receiving too many emails a day.<p>I was wondering what the experiences of HN is with similar situations, Im mostly interested in self-hosted, cloud applications or addons for GSuite. As I do no want to install software on computers.

2 条评论

mtmail超过 6 年前
Next step is software allowing one user to assign tasks (emails) to another and which keeps one thread per customer. <a href="https:&#x2F;&#x2F;frontapp.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;frontapp.com&#x2F;</a>, <a href="https:&#x2F;&#x2F;missiveapp.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;missiveapp.com&#x2F;</a>, <a href="https:&#x2F;&#x2F;www.intercom.com&#x2F;inbox" rel="nofollow">https:&#x2F;&#x2F;www.intercom.com&#x2F;inbox</a> and such.
ktpsns超过 6 年前
I made good experiences with issue trackers. Kind of leading is probably OTRS (<a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;OTRS" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;OTRS</a> -- it&#x27;s open-source despite the horrible website which I won&#x27;t link here) and RT. However, also software like <a href="https:&#x2F;&#x2F;trac.edgewall.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;trac.edgewall.org&#x2F;</a> and <a href="https:&#x2F;&#x2F;www.redmine.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.redmine.org&#x2F;</a> provide E-Mail interfaces which work quite well.<p>The thing with issue trackers is: They are made exactly made for a use case as you describe it. They excel for managing the contact &quot;workflow&quot; with clients, especially if different people work on the same &quot;inbox&quot;.<p>In my experience, Introducing an issue tracker to a team always took some days to weeks of familiarization, but it always paid off.