A shared inbox your team triages, or an AI layer that does the work
Front is an excellent shared inbox: a team assigns, comments on, and replies to customer email together in one place. this+that works differently. Across every connected channel, it turns the messages that land into tracked tasks on its own and runs automations against them, grounded in a brain your team maintains. Where Front centers human triage of the queue, this+that adds an AI work layer on top of a unified inbox.
Collaborative triage vs an AI work layer
Front is genuinely good at what it does: a shared inbox where a team owns customer-facing conversations together, with assignment, internal comments and @mentions on email threads, SLAs, and analytics for support and operations queues. If your job is to triage a high-volume queue as a team, Front is one of the best tools for it. this+that is built around a different idea. It treats Gmail, Outlook, Slack, Teams, Google Chat, and Telegram as one stream of incoming work, then adds an AI layer on top. The tasks and commitments buried in your messages get extracted automatically, plain-language workflows handle what comes next, and the drafts and answers stay grounded in a brain your team maintains. Front keeps people fast at triaging the queue. this+that goes after a smaller queue by turning routine messages into tracked, assigned work before anyone has to read them. So if your team triages a shared support queue together, Front fits. If you would rather have the work that comes out of your messages handled and assigned automatically across every channel, that is the distinction that matters.
Feature by feature
How the two products compare across the things that matter most.
| Topic | Front | this+that |
|---|---|---|
| Core use case | Collaborative inbox triage. A team owns customer-facing conversations together, assigning and replying in one shared place. | An AI work layer on a universal inbox. Read every channel, turn messages into tracked tasks, and automate the follow-through. |
| Channels | Email and shared inboxes are the core, with SMS, social, and chat channels routed into the same queue for support and ops teams. | Gmail, Outlook, Slack, Teams, Google Chat, and Telegram as one stream of incoming work. WhatsApp, Instagram, and Facebook Messenger are coming soon. |
| Team triage & assignment | A real strength. Assign conversations, see who owns what, and avoid two people answering the same message. | Assign extracted tasks to teammates with due dates, priorities, and comments, rather than assigning the email thread itself. |
| Internal collaboration | Internal comments and @mentions directly on an email thread, so the team discusses a reply without forwarding. A real strength. | Comments and @mentions live on the task in DoBox, where the work is tracked, not on the message thread. |
| Task extraction | Not a focus. A teammate reads the conversation and decides what needs to happen. | Automatic. DoBox reads every message across channels and extracts requests, decisions, commitments, and deadlines into tracked tasks. |
| Tasks | Conversations are the unit of work; status is handled by assigning, tagging, and archiving threads. | A dedicated task system: multiple lists, assignees, priorities, due dates, recurring tasks, comments, and file attachments. |
| Workflow automation | Rules route, tag, and assign incoming messages, and trigger SLA reminders across the queue. | Plain-language automations with 32 action types, conditional logic, loops, MCP tool connections, and autonomous sub-agents. |
| AI drafting | AI assists drafting and summarizing replies inside the shared inbox. | AI draft replies and emails, interactively and as a workflow action, grounded in the brain your team maintains. |
| Knowledge grounding | Canned responses and a knowledge base feed consistent answers into the queue. | A brain with version history grounds drafts, answers, and workflows. It does not yet auto-update from your message stream; that is coming. |
| SLAs & analytics | Mature SLA tracking and team performance analytics for support and ops queues. A real strength. | Not a focus. this+that tracks work as tasks, not queue-level SLA and response-time metrics. |
| Integrations | A large catalog of native integrations and an API, built around the support and ops stack. | Open MCP standard: connect GitHub, Jira, Notion, and any MCP-compatible tool as a workflow step. |
- Collaborative triage is its core strength. A team owns a shared inbox together, with clear assignment so no message is missed or answered twice.
- When a team needs to agree on a reply, internal comments and @mentions live right on the email thread, with no forwarding or side channels.
- Years of refinement show in mature SLA tracking and response-time analytics built for support and operations queues.
- There is a wide catalog of native integrations, and several channels can be routed into one queue for customer-facing teams.
- For a high-volume support or ops queue, where shared ownership of every conversation is the whole job, it is purpose-built.
- Gmail, Outlook, Slack, Teams, Google Chat, and Telegram all flow in as one stream of work, not a support queue alone.
- Every message is read for requests, commitments, and deadlines, which surface automatically in DoBox instead of being caught by hand.
- The task system is dedicated, with multiple lists, assignees, priorities, due dates, recurring tasks, comments, and attachments.
- Describe a process in plain language and this+that builds it: 32 action types, conditional logic, loops, MCP connections, and autonomous sub-agents.
- Drafts, answers, and workflows are grounded in a brain with version history, built from what your team has actually written down.
- Through the open MCP standard, you can connect GitHub, Jira, Notion, or any MCP-compatible tool as an automation step.
See what's waiting in your inbox
Connect your inbox and get a free analysis of the tasks, follow-ups, and open commitments this+that would surface across your channels.
Free to use · No credit card required