Labels every email that hits a shared inbox, forwards it to the person who owns it, and pings Slack only when something genuinely cannot wait.
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
All 34 stores offline since 09:40
Our tills stopped syncing at 09:40 this morning and all 34 stores are taking cash only. We restarted the local gateway in two stores with no change, so it looks like the problem is on your side. Saturday is our busiest day and we are losing roughly 40,000 kroner an hour. Please call my mobile, I am reachable all day.
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Gmail
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Routing rules
Your categories, the exact Gmail label for each one, who owns it, and the fallback label and owner for mail that fits nothing. The agent never invents a label or sends to anyone outside this list.
Urgent criteria
What genuinely cannot wait, such as the senders, deadlines, amounts, or phrases that should interrupt someone, plus the channel that has to hear about it. Everything else is labeled and forwarded without a Slack ping.
Choose which agent runs it
NoClick's built-in models work out of the box — or bring Claude Code, Codex, and other coding agents on your own subscription.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
A shared inbox is where work goes to wait, because sorting it is nobody's job in particular. This agent reads each new email, applies the label from your rules, and forwards it to the owner with two lines of context on top. Slack fires only for what you defined as urgent, so a ping in that channel still means something.
What do I need to connect before it runs?
A Gmail account for the shared inbox, with the labels already created under the exact names you use in the rules, and the Slack channel for urgent items. Then you write the routing rules, one line per category with its label and its owner's email address, plus what counts as urgent. Everything the agent does comes from that list, so it is worth spending twenty minutes on.
What happens when it gets a label wrong?
It can only label and forward, so a mistake is a misfiled email, not a lost or answered one. It cannot reply to the sender, delete, or archive, and it will not forward to an address outside your rules. When nothing fits it applies your fallback label and says plainly that it could not classify the email, which is far easier to fix than a confident wrong route. Run it alongside your current process for a week and read the labels before you trust the forwards.
What does it cost to run?
One short agent run per email the trigger picks up, so cost follows inbox volume. Urgent items cost the same as routine ones, since the Slack post is the cheap part. If the inbox is full of automated notifications, filter the trigger to the mail you actually want triaged.
Free to start. Guided setup, a test run against staged conversations, and it's live.