this+that vs Jared
An AI teammate inside Slack, or one that reads your whole comms stack.
Jared is an AI teammate in Slack and WhatsApp. It reads the room, follows the conversation, learns your team, and speaks up when it can help, without being asked. this+that shares that instinct and widens the surface. It reads the messages your team receives across email, Slack, Teams, and Google Chat, then gives the work structured homes: a shared task manager, plain-language workflows, and a team knowledge layer. Same starting idea. A different amount of ground covered.
An AI teammate in two channels, or an AI layer across all of them
Jared and this+that start from the same instinct. Most AI tools wait for you to open them and ask. Jared and this+that both read the conversation as it happens and act on what shows up. They share a philosophy, and Jared executes it well. It watches Slack channels, DMs and WhatsApp threads, it knows when its input matters and when to stay quiet, and it handles the longer running, multi-stakeholder tasks that traditional assistants drop (think "make sure the launch materials are ready before Friday"). If your team lives in Slack, Jared is a thoughtful, proactive teammate to have in the room.
The difference is surface area. Jared works in Slack and WhatsApp. this+that reads across the whole comms stack: Gmail, Outlook, Slack, Microsoft Teams, and Google Chat, all scanned for what needs doing. And it does not stop at speaking up in the thread. The work it finds gets structured homes. DoBox is a shared, assignable task manager the whole team can see. Workflows turn recurring requests into plain-language automations. The brain is a team knowledge layer that grounds what the AI drafts and answers. Jared is an AI teammate inside two channels. this+that is the inbox, task, automation, and knowledge layer across all of them. Many teams that love Jared in Slack still have most of their work arriving by email, and that is the gap we are built for.
Feature by feature
How the two products compare across the things that matter most.
| Topic | Jared | this+that |
|---|---|---|
| Core idea | An AI teammate that reads ongoing conversation and acts without being asked. Proactive and context-aware by design. | The same instinct, widened. The AI reads the messages your team receives and acts on what needs doing, then gives the work structured homes. |
| Where it lives | Slack. It works in any public or private channels and DMs you invite it to. | A unified inbox spanning five live channels: Gmail, Outlook, Slack, Microsoft Teams, and Google Chat. (Instagram and Facebook Messenger are on the roadmap, not yet live.) |
| How it engages | Reads the room, follows the thread, and speaks up in Slack when it can add value. Knows when to stay quiet. | Scans every message across every connected channel for requests, commitments, deadlines, and follow-ups, then surfaces them as tasks. |
| Task layer | A running task queue Jared keeps for the work it picks up. Built around what Jared itself is doing. | DoBox, a shared team task manager. Tasks auto-created from messages or added by hand, on multiple team lists, assignable to specific teammates. |
| Assigning work to people | Centered on what Jared does for the team. Designed as a coworker doing the work itself. | Assign, reassign, and remove teammates on any task. Priorities, due dates, labels, checklists, recurring tasks, and comments with @mentions and attachments. |
| Automation | Strong at longer, ongoing tasks that coordinate stakeholders toward a goal (for example, getting materials ready before a deadline). | Plain-language workflows triggered by your messages, with conditional logic, loops, autonomous sub-agents, and a broad action set. Tools connect over MCP. |
| Knowledge | Ingests team context at onboarding (Slack history, docs, code, notes) so it shows up knowing the background. | The brain, a team knowledge layer with version history that grounds the AI’s drafts, answers, and workflows. You write to it directly today. |
| Tool connections | Connects to a large catalog of tools to get work done from inside Slack. | Open MCP standard. Any tool with an MCP server or API plugs in. |
| Who it is for | Teams that run in Slack and want a proactive AI coworker in the room. | Teams whose work arrives across many channels and want one place to see it, act on it, and automate it. |
| Pricing | Per workspace with usage caps, never per seat. Starter $100 a month covers 100 voice minutes and 300 chat messages; Pro is $300 a month for unlimited voice and chat and is the only tier with a trial, at three days. Monthly billing only, with no annual rate published and no free tier. | Free for 30 days, including 3,000 credits, no credit card required. Then $35 per user per month, or $29 billed annually, with 3,000 credits a month per person. |
- The proactive read is the hard part, and Jared nails it. It follows the conversation and acts without being asked, yet without flooding the channel.
- It knows when to stay quiet. That restraint is what makes it read like a teammate rather than a bot reacting to every mention.
- Long, multi-person work suits it well. Pushing a launch checklist over the line by Friday is the kind of task that usually slips through the cracks, and Jared keeps at it.
- Onboarding is light, since it ingests team history and docs up front and arrives already knowing the background.
- For a team that genuinely lives in Slack, it is a natural fit.
- The same instinct, more ground covered. Reading and acting on the stream happens across email, Slack, Teams, and Google Chat, so everything feeds one inbox instead of one channel.
- DoBox is where the work lands. It auto-creates tasks from messages, sorts them onto team lists, and lets you assign specific teammates, with priorities, due dates, labels, checklists, and recurring tasks.
- Workflows cover the repeatable cases. You describe them in plain language; conditional branches, loops, sub-agents, and a broad action set are all available.
- The brain grounds every reply in your team’s own context, with version history behind it.
- Tooling stays open. Anything with an MCP server or API connects.
- It is a team product first, not a single coworker with team features bolted on. Shared task views, assignment, and team-request grounding come standard.
See what's waiting in your inbox
Connect your inbox and this+that starts reading it. The tasks, follow-ups, and open commitments buried in your messages become tracked work, and your workflows write what they learn back to the brain.
Free for 30 days · No credit card required · Then $35 per user per month · $29 billed annually