You opened a shop, not an inbox
Cafes, restaurants, boutiques, salons, studios: one owner serving the room and still answering the whole inbox, with no one whose job it is to catch what slips. this+that reads what lands, handles what it can, turns it into tracked work, and drafts the replies for you to approve, so the slow ones stop falling through.
The fast questions get answered, and the rest slip away
You are behind the counter when the messages arrive. A customer asks whether you are open Sunday. A supplier confirms tomorrow's delivery. Someone wants a bulk order for their office, the kind of order that pays for a slow week. A new review lands, and it deserves a reply. All of it stacks up in one inbox while you are pulling shots, plating dishes, or finishing a cut, and there is no one to sort it first.
So you handle the quick ones between customers and tell yourself you will get to the rest tonight. By closing you are too tired. The bulk order never gets quoted, even though it was the message most worth answering. None of it was hard work. It just needed someone whose whole job was watching the inbox, and that someone is you, in the gaps, after a full day on your feet.
A back office that runs while you work the room
this+that watches every channel you connect, from email to Slack to Teams, and turns each incoming message into a task in your DoBox with a deadline attached, so the bulk-order request cannot quietly drop off the list while you are busy. A note from a supplier gets flagged for review and filed where it belongs rather than sitting unread. Anything still waiting on you is surfaced in one place instead of buried under everything newer.
Then it drafts the replies for you. The answer to "are you open Sunday" or "can you cater for twelve" comes back grounded in your own hours, prices, and policies, written in your voice, ready in your queue. You write those facts down once and this+that uses them; it does not make them up. By default nothing goes out until you approve it: you read the draft, adjust a word if you want, and hit send. Once you trust how it handles a kind of message, you can let those go on their own. Either way, no more starting from a blank box at eleven at night.
Automations built for how a small shop actually runs
You describe what you need in plain English and this+that sets it up and runs it. These are the kind of things owner-operators ask for, typed the way you would say them out loud.
Tied to the tools you already use, even the ones we are not
this+that does not run your inventory or your marketing. What it does is connect to the tools that do, through MCP, an open standard for letting software talk to AI agents. Your point-of-sale, your inventory system, your marketing list: this+that reaches into the ones you already pay for and drives them from the same plain-English workflows that handle your inbox.
So a low-stock alert from your inventory tool can trigger a draft reorder email to the right supplier, waiting in your queue to approve. A first-time customer can be added to your marketing list without you copying anything over. The work that used to mean jumping between four apps becomes one workflow, started by a message and run for you. this+that ties your messages to the tools you already use, even the ones it does not replace.
It hands back the part you opened the shop to do
You started this to run your place and do the work you love, not to live in an inbox after close. Hiring someone to sit on the messages costs more than a small shop can spare, and inbox filters only move mail around; they have no idea that one email is a catering order worth chasing and the next is a flyer. this+that reads each message, works out what it is actually asking for, and either drafts the reply or opens the task, so the admin gets handled in the background and you get your evenings back.
See what's waiting in your inbox
Connect your inbox and it will surface everything waiting on a reply, from the quick questions to the orders worth chasing. Takes under 2 minutes, and there's no signup to do it.