Customer support automation

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

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.

Inbox

A stranger pitching you, or a phishing mail, leaves the inbox. A real customer’s first email stays where you can see it.

Product updates from other companies leave the inbox, so they stop pinging you.

Invoice, refund, and plan questions stay grouped for the person who handles the money.

Routing

A customer who says the docs are wrong, or that a step is missing, reaches you with a note to fix the article.

Replies

Alerts

AI agents

Webhook

A customer’s idea is saved, and the thread comes back in a week so you can answer them with the others.

Smart snippets

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.

Saved replies

You ask the customer for the request id, the time, and the endpoint your logs are indexed by.

/logs

The customer gets a temporary step. The thread comes back when you can say it is fixed.

/workaround

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

Billing

You ask the customer for the last four digits or the invoice number before you touch the charge.

/pay

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

Account

The customer hears the export is on the way, or you ask which workspace.

/export

You ask for the file format and the size, and you tell them the column order you need.

/import

Send to a tool

Hand to an agent

The customer is waiting on this thread. Cursor writes the draft, and you send it.

/cursor

Questions

What is a rule?
A rule runs on its own. Some fire when a conversation is created and a condition matches, such as a paid plan or a channel. Others fire when the email is about a phrase you type. AI reads the new email and runs the closest phrase. If none is close, the email stays in the inbox.
Can Cursor, Claude Code, or Grok run these?
The AI agent templates POST the conversation to a URL you own. That URL starts Cursor, Claude Code, Codex, Amp, Grok Bot, or Hermes. The Fernand API key stays on that server. Give it drafts and notes, and leave reply off until you trust the drafts.
What does "a conversation is about" do?
You type a short phrase, such as "Cold outreach, spam, phishing" or "Bug report". AI reads the new email and runs the rule whose phrase fits best. One phrase wins. If none is close, the email stays in the inbox.
What is a smart snippet?
A snippet runs when you type a slash command in the reply box. Use one when a person should decide. Use a rule when the inbox should decide.
How do the webhooks work?
Send to a webhook is a POST to a URL you paste, with the JSON you write. Slack, Discord, Teams, Telegram, Better Stack, and PostHog can take that directly. Tools that want an Authorization header, such as Linear, GitHub, HubSpot, or Notion, sit behind Zapier, Make, or n8n.
Which variables can the JSON use?
The webhook body can use ${contact_name}, ${subject}, and ${url}. Reply text can use {{first_name}} and {{agent_first_name}}.