Spam and Non-Customer Ticket Patterns

This article defines the patterns used to identify tickets that are not legitimate customer support requests. These tickets should be closed without sending a reply.

Automated Notifications and System Emails

Emails from automated systems that are not customer-initiated:

Zapier workflow notifications
Automated notification/message/reply/email (from any platform)
"Do not reply" or "noreply" sender addresses
Internal notification emails forwarded to support
Domain renewal notices (e.g. GoDaddy, Namecheap, Google Domains)
SSL certificate expiration warnings
Server monitoring alerts
Backup completion notifications

Solicitations and Marketing

Unsolicited commercial emails from vendors or marketers:

SEO, web design, or digital marketing service offers
UI/UX design solicitations
Lead generation service pitches
Software vendor cold outreach
Recruiting/staffing agency outreach
Partnership or co-marketing proposals
Press/media inquiry from unknown outlets
Survey or research participation requests

Logistics and Freight (Misdirected)

Emails from shipping/logistics companies not related to a Styku order:

Booking requests with cargo/freight terminology
Shipper's Letter of Instruction (SLI)
Import documentation requests
Emails containing: freight, cargo, shipper, forwarder, shipment, consignment (when not about a Styku scanner order)

Key Distinguishing Signals

A ticket is spam if it meets ALL of these criteria:

The message is not from a Styku customer (no scanner, no subscription, no account found)
The message content is unrelated to Styku products or services
The message is either automated, a solicitation, or misdirected

A ticket is NOT spam if:

The sender has a Styku account, scanner, or subscription — even if the message seems off-topic, it may be a confused customer
The message mentions Styku, body scanning, or any Styku product by name
The sender is replying to a previous Styku support conversation