Spam is not a lead source: investigate complaints before counting results

A contractor reports new leads, while support receives messages saying, “I never asked you to contact me.” Counting those objections as engagement makes the acquisition report look healthier precisely when the process is harming people. The advertiser needs two separate decisions: how to stop the unwanted contact, and which commercial outcomes can actually be accepted. Neither decision should depend on persuading the complainant to become a customer.

This guide produces a complaint ledger, a source investigation and a costed decision about stopping or replacing the route. It concerns unsolicited acquisition and complaint handling, not buying a contact database or diagnosing forced browser visits. The legal references concern UK electronic marketing; translations and example currencies do not extend those rules to other countries. Gmail documentation describes that service, not universal law. Both ordinary-service examples are invented exercises, not AffiliateCore customer results. USD amounts are independent assumptions, not exchanged UK prices.

1. Separate unwanted contact from a requested service

A reply can be a complaint, a refusal, a request for information or an actual service inquiry. A message saying “remove me” is not a qualified lead. A click can have been made to find the unsubscribe control. A delivered email does not establish that the recipient wanted it. Record the action in its original context before giving it a sales label. Your operational objective is to prevent further unwanted acquisition, not to improve apparent response rates.

The ICO’s UK electronic-mail guidance distinguishes recipient categories and exceptions; the page is under review. Do not assume that every business address has the same treatment. The ICO also explains objections and suppression records. Obtain an applicable assessment before making a legal eligibility decision. Here the exercises use a stricter operating condition: documented voluntary requests, no reliance on an unverified exception.

The Gmail sender guidelines address authentication, complaints and unsubscribe mechanisms for personal Gmail accounts. Technical delivery is not permission. Do not interpret a provider metric below a published threshold as an allowance to ignore a complaint. This article does not configure sending systems, raise sending limits, replace blocked domains or provide methods of contacting people who objected.

2. Build a complaint record that is not a sales list

Before reviewing the first incident, assign a complaint owner, a campaign owner able to pause the supplier and a reviewer for disputed outcomes. Obtain read access to your own CRM, invoices, agreed source restrictions and relevant campaign records. Keep the complaint workspace separate from promotion lists. People who report an incident must not be enrolled into a “customer recovery” campaign merely because they contacted support.

Use these fields: incident ID; received time and timezone; channel; complainant’s requested remedy; minimal contact identifier; message date; displayed sender; campaign or supplier ID if known; source claimed by supplier; request evidence reference; opt-out time; subsequent-contact evidence; containment action; response owner; supplier explanation; decision; follow-up date. Unknown values remain unknown. Preserve originals with limited access and use redacted working copies. Do not ask for passwords or a full inbox export.

Store three counts separately: complaint messages, distinct complainants and commercial inquiries. Three messages from one person may concern one unresolved incident. The number of inquiries is not automatically the denominator for a complaint rate. If you lack a reliable delivered-message population for the same route, period and recipient scope, report the observed counts and the missing denominator. Never fill that gap with a contractor’s estimate and present it as a measured rate.

For a suitable partner programme, start with permitted-source rules and acceptance definitions for your own offer in our AffiliateCore. Prepare an advertiser profile if that workflow fits the product. State that complaints, objections and unsubscribe clicks are not payable inquiry events. Product eligibility and review still apply. This article does not claim that AffiliateCore automatically synchronises every supplier’s suppression list or investigates mail headers; keep those responsibilities explicit and verify the actual integration before relying on it.

3. Contain the incident, then investigate its cause

1. Acknowledge without selling. In an authorised support conversation, confirm the requested remedy and explain the next review step. Do not append a discount, referral link or request to reconsider. If the person asked for no further reply, respect that request except where a necessary response is independently justified.
2. Stop the relevant marketing action. Apply the objection to the systems you control and notify the responsible supplier through the agreed process. Pause the affected acquisition segment while evidence is incomplete. Do not promise that every external system has updated until its owner confirms completion.
3. Preserve a minimal trace. The complainant may voluntarily provide the relevant message and timestamp through a safe support route. Gmail documents viewing the original message headers. Redact personal and authentication data before sharing. A displayed brand name alone does not prove which party sent the message.
4. Compare claims with records. Match supplier ID, time, message version and any request evidence. Check whether an objection preceded later contact. Consider a forwarded message, mistaken brand attribution or an old queued action as alternative explanations. These possibilities call for evidence; they do not excuse a confirmed repeat.
5. Ask the supplier a bounded question. Request the relevant source, scope, request record, exclusion result and explanation of the particular incident. Do not accept an entire contact database as a substitute. Record discrepancies and allow a reply under the agreed dispute process; do not invent retrospective payment conditions.
6. Verify the correction without contacting the person again. Inspect exclusion status and pending work with the system owner. Use synthetic internal records to test re-import and queue behaviour. A real complainant must not receive a test advertisement. Keep unresolved reachability or unknown supplier state visible in the closure record.

A possible support template is: “We recorded your request to stop promotional contact. The restriction in the system we control has been applied at [time]. We are reviewing the reported source under reference [ID]. We will not use this complaint to send offers.” Only state completed actions that can be demonstrated. The ICO’s public information on unwanted marketing emails is a separate route for people seeking guidance; handling a complaint must not obstruct their choices.

4. Exercise: a contractor’s apparent leads include objections

A home-maintenance advertiser discovers complaints about a contractor’s earlier email acquisition. The agreed material had offered a voluntary repair estimate, but support receives accounts of unrequested messages. The team does not run another campaign to reproduce the issue. It freezes new supply, preserves the reported messages and reviews the seven-day historical cohort over a fourteen-day outcome window. The material used in this exercise is an incident card and a contractor evidence request, not a spam template.

Nine complaint messages come from six people. One person sent three messages, another sent two, and the remaining four sent one each: 3 + 2 + 1 + 1 + 1 + 1 = 9 messages from six people. The workload count and person count therefore differ. The supplier cannot produce a reconciled delivery denominator. Report nine messages and six complainants; do not label six divided by all leads a provider spam rate. One record shows a marketing action after an earlier objection. That repeat triggers immediate containment, regardless of how many purchases the source claims.

The contractor reported 120 inquiries. Review assigns mutually exclusive categories: 20 duplicates, 30 people denying a service request and 20 records with unresolved source evidence. Fifty remain eligible; ten withdraw before acceptance, leaving 40 accepted inquiries. Fifteen become paid jobs and three are refunded, leaving 12 retained jobs. The complaint ledger overlaps these records and must not be subtracted again. Valid service requests can be handled under their own scope without turning objections into new marketing permission.

Costs are USD 720 supplier spend, USD 180 intake work, USD 150 investigation, USD 60 exclusion remediation and USD 90 tools: USD 1,200. A settled supplier credit of USD 240 reduces this to USD 960. Count the credit only after it is actually agreed and booked. All setup and labour are charged to the cohort. No separate partner commission, non-recoverable acquisition tax, currency charge or payment fee is assumed; add them if present rather than hiding them in the cost per lead.

Cost per accepted inquiry is 960 ÷ 40 = USD 24. Cost per retained customer is 960 ÷ 12 = USD 80. Assume USD 60 contribution per retained job after service delivery, payment charges, applicable taxes and operational refund losses. Total contribution is 12 × 60 = USD 720; the residual after acquisition is minus USD 240. Without the credit, retained-customer cost is USD 100 and the residual is minus USD 480. Fixed company overhead is still excluded, so these are contribution calculations, not net profit.

The preset ceiling was USD 70 per retained customer. The route fails both that gate and the repeat-contact gate. Stop the disputed supply, retain evidence for the defined purpose, settle genuine results under existing terms and require a documented correction. A reimbursement does not establish permission or repair every consequence. Reputation damage, regulatory exposure and future support costs are unquantified here; do not invent a monetary estimate to make the example look complete.

5. Exercise: test a correction and replace unsolicited acquisition

A household repair service replaces the disputed route with a clearly labelled placement in a permitted local directory. The visible material says: “Read our service area and request an estimate if you need a repair.” The landing page provides useful information without a form submission. A person can separately request service; that request is not automatically a newsletter subscription. This is a replacement with voluntary inbound interest, not a method of making unwanted email appear acceptable.

Before purchasing the placement, the team tests its complaint process internally. Synthetic record A has an objection, record B is a fresh service request and record C is an old excluded record imported again. A and C must stay outside promotional work; B must retain the scope of the request without automatic subscription. Inspect the test state with the responsible owner, send no external messages and save the result. Also check that pending work cannot restore A through a stale export.

The pilot uses seven acquisition days, fourteen follow-up days and a separate placement identifier. Sixty inquiries arrive: six duplicates and four outside the service area leave 50 eligible. Ten withdraw, leaving 40 accepted. Twenty-four jobs are paid and four refunded, leaving 20 retained. One person complains about a message attributed to the brand. Review finds evidence of a separate unrelated sender, but the team still records the person’s preference in its own system. Do not erase the complaint or claim “zero complaints” after reclassification.

Full costs are USD 400 placement, USD 120 creative, USD 160 handling, USD 100 quality and complaint-process testing, and USD 60 tools: USD 840. No supplier credit is assumed. Separate commissions, non-recoverable acquisition taxes and exchange costs are zero in this exercise, not universally absent. Accepted-inquiry cost is 840 ÷ 40 = USD 21. Retained-customer cost is 840 ÷ 20 = USD 42. At USD 55 contribution per retained job after fulfilment, payments, taxes and refund losses, contribution is USD 1,100 and the residual USD 260 before fixed overhead.

The commercial ceiling is USD 45 per retained customer. If four additional jobs are refunded, 16 remain: 840 ÷ 16 = USD 52.50; contribution falls to USD 880 and the residual to USD 40. To meet the same ceiling at 16 jobs, acquisition spend would need to be no more than 16 × 45 = USD 720. That sensitivity argues against automatically increasing budget even though the base cohort looks acceptable.

The operational gate is independent: no confirmed repeat promotional contact after an objection, no unresolved source gap and a verified exclusion test. A single confirmed repeat stops further acquisition through the affected route; a complaint alone triggers review rather than an automatic fraud finding. Complete another cohort under unchanged definitions before considering expansion. The hypothetical comparison does not prove incrementality, since audiences and exposure between the old and replacement route are different.

6. Make the correction survive a handoff

Use a handoff card: incident owner; supplier acknowledgement; affected route; pause time; excluded records reference; pending-work review; synthetic test result; commercial adjustments; unresolved items; restart approver; next review date. A contractor change must not reset these obligations. Keep necessary exclusion identifiers separate from active acquisition data, with access and retention justified for the applicable context. Do not retain full complaints indefinitely merely because storage is inexpensive.

Put the permitted source, payable event and complaint responsibilities into the offer preparation process. Open the AffiliateCore advertiser workspace to review the proposal information you can supply. Confirm product acceptance and the actual partner review process before activation. For suppliers outside that workflow, use a directly agreed contract and internal incident register. Neither route removes the need to verify that the person’s preference reaches every responsible operator.

7. Close with evidence, not a reassuring label

Check that objections are no longer counted as leads, unique complainants are separate from messages, the denominator is stated honestly, source evidence is preserved, supplier answers are recorded, exclusions survived the internal test, and costs include investigation and cancellations. Classify the outcome as confirmed breach, unresolved evidence or unsupported attribution with reasons. A sales success must not erase a complaint, and an allegation must not automatically erase unrelated genuine work.

Your assignment is to complete one incident card, the six investigation steps and both cost formulas before accepting the next cohort. Decide between stopping the route, keeping it paused pending evidence or authorising a bounded voluntary replacement. Related boundaries are covered in contact resale and provenance and forced browser visits. Here the central question is whether unwanted outreach stops and the complaint is resolved without becoming another acquisition attempt.

Official sources were opened on 18 October 2026. The process, templates, budgets and thresholds are editorial exercises. The ICO page’s review notice means its current detailed guidance should be rechecked before an actual legal decision. Public-source access does not certify a contractor or establish a live product integration.