Keeping your inbox clean is essential for efficient support operations.
ArminCX provides multiple ways to automatically detect, tag, and handle spam or irrelevant tickets.

This article outlines the recommended best practices for spam handling and inbox hygiene.

1. Use Auto Solved Settings

In the settings, you can already configure certain automatic spam-related behaviors inside the Auto Resolve Settings section in the General Settings.

Examples include:

• Out-of-office replies

• Automatic system notifications

• Marketing emails

• Auto-generated responses

These filters help reduce noise before tickets even reach your team.

2. Use AI Auto-Tagging for Spam Detection

A highly recommended setup is using AI Auto-Tagging to detect and classify spam tickets automatically.

How it works

You can instruct the AI to apply a Spam tag whenever a ticket:

• is not a real customer inquiry

• contains irrelevant outreach

• contains automated or unsolicited messages

• matches specific spam patterns

Spam: “Use this tag if the message is not a real customer support request. This includes unsolicited marketing emails, phishing attempts, irrelevant automated messages, or spam that does not require any action. Do not use this tag for legitimate transactional or business-related emails such as orders, invoices, confirmations, or important system notifications, even if they do not contain a direct customer inquiry. Also examples like; "Hi, are you the one managing this brand" are Spam and should be tagged.”

Example Spam Cases

Examples you can define for the AI:

• “Hi, are you the one managing this brand?”

• Cold outreach / sales inquiries

• Link-building requests

• Automated notifications

• Marketing or partnership spam

• Irrelevant B2B outreach

The advantage:
👉 You can continuously improve the AI by adding new spam examples over time.

3. Automatically Resolve Spam Tickets

Once the AI applies a Spam tag, you can create a rule such as:

Example Rule

• IF Ticket Tag = Spam

• THEN Automatically set ticket status to Resolved

This prevents spam tickets from cluttering your open inbox and blocking agents unnecessarily.

4. Recommended Best Practice: Create a Spam Inbox / Folder

Even when automation is enabled, we strongly recommend creating a dedicated:

• Spam Inbox

• Spam View

• or Spam Folder

This acts as a backup layer so your team can:

• periodically review flagged tickets

• ensure legitimate customer tickets were not incorrectly classified

• improve AI spam instructions over time

5. Gmail Connection Settings

Inside the Gmail channel settings, you can additionally configure how Gmail spam emails should be handled inside ArminCX.

Skip Gmail Spam

When disabled:

• Spam-marked Gmail emails can still create tickets inside ArminCX.

When enabled:

• Emails marked as Spam in Gmail will NOT create tickets inside ArminCX.

This setting is useful if you want to completely exclude Gmail spam emails from your inbox and avoid unnecessary ticket creation from obvious spam messages.

5. Gmail Connection Settings

Inside the Gmail channel settings, you can additionally configure how Gmail spam emails should be handled inside ArminCX.

Skip Gmail Spam

When disabled:

• Spam-marked Gmail emails can still create tickets inside ArminCX.

When enabled:

• Emails marked as Spam in Gmail will NOT create tickets inside ArminCX.

This setting is useful if you want to completely exclude Gmail spam emails from your inbox and avoid unnecessary ticket creation from obvious spam messages.

5. Gmail Connection Settings

Inside the Gmail channel settings, you can additionally configure how Gmail spam emails should be handled inside ArminCX.

Skip Gmail Spam

When disabled:

• Spam-marked Gmail emails can still create tickets inside ArminCX.

When enabled:

• Emails marked as Spam in Gmail will NOT create tickets inside ArminCX.

This setting is useful if you want to completely exclude Gmail spam emails from your inbox and avoid unnecessary ticket creation from obvious spam messages.

6. Mark Contacts as Spam

Inside a ticket, you can manually mark a contact as Spam.

This is useful if:

• you never want to receive messages from this sender again

• a sender repeatedly sends spam or irrelevant messages

• you want to permanently block unwanted contacts from creating new tickets

Once marked as spam:

• future messages from this contact can automatically be filtered or blocked depending on your setup

• all open Tickets from this contact will automatically be closed

This is especially useful for recurring outreach spam, phishing attempts, or unwanted automated senders.

7. Dedicated Spam Settings Area

Inside the Settings, there is also a dedicated Spam section.

Here you can:

• upload spam contacts

• manage blocked/spam contacts

• review which contacts were previously marked as spam

This gives your team centralized visibility and control over spam management across the workspace.