Support emails pile up. The right person rarely sees the right email first.
Every support team knows the pattern: too many emails, too much manual triage, and the occasional critical thread that gets seen too late. this+that adds an intelligent routing layer between your inbox and your team.
Manual triage is where support quietly leaks
Most of it comes down to doing by hand what a queue should never need a person for. Common questions get answered one at a time, so the same refund-policy question collects twelve different answers from twelve different teammates. And there is no single view of open threads, time to first response, or which issues are aging, which leaves you managing support by searching your inbox. Two failures hurt customers the most.
Email lands with the wrong person
Billing questions go to engineering. Feature requests go to support. Every misroute costs time, and the customer feels the delay.
The urgent thread waits
A customer emails to cancel their account, and it sits in the queue for six hours. By the time someone opens it, the window to save the relationship has closed.
Classify, route, draft, and escalate, before a human ever opens the email
It starts the moment an email lands. this+that reads it for topic and urgency, then routes it: billing to finance, technical issues to engineering, anything high-urgency flagged on the spot before it can age in the queue. From there, three things happen without anyone lifting a finger.
Start from a draft, not a blank page
For common questions, this+that writes a reply from your knowledge base and queues it for review. Approve, edit, send.
The risky stuff jumps the queue
When an email mentions cancellation, a refund, or another high-risk signal, the right person gets pinged in Slack right away, no waiting for the next inbox check to catch it.
Nothing falls off the end
Each support email becomes a DoBox task with an owner and a deadline. Time to resolution is finally something you can see and measure.
Support workflows that run automatically
These are the kinds of workflows you can describe in plain English and have running in minutes.
Helpdesk tools manage tickets. this+that handles the work before the ticket exists.
Ticketing systems are good at organizing work that's already been triaged. They don't read the email, decide who should handle it, draft the first response, or ping someone on Slack when something is urgent. this+that operates in the gap between email arriving and a human taking action, reducing the time between those two events from hours to seconds for the issues that matter most.
A good reply needs the answer and the customer behind it
A canned reply from the knowledge base answers the question but misses the person. The customer asking about an integration is the same one who escalated a billing issue last week and is on a trial that ends Friday. That operational knowledge, the live state of the account, who has touched it, the context buried in last week's threads, usually lives nowhere. The Brain holds the canonical answers and keeps the operational picture current automatically from your communications, so a reply is grounded in your real policy and personal to the customer in front of you.
One source for the canonical answers
Refund policy, pricing, approved positioning, your best support replies: they all live in the Brain. A draft uses what the team actually decided, so that refund question stops collecting twelve answers.
The customer's live context comes attached
The Brain keeps each customer's operational state current from the comms that already flow through this+that: open issues, recent escalations, where the relationship stands. So a reply arrives knowing who it is talking to, rather than starting cold.
Answer it once, find it next time
When a thread resolves something the knowledge base never covered, that answer can be written back into the Brain, and the next person or agent to hit the question finds it waiting. It is not a CRM, so your systems of record stay where they are. And it is more than a wiki, because the operational layer keeps itself current.
Your support inbox has patterns. this+that finds them.
Connect your inbox and see which support workflows this+that would automate based on your actual email patterns. No signup required.