How to Block Spam & Set Email Rules in Freshdesk

The three layers of Freshdesk spam handling

Before the menus, the mental model. Freshdesk fights spam at three levels, and most teams use all three together.

• Reactive (per ticket): the Spam action on an individual ticket, for the one-off that slipped through.
• Automatic (built in): the proactive spam filter, which scores every incoming email and quarantines the obvious junk without any setup.
• Rule-based (proactive): Ticket Creation automations that inspect the sender, subject, or body of every new ticket and mark matching mail as spam the moment it arrives.

The first is a broom, the second is a smoke detector, and the third is a locked door. Configure the third well and the first two barely get used.

Mark a single ticket as spam

This is the fastest fix and the one you'll reach for most. When a junk ticket lands in your queue, open it and use the ticket's overflow menu.

1. Open the offending ticket.
2. Click the ... (More) menu in the ticket toolbar.
3. Select Spam.

That's it. Per Freshworks' Spam and trash documentation, marking a ticket as Spam removes it from your main inbox and moves it into the Spam folder under the Tickets tab, where it stays out of your agents' way but isn't permanently deleted. If Freshdesk ever gets it wrong, you open the Spam folder and restore the ticket back to your queue in a click.

The Spam action lives in the same More menu as Execute scenarios, Merge, Convert to forum topic, Log time, Print, and Delete — so if you can merge a ticket, you already know where to find it. Note that Freshdesk distinguishes Spam (recoverable, in the Spam folder) from Delete (moves to Trash): marking as spam is the safer default, because a genuine customer you accidentally quarantined can be pulled back.

Let the proactive spam filter do the obvious work

You don't have to catch everything by hand. Freshdesk ships with a proactive spam filter that's enabled automatically, and it does more than you might expect. According to the How to protect your helpdesk from spam attack article, the filter evaluates every incoming email ticket and assigns it a spam score based on predefined criteria. Messages scoring 6 or higher are automatically flagged as spam and dropped into the Spam folder — no rule, no action, no agent involvement.

Two practical implications follow from that:

• Check the Spam folder periodically. Because the filter is automatic and score-based, it can occasionally misjudge a legitimate email — a newsletter-style transactional message, or mail arriving via a flagged relay. Skim the Spam folder now and then and restore anything real.
• You can tighten the front door for portal spam. A lot of junk doesn't come by email at all — it's bots filling in your support form. To stop that, go to Admin → Channels → Portals → Edit → Manage sections and turn on Enable CAPTCHA to help avoid spam. It's the single most effective setting against form-submission bots.

Auto-route junk with Ticket Creation (Dispatch'r) rules

The manual Spam action and the built-in filter handle most cases, but for a recurring offender — a spam domain hammering you, a mailing list you're stuck on, a subject line that always signals junk — you want it gone before it ever hits your queue. That's the job of a Ticket Creation automation rule.

If you've used Freshdesk for a while, you know this feature as the Dispatch'r. Freshdesk has since folded it into the unified automations UI, but it runs at exactly the same moment: the instant a ticket is created. Per the Automation Rules Examples: Ticket Creation documentation, here's how to build a rule that marks incoming mail as spam:

1. Go to Admin → Workflows → Automations and open the Ticket Creation tab.
2. Click New rule and give it a clear name (e.g. Block spam domains).
3. In the "On tickets with these properties" (conditions) section, choose Requester email → Contains and enter the values you want to block — for example spamdomain.com or a specific sender.
4. In the "Perform these actions" section, add the Mark as spam action.
5. Click Preview and save, then Save and enable.

From then on, any new ticket whose requester email matches your criteria is quarantined automatically. The Dispatch'r documentation adds one important sequencing tip: because the first decision on any ticket is usually "is this spam?", you should place your spam rules at the top of your automation list so they run before your routing and assignment rules waste cycles on junk.

Blocking a whole domain (a poor-man's blocklist)

Freshdesk has no standalone "blocklist" screen on most plans, but a Ticket Creation rule is the practical equivalent. To block an entire domain — say, a persistent *.ru spam wave or a competitor scraping your form — create the rule above with Requester email → Contains → @baddomain.com and the Mark as spam action. You can stack several domains into one rule's condition set, and combine it with Subject or Description → Contains conditions to catch spam that rotates sender addresses but reuses the same pitch text. It isn't a formal allow/deny list, but it behaves like one.

Native spam handling vs. what it can't do

Credit where it's due: for the overwhelming majority of teams, these layers are enough. The proactive filter quietly eats the bulk of junk, CAPTCHA shuts down form bots, and a handful of Ticket Creation rules handle the repeat offenders. None of what follows is a knock on native handling.

But notice the shared limitation: every one of these tools matches on patterns, not meaning. A rule that blocks @baddomain.com can't tell an angry-but-legitimate customer from a troll, and the spam filter's score doesn't understand intent. So the messages that make it past the filters — the real tickets — still land on a human who has to read each one, figure out what the customer actually wants, and write the reply. Spam handling cleans the queue; it does nothing about the work waiting inside it. There's also a subtler cost: rules are literal, so aggressive spam blocking risks quarantining real customers, and every rule you add is one more thing to maintain as spam patterns shift.

This is the seam where an AI layer fits — and it's worth being clear-eyed about the build-versus-buy tradeoff before adding one. The category of AI agents for customer service exists to do the reasoning-heavy part that pattern rules can't. Macha is one such layer: it runs on top of the Freshdesk you already use as a native connector — it does not replace your help desk, your Spam folder, or your automation rules. You connect Macha to Freshdesk with your subdomain and API key, and it reads the same tickets your spam rules already filtered, drafting a grounded first reply, triaging by intent, and looking up order or account status through a custom tool that turns a REST API into something the agent can call. Because it reasons about what a message means rather than which string it contains, it can also flag borderline junk your literal rules miss — while Freshdesk stays the system of record for how mail is received and quarantined. (Macha's connector is for Freshdesk specifically — not Freshchat, Freshservice, or Freshcaller. Credits are consumed per AI action, not per resolution — see the pricing breakdown.) If you want to see how that automation is wired, how to automate Freshdesk with AI walks through it.

For the broader picture on email setup and deliverability, see how to configure email in Freshdesk and the companion guide on why Freshdesk emails go to spam — the flip side of blocking junk is making sure your own replies aren't treated as junk.

FAQ

How do I mark an email as spam in Freshdesk? Open the ticket, click the ... (More) menu in the ticket toolbar, and choose Spam. The ticket leaves your inbox and moves to the Spam folder under the Tickets tab, where you can restore it later if it was flagged by mistake.

Can I block an entire email domain in Freshdesk? Yes, using a Ticket Creation automation rule (formerly the Dispatch'r). Go to Admin → Workflows → Automations → Ticket Creation → New rule, set the condition Requester email → Contains → @yourdomain.com, add the Mark as spam action, and save. New tickets from that domain are quarantined automatically.

Does Freshdesk have a built-in spam filter? Yes. A proactive spam filter is enabled by default and scores every incoming email ticket; messages scoring 6 or higher are automatically flagged as spam and moved to the Spam folder. Check that folder occasionally in case a real email is over-flagged.

How do I stop spam from my customer portal form? Go to Admin → Channels → Portals → Edit → Manage sections and enable CAPTCHA to help avoid spam. It's the most effective control against bots submitting your support form.

Can I add AI to Freshdesk spam handling without replacing Freshdesk? Yes. An AI agent layer like Macha connects to Freshdesk as a native connector and works on the same tickets your spam rules and filter already produced — reasoning about intent to draft replies and surface borderline junk — while Freshdesk stays the system of record for how mail is quarantined and restored.

Ready to clear the tickets that survive your spam filters? Start a free trial of Macha and connect it to your Freshdesk in minutes.