← Back to library

File orphaned customer replies into Freshdesk

u/flexrc noticed customers answering order confirmation emails with support questions that sat in a general info@ inbox. Forwarding everything would have flooded support, so he routed that mail to a separate Gmail catch-all, added an n8n AI classifier to pick out real help requests, and forwarded only those to Freshdesk. He built it in roughly thirty minutes.

  • OutcomeSupport questions sent to the wrong address reach your help desk, while everything else stays out of the queue.
  • SetupAn afternoon+
  • LevelIntermediate
  • Creditu/flexrc on r/n8n
View original
Works with
n8nChatGPT

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

When should you use it?

  • Customers reply to transactional emails with problems
  • Support requests get lost in a general inbox
  • You use a help desk like Freshdesk

Not for: Inboxes where misrouting a message has legal consequences; Replacing a proper reply-to address on your order emails

What do you need, and what do you get?

You need

  • A catch-all mailbox for the general address
  • An AI classifier step in n8n
  • Your help desk's email intake

You get

  • Support requests forwarded to the help desk
  • Other mail left where it was
  • A log of classifications to review

How does it work, step by step?

  1. Collect general mailRoute the general address into a dedicated mailbox the workflow watches.
  2. Classify each messageAsk a model whether it's a support request, with a short reason.
  3. Forward support onlySend support messages to the help desk with the original sender preserved.
  4. Log decisionsRecord each classification so you can spot misroutes.
  5. Add handlers over timeCreate branches for other categories, such as billing or partnerships, as needed.

The prompt

Our own prompt, inspired by u/flexrc on r/n8n and written to work in n8n and ChatGPT. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt4 variables
Classify this email sent to our general inbox. From: {sender}. Subject: {subject}. Body: {body}.
Return one label from {labels} (for example support, billing, sales, spam, other), a confidence of high, medium or low, and a one-sentence reason. Label it support if the customer reports a problem with an order, delivery, product or account. If confidence is low, return 'needs_human'.

Inspired by u/flexrc on r/n8n: Automating customer support email routing with n8n and AI. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Forwarding can change the sender address; make sure the help desk ticket replies to the customer.
  • Borderline messages should go to a person rather than be dropped.

Our take

This is a small fix for a real, common leak: customers reply to whatever email they have, and order confirmations often come from an address nobody watches closely. Classifying each message rather than forwarding everything keeps the support queue clean, and the pattern extends naturally to billing, partnership or press emails. Two practical details make or break it. First, preserve the original sender when forwarding so the ticket reply reaches the customer, not your catch-all account. Second, decide what happens to uncertain messages; sending them to a person is safer than dropping them. Keep a log of decisions for the first few weeks and check misroutes. Longer term, also fix the cause by setting a sensible reply-to address on transactional emails, but the classifier remains useful for the replies that will always slip through. Because the model only labels and never answers, the risk is low and the payoff is quick.

Where the time goes back: Support requests no longer wait in the wrong inbox until someone notices them.

FAQ

Why not forward everything to support?
Unrelated mail would land in the queue and create noise.
How long did it take?
He says about thirty minutes for the first version.

Source and credit

Inspired by u/flexrc on r/n8n. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Automating customer support email routing with n8n and AI
Creator
u/flexrc on r/n8n
Published on
Reddit
Original date
Oct 23, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
n8n
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS (desk check, not a live run in the vendor's app). Replaces an earlier templated dry-run note.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Customer Support

All 27 Customer Support playbooks →

Related playbooks

Customer SupportPrompt✓ AI dry run

Clean up saved support replies before your bot reuses them

Read every saved answer your support bot can pull from as if it were about to be sent to a stranger, rewrite the risky ones into generic answers and set rules so new ones are written that way.

Credit: Pierre-Laurent Medori

Under an hour
Customer SupportPrompt✓ AI dry run

Find the bugs in your intake chatbot with one test chat per rule

Write a small set of test chats, each aimed at one rule in your bot's field spec with the stored values you expect written down first, and catch errors a large pile of happy-path chats misses.

Credit: Adam (Adam13y)

Under an hour
Customer SupportWorkflow✓ AI dry run

Stop a booking agent from double-booking after a timeout

Change an appointment agent so that a timed-out booking call counts as unknown rather than done, the agent tells the customer a person will confirm instead of saying they are booked, every write carries a request key so a retry cannot create a second appointment, and a forced-timeout test runs after every workflow change.

Credit: ccch713

An afternoon+
Customer SupportWorkflow✓ AI dry run

Have an agent work each client Slack request

Watch a shared Slack channel with a client, open an investigation and a ticket for each new message, and route a drafted reply to you for approval.

Credit: Dale Spoonemore (@DaleSpoonemore)

An afternoon+