®
Spam Complaints and Feedback Loops
A spam complaint is one of the strongest negative signals an inbox provider can record about your sending. A small number is normal. A pattern of complaints tells Gmail, Yahoo, and Outlook that people do not want your email, and inbox placement suffers quickly after that.
Complaints are a measure of consent and expectation, not content. People mark email as spam when they did not ask for it, do not recognize it, or cannot find an easier way out. Fix the relationship, not the subject line.
What a Complaint Is
A complaint happens when a recipient clicks "Report spam", "Mark as junk", or a similar button in their inbox. The inbox provider records it against your sending identity. Enough of them and the provider starts filtering your mail to spam for everyone, not just the people who complained.
A complaint is different from an unsubscribe. An unsubscribe is a neutral signal. Someone opted out through the path you provided, and providers do not penalize you for it. A complaint means the recipient chose the spam button instead, either because they could not find the unsubscribe link or because they wanted to punish the sender.
Complaints are also different from bounces. A bounce means the email could not be delivered. A complaint means it was delivered and the recipient rejected it. See the Bounce Guide for how Bento handles delivery failures.
The practical rule: every complaint you can convert into an unsubscribe instead is a win. Make leaving easy.
How Feedback Loops Work
A feedback loop (FBL) is a reporting channel between an inbox provider and a sender. When a recipient marks your email as spam, the provider sends a report back to the sending platform identifying the message. The platform then suppresses that recipient so they are never emailed again.
Most major providers offer feedback loops:
| Provider | FBL available | Notes |
|---|---|---|
| Yahoo | Yes | Per-recipient complaint reports |
| Outlook / Microsoft | Yes | Reports via the SNDS and JMRP programs |
| Comcast, AOL, others | Yes | Standard ARF-format complaint reports |
| Gmail | No per-user FBL | Aggregate complaint rate only |
Gmail is the special case. Gmail does not send per-recipient complaint reports to senders. You cannot know which Gmail user marked you as spam. Instead, Gmail exposes your aggregate complaint rate in Google Postmaster Tools. If you send meaningful volume to Gmail, set up Postmaster Tools and check the spam rate dashboard regularly. It is the only complaint visibility you get for Gmail.
Bento subscribes to the available feedback loops and processes them automatically. When a complaint report arrives, the recipient is suppressed without any action from you. See How Bento Handles Complaints below.
Complaint Thresholds
Gmail and Yahoo published explicit complaint rate requirements as part of their bulk sender rules. These are the numbers to manage against:
| Complaint rate | Status | What it means |
|---|---|---|
| Under 0.1% | Healthy | Sustainable long-term target. One complaint per 1,000 delivered emails. |
| 0.1% to 0.3% | At risk | Filtering pressure builds. Investigate the segment or campaign causing it. |
| Above 0.3% | Danger | Gmail and Yahoo may reject or junk your mail broadly. Stop and fix before sending more. |
A few things to keep in mind when reading these numbers:
- Rates are calculated against delivered mail, not sent mail.
- A single bad campaign to a cold segment can push you over 0.3% for the day even if your overall program is healthy.
- Gmail evaluates your rate over time. One bad day matters less than a sustained pattern, but repeated spikes compound.
- Small senders need extra care. At 500 emails a day, two complaints is 0.4%.
Bento's Deliverability Monitor surfaces reputation and placement signals inside the app. Pair it with Google Postmaster Tools for Gmail-specific complaint data.
Why Complaints Happen
Almost all complaint spikes trace back to one of these causes:
- Cold lists. Emailing people who have not heard from you in months or years. They forgot they subscribed, so your email looks like spam to them.
- Unclear sender name. The from name does not match what the recipient signed up for. If they subscribed to "Acme Weekly" and the email arrives from "Jane Smith", they will not recognize it.
- Frequency mismatch. They expected a monthly digest and got daily promotions. Or they signed up for a download and entered a long sales sequence they never agreed to.
- Hard-to-find unsubscribe. Tiny grey text, buried footers, or multi-step opt-out pages push people to the spam button because it is faster.
- Purchased or scraped lists. These recipients never opted in at all. They complain at high rates and often include spam traps. This is the fastest way to destroy a sending domain.
Never import a purchased, scraped, rented, or "partner" list into Bento. Beyond the complaint damage, these lists violate Bento's terms and will stall your account during approval and warmup.
Content matters less than people expect. A clean, well-designed email sent to people who did not ask for it still gets complaints. A plain text email sent to an engaged list does not.
When Complaints Spike
If your complaint rate jumps, work through this sequence:
- Pause broad sends. Stop campaigns to large or mixed segments immediately. Every additional send to the affected audience adds complaints.
- Identify the source. Compare complaint rates by campaign and by segment. A spike usually traces to one send, one list source, or one automation step.
- Segment to engaged recipients only. Resume sending only to people who opened, clicked, or purchased in the last 30 to 90 days. Engaged recipients almost never complain.
- Fix sender recognition. Make sure your from name matches your brand, your subject lines match the content, and the first line of the email reminds people why they are receiving it.
- Make unsubscribing obvious. A clear unsubscribe link beats a complaint every time. Bento adds one-click unsubscribe headers automatically, but the visible link in your template should be easy to find too.
- Audit your list sources. Check where recent imports came from. Remove contacts with unclear consent. Consider double opt-in for risky signup sources, and review list hygiene practices for older segments.
Recovery is gradual. Complaint rates fall as the bad segment stops receiving mail and engaged sends dilute the history. Expect days to weeks, not hours. If your mail is already landing in spam, follow the Spam Recovery Guide.
How Bento Handles Complaints
Bento handles the mechanical side of complaints for you:
- Automatic feedback loop processing. Bento receives complaint reports from providers that offer feedback loops and processes them without any setup on your side.
- Automatic suppression. When someone complains, Bento suppresses them so they are never emailed again. This protects your reputation from repeat complaints by the same person.
- Per-site suppression list. Complainers join your site's suppression list alongside unsubscribes and hard bounces. Suppressed addresses are excluded from all future sends, including imports that contain them.
- One-click unsubscribe headers. Bento adds List-Unsubscribe and one-click unsubscribe headers to your emails automatically. Gmail and Yahoo require these for bulk senders, and they give recipients an easy exit that does not count against your reputation.
What Bento cannot do is control why people complain. Consent, sender recognition, frequency, and list sourcing are yours to manage. Keep your complaint rate under 0.1%, watch Google Postmaster Tools for Gmail, and treat any spike as a signal to pause and investigate.
For the broader picture, start at the Deliverability Guide. For provider-specific behavior, see the Yahoo and Outlook guides.