What is a spam complaint, and how many is too many?

What counts as one

A spam complaint is a recipient pressing the spam or junk button on a message in their own inbox. It is a manual act by a person, not a filter decision.

systeme.io shows it in the statistics table as a column called Average percentage of spam reports per opened email. The tooltip on that column spells the calculation out: the spam report percentage is the ratio of spam reports to the open rate.

That denominator is the part worth pausing on. A complaint rate measured against opens is a much smaller pool of people than the same rate measured against everything sent, so the percentage climbs faster than most people expect.

What it does to the contact

When a contact marks one of your emails as spam, systeme.io automatically moves them to Bounced status. They receive nothing from the account after that, with no action needed on your side.

How many is too many

Three published numbers apply, from three places, and they are not the same number.

The first decides which pool of sending IP addresses the account uses:

Quarantine is the one to watch, because it does not wait. Emails sent in the last 24 hours are checked, and crossing 1% moves the account there immediately rather than at the next review.

The second is systeme.io's guidance on reading the figure day to day:

The third is Google's, quoted in systeme.io's own guidance: do not go over 0.3% of spam reports per sender domain. Passing it repeatedly degrades deliverability in a way that lasts.

The three scales disagree with each other. Working to the tightest of them, under 0.08%, keeps an account clear of all three.

The complaints you cannot see

Gmail does not run a normal feedback loop. When a Gmail user reports an email as spam, that report is not passed back to the sender or to systeme.io, so it never reaches the statistics. systeme.io leaves Gmail open rates out of the spam percentage calculation for the same reason.

Google Postmaster Tools is the way to see it. It reports the user-reported spam rate for your own domain, alongside authentication status and delivery errors.

Setting it up means verifying the domain with a TXT record in your DNS, or a CNAME record if the TXT gives trouble. systeme.io asks to be added as a user on each domain, with the address customers-gpt@systeme.io, so its own team can read the same data when helping you.

What to do about a rate that is climbing

• Make unsubscribing obvious. A reader who does not want an email has three options: unsubscribe, stop opening, or report it as spam. The first is the good outcome, so the link has to be findable.
• Check where the list came from. Bought lists are strictly forbidden on systeme.io, and it does not allow addresses found on the internet either, yellow pages and public social profiles included. They are the fastest route to complaints.
• Turn on double opt-in and reCAPTCHA. Between them they keep bots and addresses that never asked for anything off the list in the first place.
• Reconfirm an old list before mailing it. Consent given long ago is still consent, but a contact who has not heard from you in a year may not remember giving it. Asking whether they still want the emails is the documented fix.
• Keep the sender name, subject and content consistent. A subject line that does not match what is inside earns complaints, and systeme.io runs an internal filter that blocks misleading subject lines before they go out.

What happens if it stays high

systeme.io monitors accounts daily and suspends sending from an account when an indicator is abnormally high. It describes that as a security measure taken in the interest of all its users.

List bombing is the harshest version. If bots flood one of your forms with fake sign-ups and the resulting rejections put systeme.io's sending addresses at risk, email sending can be suspended temporarily, and it is reinstated only after you complete a remediation plan their team provides.