A stranger pitching you, or a phishing mail, leaves the inbox. A real customer’s first email stays where you can see it.
When a customer asks for a refund, reports a bug, or needs a password reset, you already have a rule that routes it, answers it, or closes it.
Rules for the emails customers send you. A cancellation reaches you, a bug reaches engineering, and a cold pitch leaves the queue. Replace the names, tags, and URLs with yours.
A stranger pitching you, or a phishing mail, leaves the inbox. A real customer’s first email stays where you can see it.
A compliment or an offer to leave a review, with nothing to fix, closes on its own.
Product updates from other companies leave the inbox, so they stop pinging you.
A vacation auto-reply leaves the queue and stays on the contact, so you still see it when they write back.
Mail that looks like junk leaves the inbox. If a real customer disappears with it, loosen the rule.
A customer’s out-of-office reply leaves the queue and stays in the history.
A delivery failure leaves the queue and stays on the contact, so you can see why the mail did not arrive.
A customer who only says thanks gets the thread closed.
Invoice, refund, and plan questions stay grouped for the person who handles the money.
Each new conversation gets a label from the mail itself, so the queue is sorted before you open it.
A customer writing in the widget is easy to tell apart from email.
A student, a nonprofit, or anyone asking you to waive a fee reaches you. The price stays put until you decide.
A partnership, affiliate, or sponsorship pitch reaches you, so you can answer the ones you actually want.
A paying customer who wants money back because you were down reaches you, with a reminder to check the status page.
A customer who wants a person, or wants the bot to stop, gets a human on the thread.
A customer who wants their data, or wants their own account deleted, reaches you.
A customer who is unhappy, and is not describing one broken thing, reaches you.
A customer who wants to move data in reaches the person who runs imports.
A customer who says the docs are wrong, or that a step is missing, reaches you with a note to fix the article.
A customer who says the product is slow or timing out reaches engineering. A full outage still pages the person on call.
Each new customer email lands on the next person, so one of you is not left with the whole queue.
Mail from a company you care about goes straight to you.
A customer waiting in the chat widget gets a person immediately.
A customer who says something is broken gets engineering on the thread.
A paying customer skips the free queue and lands with priority support.
A paying customer who wants to cancel reaches you, and you get a notification.
Someone who is not a customer yet gets a draft. You still send it.
A paying customer asking for a refund reaches you, with a reminder to check the last invoice.
You can spot a paying customer in the queue without opening the thread.
A customer who wants to know how to call the API gets a draft. A broken endpoint stays with the bug.
A customer who writes at night hears that you are back at 9:00. The thread stays open.
A customer who writes on Saturday hears that a person will read it on Monday.
Mail that arrives overnight comes back at the start of your day.
A customer who writes on Friday evening hears that you will reply on Monday.
A customer who cannot log in gets the reset steps. You can still jump in if the link fails.
A paying customer who only wants their receipt gets the path to it, and the thread closes.
A customer asking for your SOC 2 or a DPA gets a draft, and the thread reaches you.
A customer with an idea gets a thank-you. The thread comes back in a week so you can answer a batch of them.
A customer stuck on setup gets a draft, and the thread reaches you.
A lawyer, a regulator, or a formal demand to delete data reaches you immediately. They get no template back.
A researcher reporting a hole in the product reaches you, and the details stay off a public issue.
A journalist or a podcast asking about you reaches you the same day.
A threat reaches you. A customer who is upset about a bug stays on the bug.
When customers report errors or slowness, Slack hears about it while you still reply to them.
A paying customer who cannot do their work pings Slack. They still wait for a person, not an automatic reply.
A paying customer who writes at night shows up in Slack before you open the inbox in the morning.
A customer who says someone got into their account, or that they can see another customer’s data, reaches you in Slack immediately.
A customer saying you are down, outside your hours, wakes the person on call.
A customer reporting an outage opens an incident in Better Stack.
A customer asking how something works gets a draft from Cursor. You still send it.
A customer with a stack trace gets the bug reproduced and filed. They hear back from you.
A customer who cannot find this in the docs gets a draft of the article. You edit it, then publish it.
Every new customer email gets a one-line note before you open it. Spam, billing, and legal stay with you.
A customer who says the last answer was wrong gets a new draft. You send it.
A customer who says the fix you shipped is still broken gets a pull request opened, then a reply from you.
A customer asking for something you may already ship gets a note on whether it exists.
You see each new customer in Slack, with their name, the subject, and a link back to the thread.
A paying customer pings a quieter Slack channel. Free-trial mail stays out of it.
A customer asking about an invoice or a refund shows up where the person who handles money already is.
A paying customer who wants to leave reaches you in Slack and in the inbox.
A paying customer pings Discord, for a team that lives there.
A new customer shows up in Teams, with their name, the subject, and a button back to the thread.
A customer reporting a bug gets an issue filed, and engineering gets the thread.
A customer reporting a bug gets a GitHub issue that links back to their email.
A customer reporting a bug gets a Jira work item, and you still reply from the inbox.
A customer’s idea is saved, and the thread comes back in a week so you can answer them with the others.
A customer asking for a demo or a price becomes a lead in HubSpot.
A paying customer who wants to cancel gets a note on their record.
A new customer email shows up in PostHog, next to what they did in the product.
Every new customer email lands in a spreadsheet, with their name and a link to the thread.
A new customer email can start whatever else you already run.
A snippet runs when you type the slash command in a reply. /cursor, /claude, /grok, and /hermes hand the open thread to that agent. You still decide what the customer receives.
The customer already has the answer. You thank them and close the thread.
/thanks
The customer has been waiting. You tell them a person has the thread, before you have the answer.
/ack
The customer hears you will be back in a few hours, and the thread returns then.
/eta
The customer gets the help-center link, and you ask where they got stuck.
/docs
You ask the customer for the page, their email, and a screenshot before you guess.
/screenshot
You ask the customer what they clicked, what they expected, and what happened.
/repro
You ask the customer for the request id, the time, and the endpoint your logs are indexed by.
/logs
The customer gets the status page. You tell them you are on it, and you name no time.
/status
You apologise, ask for the page and a screenshot, and engineering gets the bug.
/bug
The customer gets a temporary step. The thread comes back when you can say it is fixed.
/workaround
The customer hears the fix is out, tries again, and the thread closes.
/fixed
You ask the customer for the endpoint, the status code, and the request id.
/api
The customer hears it is fixed, and the thread closes.
/resolved
The customer hears you will check back in two days, and the thread returns then.
/followup
You send the step from the article you found, and the thread comes back when they reply.
/article
The docs do not cover the question. You ask two things, and you leave a note to write the article.
/gap
You send the link to the issue you already found, and you say you will write when it ships.
/tracked
The last reply did not fix it. You put a person on the thread and leave a note.
/escalate
You ask the customer for the last four digits or the invoice number before you touch the charge.
/pay
A customer who only wants their receipt gets the billing portal, and the thread closes.
/invoice
You tell the customer you will look at the charge. You check the last invoice before you promise anything.
/refund
You ask the customer what went wrong, and the cancellation reaches you.
/cancel
The customer hears which plan they will land on, and what they will lose.
/downgrade
The customer gets the plan page. You switch them when they reply with the plan name.
/upgrade
You tell the customer you can pause, and you ask for how long.
/pause
The customer gets the reset steps, once you have read the mail.
/password
You ask the customer to confirm. Nothing is deleted, and the thread stays open.
/delete
The customer hears the export is on the way, or you ask which workspace.
/export
You ask which login provider they use, and who their admin is.
/sso
You ask for the domain, and you tell them which DNS records you need.
/domain
You ask for the account email and a detail from a recent invoice, so you know it is them.
/2fa
A new customer gets a short hello from a person, and the one setup link that matters.
/welcome
The customer gets the three setup steps, in order.
/setup
You ask for the file format and the size, and you tell them the column order you need.
/import
You drop the customer’s thread into Slack. They get no extra email.
/slack
The customer’s bug becomes a Linear issue, from the thread you are reading.
/linear
The customer’s bug becomes a GitHub issue, from the thread you are reading.
/github
The customer’s idea is saved to Notion when you decide it is worth keeping.
/notion
The customer’s bug becomes a Jira work item.
/jira
This customer’s thread starts an n8n workflow you already run.
/n8n
This customer’s thread starts a Make scenario.
/make
This customer’s thread starts a Zap when you decide it should.
/zapier
This customer gets a note on their HubSpot timeline.
/hubspot
This customer gets a note on their person or company in Attio.
/attio
The customer’s idea becomes a Canny post, or a vote on one that already exists.
/canny
This customer, the subject, and the link land as a row in the sheet.
/airtable
The customer’s bug becomes a ClickUp task.
/clickup
This customer gets a case, or a task, on their Salesforce contact.
/salesforce
This customer’s email shows up as an event in Segment.
/segment
This customer can enter a Loops campaign because they wrote in.
/loops
This customer can enter a Customer.io campaign because they wrote in.
/customerio
You get the customer’s subject and a link to the thread, in Telegram.
/telegram
The customer’s request becomes an Asana task.
/asana
This customer gets a note on their deal, or on their person, in Pipedrive.
/pipedrive
The customer is waiting on this thread. Cursor writes the draft, and you send it.
/cursor
The customer hit a bug. Claude Code finds it in the repo and files the issue. You tell them.
/claude
A long thread gets a four-line summary before you answer the customer.
/grok
If a help article fully answers the customer, Hermes sends it. A partial answer stays a draft for you.
/hermes
The customer’s bug gets a pull request. They hear about the fix from you.
/codex
Before you promise a customer a feature, Amp checks whether you already shipped it.
/amp
The docs do not cover this thread. Claude Code drafts the article, and you publish it.
/draft