Turn your customer-facing mailbox into an issue board. ServiceBeard syncs your emails directly to your issue tracker, letting you run a full service desk from your existing workspace. You can leverage the automation pipelines you’ve already set up without investing in expensive, per-seat helpdesk software. It's open-source, connects via standard IMAP/SMTP, and currently supports GitHub, GitLab, and Linear.
Finally a helpdesk tool that doesn't force per-seat pricing. Hooked it up to my Linear board over IMAP and had tickets flowing in within minutes, no need to migrate my whole team's setup.
Finally something that doesn't force me to drag my team onto yet another per-seat subscription. Synced our shared inbox to Linear in a few minutes, and the IMAP setup was straightforward enough that I didn't need to bother our admin.
Nice angle on using existing IMAP/SMTP plus the automation teams already have in GitHub, GitLab, or Linear instead of adding another per-seat support layer. One workflow question I would look for quickly as a user: how do you handle email threading and duplicate issue prevention when one conversation turns into multiple tickets or several teammates reply from the same mailbox?
@Joram good to hear it's on the roadmap. if it helps at all, the case I'd prioritize testing first is a thread where a customer replies twice in a row before anyone on your team answers - that's the one that tends to break naive read/unread and two-way sync logic the hardest, way more than plain out-of-order delivery.
Running a service desk out of Linear instead of paying per-seat for a helpdesk is exactly the tradeoff a small community/support team wants, especially self-hosted over IMAP. The loop I'd need to close before adopting: is the sync bidirectional — if I reply on the Linear issue, does that go back out to the customer over SMTP as an email, or is it inbound-only and I'm still answering from the mailbox? One-way would mean context lives in two places again, which is the exact problem I'd be adopting this to kill.
Getting stuff out of the inbox and into where work actually gets tracked is a problem I feel weekly. When ServiceBeard syncs a mailbox to the issue tracker, how does it decide what's a real issue versus a one-off reply or a thank-you, and can I keep a two-way link so a comment on the issue lands back in the email thread? The round-trip is the part that makes or breaks these
The "avoid per-seat helpdesk software" angle is the honest pitch here, Zendesk and Intercom pricing gets painful fast for small teams that just need email-to-ticket without the full enterprise platform. Curious what the actual setup time looks like for someone already on Linear.