# InboxBarn

> InboxBarn is a multi-platform help desk for small teams. It unifies email, Discord, Slack and an embeddable web chat widget into one shared inbox, and delivers every reply back on the channel the customer originally used — in their existing thread. Teams can also work conversations from Discord, Slack, Microsoft Teams or Telegram instead of the dashboard. Pricing is flat, not per-agent: free forever for up to 5 teammates (every channel included), $5/month total for up to 25.

Key facts:
- Sources (where customers write in): email, Discord, Slack, website chat widget.
- Team-side destinations: web dashboard, Discord, Slack, Microsoft Teams, Telegram, email.
- Conversations are routed by category (general, VIP, billing, sales); each destination subscribes to categories.
- The reply invariant: wherever an agent types, the customer receives the answer on their original channel and thread.
- Pricing: Homestead — free, up to 5 team members, every channel. Big Barn — $5/month flat, up to 25 members, removes widget branding. Enterprise — custom.

## Core pages

- [Home](https://inboxbarn.com/): what InboxBarn does and how the two-way bridge works
- [Pricing](https://inboxbarn.com/pricing): plans, comparison table, pricing FAQ
- [Docs](https://inboxbarn.com/docs): product documentation overview
- [About](https://inboxbarn.com/about): who builds InboxBarn and why
- [Contact](https://inboxbarn.com/contact): how to reach the team
- [Changelog](https://inboxbarn.com/changelog): what shipped, month by month

## Channel routing guides

How to route each customer channel into each team-side tool:

- [Email to Discord: Route Support Email into Discord](https://inboxbarn.com/blog/email-to-discord): Send every message from your support inbox into Discord as a live conversation, and reply from anywhere. Customers still get answered by email. Set it up in 3 steps.
- [Email to Slack: Send Support Emails into Slack](https://inboxbarn.com/blog/email-to-slack): Turn your support inbox into Slack messages your team can answer in seconds. Replies go back by email automatically - no portal, no copy-paste. Set up in 3 steps.
- [Email to Microsoft Teams: Route Support Email into Teams](https://inboxbarn.com/blog/email-to-microsoft-teams): Bring your support inbox into Microsoft Teams as channel conversations, with replies sent back by email. Built on the Graph API. Set it up in 3 steps.
- [Email to Telegram: Route Support Email into Telegram](https://inboxbarn.com/blog/email-to-telegram): Forward your support inbox into a Telegram group as a topic per conversation, and reply from your phone. Customers still get answered by email. Set up in 3 steps.
- [Discord to Slack: Bring Discord Tickets into Slack](https://inboxbarn.com/blog/discord-to-slack): Let community members open tickets in Discord and answer them from Slack, where your team works. Replies go back to Discord automatically. Set up in 3 steps.
- [Discord to Email: Answer Discord Tickets from Your Inbox](https://inboxbarn.com/blog/discord-to-email): Let members open tickets in Discord and answer them from your email inbox - no Discord tab to babysit. Replies post back to Discord. Set it up in 3 steps.
- [Discord to Microsoft Teams: Route Discord Tickets to Teams](https://inboxbarn.com/blog/discord-to-microsoft-teams): Let your community open tickets in Discord and answer them from Microsoft Teams. Built on the Graph API; replies go back to Discord. Set up in 3 steps.
- [Discord to Telegram: Route Discord Tickets to Telegram](https://inboxbarn.com/blog/discord-to-telegram): Let members open tickets in Discord and answer them from Telegram on your phone. Replies post back to Discord, one topic per ticket. Set up in 3 steps.
- [Slack to Discord: Route Slack Tickets into Discord](https://inboxbarn.com/blog/slack-to-discord): Let your team open tickets in Slack and route them into a Discord server, with replies sent back to Slack. A channel per ticket. Set up in 3 steps.
- [Slack to Email: Answer Slack Tickets from Your Inbox](https://inboxbarn.com/blog/slack-to-email): Let your team open tickets in Slack and handle them from email - searchable, forwardable, organized. Replies post back to Slack. Set it up in 3 steps.
- [Slack to Microsoft Teams: Bridge Slack Tickets to Teams](https://inboxbarn.com/blog/slack-to-microsoft-teams): Bridge tickets raised in Slack into Microsoft Teams, where another department works. Replies go back to Slack. Built on the Graph API. Set up in 3 steps.
- [Slack to Telegram: Route Slack Tickets to Telegram](https://inboxbarn.com/blog/slack-to-telegram): Route tickets raised in Slack into Telegram so on-call teammates can answer from their phones. Replies go back to Slack, one topic per ticket. Set up in 3 steps.
- [Website Chat to Discord: Route Web Chat into Discord](https://inboxbarn.com/blog/website-chat-to-discord): Add a chat widget to your site and route every conversation into Discord, where your team works. Replies appear in the visitor's chat bubble. Set up in 3 steps.
- [Website Chat to Slack: Route Web Chat into Slack](https://inboxbarn.com/blog/website-chat-to-slack): Add a chat widget to your site and answer every conversation from Slack. Replies appear live in the visitor's bubble. Hit the 5-minute reply window. Set up in 3 steps.
- [Website Chat to Email: Turn Web Chat into Email Threads](https://inboxbarn.com/blog/website-chat-to-email): Add a chat widget to your site and handle conversations from your inbox - searchable and organized. Replies appear in the visitor's bubble. Set up in 3 steps.
- [Website Chat to Microsoft Teams: Route Web Chat to Teams](https://inboxbarn.com/blog/website-chat-to-microsoft-teams): Add a chat widget to your site and answer from Microsoft Teams, where your company works. Replies appear in the visitor's bubble. Graph API. Set up in 3 steps.
- [Website Chat to Telegram: Route Web Chat to Telegram](https://inboxbarn.com/blog/website-chat-to-telegram): Add a chat widget to your site and answer from Telegram on your phone. Replies appear live in the visitor's bubble, one topic per chat. Set up in 3 steps.

## Guides

Long-form playbooks on running support without ticket theater:

- [The one-thread doctrine: how to stop fracturing customer conversations.](https://inboxbarn.com/guides/one-thread-doctrine): Why the thread — not the ticket — is the real unit of support work, and how to run a help desk that never fractures a customer's conversation.
- [Routing without regex.](https://inboxbarn.com/guides/routing-without-regex): How to route support conversations with four plain categories instead of a regex rule builder — routing rules that read like sentences and still do the job.
- [Discord as a support channel, actually.](https://inboxbarn.com/guides/discord-as-a-support-channel): Four hard-won lessons from running real customer support inside a Discord community server — keeping threads intact without burning out the team.
- [Macros that listen.](https://inboxbarn.com/guides/macros-that-listen): How to write saved replies that adapt to context — classified by routing category, suggested on matching threads, short enough to still sound human.
- [The Monday inbox triage.](https://inboxbarn.com/guides/monday-inbox-triage): A 20-minute Monday ritual — close, recategorize, assign, prune — that keeps a small team's open-conversation queue from compounding all quarter.
- [From four tabs to one thread.](https://inboxbarn.com/guides/four-tabs-to-one-thread): A migration plan for moving a small support team off a ticket portal and into one thread — run in parallel, so your customers never notice the switch.
- [Slack DMs vs. shared channels.](https://inboxbarn.com/guides/slack-dms-vs-shared): Customer DMs and shared Slack channels are different kinds of support with different stakes. Why they need different routing, and how to set up both.
- [The case against ticket numbers.](https://inboxbarn.com/guides/case-against-ticket-numbers): What a six-digit ticket ID actually signals to your customer, what the numbering habit costs your team, and what to use instead of numbering people.

## Comparisons

Honest comparisons for teams evaluating help desks:

- [Zendesk alternative](https://inboxbarn.com/compare/zendesk-alternative): InboxBarn is a flat-priced Zendesk alternative: free up to 5 teammates with every channel included, then $5/month flat for up to 25. No per-agent fees.
- [Intercom alternative](https://inboxbarn.com/compare/intercom-alternative): Skip seat licenses and metered AI billing. InboxBarn is a flat-priced Intercom alternative — free up to 5 teammates, then $5/month flat, widget included.
- [Freshdesk alternative](https://inboxbarn.com/compare/freshdesk-alternative): A simpler Freshdesk alternative: free up to 5 teammates with every channel included, then a flat $5/month up to 25. No per-agent tiers, no ticket portal.
- [Front alternative](https://inboxbarn.com/compare/front-alternative): InboxBarn is a Front alternative with more front doors: email, web chat, Discord & Slack in one flat-priced inbox. Free up to 5 teammates, then $5/month.
- [Crisp alternative](https://inboxbarn.com/compare/crisp-alternative): Crisp and InboxBarn both price per workspace, not per seat. InboxBarn routes chats into Discord, Slack, Teams & Telegram — free up to 5, then $5/month flat.
- [Help Scout alternative](https://inboxbarn.com/compare/help-scout-alternative): A Help Scout alternative without per-user pricing: free up to 5 teammates, then $5/month flat to 25 — with web chat, Discord & Slack alongside email.