--- # === IDENTITY === id: signal-library/retail/scoring-delivery/2026 canonical_question: "What are the confidence thresholds, delivery channels, and feedback loops for retail signal dossiers?" aliases: - "retail dossier delivery rules" - "retail signal confidence thresholds" - "retail outreach feedback loop" - "retail dossier scoring thresholds" entity_type: rule domain: signal-library > retail > scoring delivery region: global jurisdiction: global temporal_scope: 2024-2026 # === VERIFICATION === last_verified: 2026-07-16 confidence: 0.80 version: 1.1 first_published: 2026-03-30 # === TEMPORAL VALIDITY === temporal_validity: status: evolving last_breaking_change: null next_review: 2026-10-14 change_sensitivity: high # === RULE SCOPE === applies_to: domain: "signal-library > retail" price_range: null user_segment: "Signal pipeline operators delivering retail distress/transformation dossiers" context: "Scoring, routing, delivery, and feedback loop for auto-generated retail dossiers" # === CONSTRAINTS === constraints: - "First 100 dossiers require mandatory human review regardless of confidence score — auto-send is prohibited until the pipeline demonstrates >5% meeting rate across those 100 dossiers. This is a house calibration policy, not a vendor-published benchmark" - "Maximum 3 dossiers per retailer per quarter — exceeding this threshold drives unsubscribe and spam complaints, and spam complaints have a hard external ceiling (see below), not a soft one" - "Spam-complaint rate must stay below 0.10% and must never reach 0.30% — Gmail and Yahoo enforce this at the mailbox-provider level, and breaching it triggers rate-limiting (4.7.x) then outright rejection (5.7.x) for ALL of the sending domain's mail, not just dossiers [src4, src2]" - "Any sending domain exceeding 5,000 messages/day to Gmail, Yahoo, or Outlook consumer addresses must pass SPF + DKIM + DMARC and implement RFC 8058 one-click unsubscribe, honored within 2 days — Microsoft has rejected non-compliant bulk mail since 5 May 2025 [src4, src2]" - "Q4 seasonal dampening must be recalibrated against the CURRENT year's seasonal hiring forecast, not the 2024-2026 baseline — US holiday hiring fell to a forecast under 500,000 in 2025 (lowest since 2009), so a blanket 30% weight reduction now over-corrects hiring-derived signals [src3]" - "Feedback loop calibration runs after every 50 dossiers — skipping calibration cycles causes scoring drift of approximately 15-20% within 90 days as market conditions evolve. This drift figure is a house estimate from pipeline telemetry, not an external benchmark" # === SKIP CONDITIONS === skip_this_unit_if: - condition: "User needs the signal detection triggers and scoring formula, not the delivery rules" use_instead: "signal-library/retail/detection-rules/2026" - condition: "User needs to understand how raw signals are enriched into dossier-ready profiles" use_instead: "signal-library/retail/enrichment-mapping/2026" - condition: "User needs the dossier output format and template structure" use_instead: "signal-library/retail-assets/distress-dossier/2026" - condition: "User needs the collection spec, refresh cadence, or API terms for one individual signal source (SEC filings, foot traffic, job postings, employee reviews)" use_instead: "signal-library/retail-sources/{source-name}/2026" # === AGENT HINTS === inputs_needed: - key: "pipeline_stage" question: "Is the pipeline in calibration phase (<100 dossiers sent) or production phase?" type: choice options: - "Calibration phase — fewer than 100 dossiers sent, all require human review" - "Production phase — 100+ dossiers sent with >5% meeting rate achieved" - "Production phase — 100+ dossiers sent but <5% meeting rate (needs recalibration)" - key: "deliverability_status" question: "What is the sending domain's current spam-complaint rate in Google Postmaster Tools?" type: choice options: - "Below 0.10% — healthy, auto-send permitted if other conditions are met" - "0.10%-0.30% — warning band, suspend auto-send and reduce volume" - "At or above 0.30% — blocked, stop all automated sending and remediate" - "Unknown — SPF/DKIM/DMARC or Postmaster Tools not configured" # === DISTRIBUTION === canonical_source: "https://knowledgelib.io/signal-library/retail/scoring-delivery/2026" suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-07-16)" # === BUY LINKS === buy_links: [] # === RELATED UNITS === related_kos: depends_on: - id: "signal-library/retail/detection-rules/2026" label: "Retail Signal Detection Rules" - id: "signal-library/retail/enrichment-mapping/2026" label: "Retail Enrichment Mapping" - id: "signal-library/retail-assets/distress-dossier/2026" label: "Retail Distress Dossier Template" - id: "signal-library/retail-assets/transformation-dossier/2026" label: "Retail Transformation Dossier Template" related_to: - id: "signal-library/retail/overview/2026" label: "Retail Signal Library Overview" - id: "signal-library/agent-prompts/signal-stack-pipeline-agent/2026" label: "Signal Stack Pipeline Agent (orchestration prompt for the whole pipeline)" often_confused_with: - id: "signal-library/retail/detection-rules/2026" label: "Retail Signal Detection Rules (produces the score; this unit decides what to DO with the score)" solves: [] alternative_to: [] # === SOURCES === sources: - id: src1 title: "Signal-Based Outbound Metrics: What to Track in 2026" author: Salesmotion (Semir Jahic) url: https://salesmotion.io/blog/signal-based-outbound-metrics type: industry_report published: 2026-06-11 reliability: moderate - id: src2 title: "2026 Guide to Mastering Microsoft, Google, and Yahoo's Bulk Email Sender Requirements" author: Red Sift url: https://redsift.com/guides/bulk-email-sender-requirements type: industry_report published: 2026-06-24 reliability: moderate_high - id: src3 title: "Retail's Seasonal Hiring Could Hit Lowest Point Since 2009" author: Retail Dive (Dani James) url: https://www.retaildive.com/news/retail-seasonal-employee-holiday-hiring-hit-record-lows/760996/ type: industry_report published: 2025-09-24 reliability: high - id: src4 title: "Email Sender Guidelines" author: Google Workspace Admin Help url: https://support.google.com/a/answer/81126 type: official_docs published: 2024-02-01 reliability: authoritative - id: src5 title: "Signal-Based Selling 2026: Reach Buyers Before Competitors" author: SalesTarget.ai url: https://salestarget.ai/blogs/signal-based-selling-b2b-buying-signals-2026-guide type: industry_report published: 2026-06-04 reliability: moderate - id: src6 title: "The Best Time to Send an Email [2023 Research]" author: HubSpot (Flori Needle) url: https://blog.hubspot.com/marketing/best-time-to-send-email type: community_resource published: 2024-12-02 reliability: moderate - id: src7 title: "US Store Tracker Extra: Store Openings and Closures 2025 Review and 2026 Outlook — Data Graphic" author: Coresight Research (Aaron Mark Dsouza) url: https://coresight.com/research/us-store-tracker-extra-store-openings-and-closures-2025-review-and-2026-outlook-data-graphic/ type: industry_report published: 2026-01-30 reliability: high - id: src8 title: "2026 Retail Industry Global Outlook" author: Deloitte url: https://www.deloitte.com/us/en/insights/industry/retail-distribution/retail-distribution-industry-outlook.html type: industry_report published: 2026-01-08 reliability: high --- # Retail Dossier Scoring Thresholds, Delivery Channels, and Feedback Loops ## What are the confidence thresholds, delivery channels, and feedback loops for retail signal dossiers? ## Summary Generate a retail signal dossier at a composite score of 7.0+ backed by at least 2 independent signal sources; watchlist 4.0-6.9; discard below 4.0. Human-review 7.0-8.5, and everything until the first 100 dossiers are done. Auto-send above 8.5 only after those 100 clear a 5% meeting rate and only while the domain's spam-complaint rate stays under 0.10% — Gmail and Yahoo throttle there and block at 0.30%, so deliverability, not score, is the binding gate. Dampen signal weights in Q4 and amplify in Jan-Feb, but re-derive both magnitudes annually rather than treating 30% and 20% as fixed. [src4, src3] ## What Changed Since the Last Review Two constraints moved materially and now bind harder than this rule's internal thresholds. First, **deliverability is an external hard gate, not a soft target**: Gmail and Yahoo require spam-complaint rates below 0.10% and never at 0.30%, and Microsoft has rejected non-compliant bulk mail outright since 5 May 2025 — so this rule's previous "suspend auto-send if negative feedback exceeds 2%" tolerance sat roughly 7x above the level at which mailbox providers start throttling and then blocking the entire sending domain. [src4, src2] Second, **the Q4 dampener rests on a baseline that has structurally shifted**: US holiday hiring was forecast under 500,000 for 2025 — the lowest since 2009 — as retailers substituted automation, extended hours, and on-demand staff for seasonal waves, so a blanket 30% Q4 weight reduction now over-corrects hiring-derived signals and can suppress genuine Q4 distress. [src3] Signals also decay faster than the scoring model implies (a hiring spike peaks in weeks 1-2 and is stale by month 2), which makes latency, not just score, a routing input. [src5] ## Rule Generate and deliver a retail signal dossier when the composite confidence score reaches 7.0 or higher with at least 2 independent signals from different source categories. Scores between 4.0 and 6.9 go to the watchlist for continued monitoring. Scores below 4.0 are discarded. All dossiers scoring 7.0-8.5 require human review before sending; auto-send is permitted only above 8.5 after the initial 100-dossier calibration period demonstrates a >5% meeting rate, AND only while the sending domain's spam-complaint rate stays below 0.10%. Reduce signal weights during Q4 (October-December) and increase them during January-February post-holiday distress peak — but recalibrate both adjustments annually against the current year's seasonal hiring and closure forecasts rather than treating 30% and 20% as fixed constants. [src4, src3, src5] ## Evidence Signal-based outbound outperforms generic outbound by a wide and consistently replicated margin: reply rates of roughly 5-18% versus 1-3% for generic outreach, with signal-to-opportunity conversion around 10-12%, and roughly 80% of pipeline traced to a small fraction of signal sources — which is why source coverage, not volume, is the lever worth pulling. [src1] The 2-independent-source minimum is corroborated by 2026 practitioner data: combining 2+ signals on the same account converts at 5-10x the rate of single-signal or cold outreach. [src5] Signals are also perishable, and the decay curve is steep — a hiring spike peaks in weeks 1-2 and goes stale from month 2, a funding round wants contact within 48 hours for ~4x conversion, and a new VP hire peaks in the first 30 days and is dead by day 90 — so a dossier that clears 7.0 on a 60-day-old signal is worth materially less than the score implies. [src5] The Q4 dampening premise has weakened. Challenger, Gray & Christmas forecast fewer than 500,000 US retail seasonal hires for 2025 — below 2024's 543,100 (-4% year over year) and the lowest since 2009's 495,800 — with retailers explicitly substituting automation, permanent-staff hours, and on-demand pools (Target alone cites a 43,000-strong on-demand team) for seasonal hiring waves. [src3] A dampener calibrated on an era of large, noisy holiday hiring surges therefore suppresses a signal that is itself shrinking. Distress base rates also ran well under forecast: Coresight counted 8,270 US store closures against 5,270 openings in calendar 2025 — a net loss near 3,000, but far below its original 15,000-closure projection for the year and below its 2024 figure of 8,825. [src7] Deloitte's 2026 outlook points the same direction: of 330 global retail executives surveyed (86% at retailers above $1B revenue), 96% expect revenue growth and 81% expect margin expansion in 2026, even as 95% anticipate higher costs from trade policy and 66% plan supply-chain restructuring. [src8] A scoring model tuned to a distress wave that did not fully arrive will over-generate. Delivery is now gated externally. Google requires bulk senders (5,000+ messages/day to Gmail) to keep Postmaster Tools spam rates below 0.10% and never reach 0.30%, to authenticate with SPF, DKIM, and DMARC, and to implement RFC 8058 one-click unsubscribe. [src4] Enforcement has teeth and is escalating: non-compliant traffic now draws temporary 4.7.x rate-limiting and permanent 5.7.x rejection, Gmail began ramping enforcement in November 2025, and Microsoft has routed or rejected non-compliant bulk mail to Outlook consumer domains since 5 May 2025; unsubscribe requests must be honored within 2 days. [src2] On send timing, the evidence is much weaker than commonly claimed: HubSpot's survey of 150+ marketing professionals found Tuesday the most-cited best day (27%, versus Monday 19% and Thursday 17%) and 9 AM-12 PM the most-cited window (47.9% of B2B marketers) — but this is self-reported practitioner preference, not a measured open- or reply-rate lift, so midweek-morning sending is a weak prior to A/B test, not a rule to defend. [src6] ## Key Properties - **Generate threshold**: Score >= 7.0 with minimum 2 independent signals from different source categories - **Watchlist range**: Score 4.0-6.9 — continue monitoring, do not generate dossier - **Discard threshold**: Score < 4.0 — insufficient evidence for action - **Human review band**: Score 7.0-8.5 — mandatory human review before delivery - **Auto-send threshold**: Score > 8.5, permitted only after first 100 dossiers achieve >5% meeting rate AND spam rate < 0.10% - **Spam-complaint ceiling**: < 0.10% target, 0.30% hard limit — externally enforced by Gmail/Yahoo, not a tunable internal setting [src4] - **Bulk-sender prerequisites**: SPF + DKIM + DMARC and RFC 8058 one-click unsubscribe (honored within 2 days) above 5,000 messages/day per provider [src4, src2] - **Signal freshness**: Hiring spike peaks weeks 1-2 (stale month 2+); funding round act within 48h; new VP hire peaks days 1-30 (dead day 90) [src5] - **Q4 dampening**: Reduce signal weights October-December — recalibrate the magnitude annually; the legacy 30% was set against a pre-2025 hiring-surge baseline [src3] - **Q1 amplification**: Increase signal weights (legacy 20%) January-February, subject to the same annual recalibration - **Per-retailer cap**: Maximum 3 dossiers per retailer per quarter - **Calibration cadence**: Recalculate precision (meetings/dossiers sent) after every 50 dossiers - **Target precision**: >5% meeting rate (vs. 1-3% generic outbound baseline) [src1] ## Conditions - **Applies when**: Operating a retail signal detection pipeline that generates outreach dossiers for B2B sales teams targeting retailers showing distress or transformation signals - **Does NOT apply when**: Selling to non-retail verticals (signal weights and seasonal factors are retail-specific); conducting inbound-only sales motions; targeting retailers below $10M or above $5B revenue (signal detectability constraints from detection-rules unit apply) - **Confidence degrades when**: Pipeline has fewer than 50 dossiers of historical data (insufficient calibration); market conditions shift rapidly (e.g., pandemic-level disruption); scoring formula thresholds are older than 12 months without recalibration; the Q4/Q1 seasonal factors are still calibrated on pre-2025 hiring baselines that no longer describe retail staffing behavior [src3]; the sending domain's authentication or spam-complaint posture is unknown [src4] ## Constraints - First 100 dossiers require mandatory human review regardless of score — no exceptions, no overrides. This is a house calibration policy, not an externally published benchmark - Maximum 3 dossiers per retailer per quarter — exceeding this drives unsubscribe and spam complaints, which are externally capped - **Spam-complaint rate must stay below 0.10% and must never reach 0.30%.** This is enforced by Gmail and Yahoo at the mailbox-provider level and applies to the whole sending domain, not just dossier mail; breaching it triggers 4.7.x rate-limiting then permanent 5.7.x rejection, and Gmail requires seven consecutive days back under 0.30% before restoring delivery [src4, src2] - Sending domains above 5,000 messages/day to any consumer provider must pass SPF + DKIM + DMARC (minimum p=none) and implement RFC 8058 one-click unsubscribe honored within 2 days; Microsoft has rejected non-compliant bulk mail since 5 May 2025 [src2, src4] - Q4 dampening is mandatory October 1 through December 31, but its magnitude must be re-derived each year from the current seasonal hiring forecast — the legacy 30% was calibrated against holiday hiring surges that have since fallen to a 16-year low, so applying it unchanged over-corrects [src3] - Signal age is a hard input, not a nicety: do not send a dossier on a signal past its decay point (hiring spike > ~6 weeks, funding round > ~8 weeks, new executive hire > 90 days) regardless of composite score [src5] - Feedback loop calibration must run after every 50 dossiers — skipping cycles causes an estimated 15-20% scoring drift within 90 days (house telemetry estimate) - Follow-up cadence (Day 3, Day 7, Day 14) must suppress after 3 total attempts — additional attempts degrade domain reputation and push complaint rates toward the 0.30% cliff [src4] ## Rationale The scoring thresholds exist to balance precision against recall in a sales context where false positives waste expensive human outreach capacity while false negatives simply mean delayed engagement with an eventual buyer. The 2-source minimum is the highest-leverage part of the rule because compound signals convert at 5-10x single-signal outreach — the gain comes from conjunction, not from any single source's strength. [src5] Seasonal calibration exists because retail Q4 patterns (holiday hiring, inventory build-up, promotional markdowns) mimic genuine distress signals; the reason it now needs annual re-derivation rather than a fixed constant is that the underlying seasonal behavior is itself moving — the holiday hiring surge that generated most of the Q4 noise has been shrinking toward a 16-year low as retailers automate and flex existing staff. [src3] The deliverability constraints are different in kind from everything else in this rule: they are not tunable trade-offs but externally enforced limits, and breaching them degrades every future send from the domain, which is why they gate auto-send independently of score. [src4, src2] ## Framework Selection Decision Tree ``` START — User needs to configure dossier scoring and delivery rules ├── Is the sending domain deliverability-compliant? │ ├── NO (SPF/DKIM/DMARC missing, or spam rate >= 0.30%) │ │ └── STOP — remediate before any automated sending [src4] │ └── YES → continue ├── Which pipeline stage? │ ├── Calibration (<100 dossiers sent) │ │ └── ALL dossiers require human review ← START HERE │ ├── Production (>100 dossiers, >5% meeting rate) │ │ └── Apply auto-send for >8.5, human review for 7.0-8.5 │ └── Production (>100 dossiers, <5% meeting rate) │ └── Recalibrate: review detection-rules thresholds, reset auto-send ├── What season? │ ├── October-December (Q4) → Apply dampening, magnitude re-derived this year [src3] │ ├── January-February (Q1) → Apply amplification, magnitude re-derived this year │ └── March-September → Use standard weights ├── How old is the newest contributing signal? │ ├── Past its decay point → Discard or re-detect; do not send [src5] │ └── Fresh → continue ├── Score range? │ ├── >= 7.0 (2+ source categories) → Generate dossier │ │ ├── 7.0-8.5 → Human review required │ │ └── > 8.5 (production phase, spam rate < 0.10%) → Auto-send permitted │ ├── 4.0-6.9 → Add to watchlist, continue monitoring │ └── < 4.0 → Discard └── Delivery channel? ├── Score > 9.0 compound signal → Slack alert (immediate) + email ├── Score 7.0-9.0 → Email (midweek morning as a weak prior; A/B test it) [src6] └── CRM integration → Always push scored leads to Salesforce/HubSpot ``` ## Application Checklist ### Step 1: Verify deliverability posture before anything else - **Inputs needed**: Sending domain, SPF/DKIM/DMARC status, Google Postmaster Tools spam rate, daily send volume per provider - **Output**: Go/no-go on automated sending - **Constraint**: Above 5,000 messages/day to any consumer provider, SPF + DKIM + DMARC and RFC 8058 one-click unsubscribe are mandatory; if the spam rate is at or above 0.30%, stop all automated sending until seven consecutive days back under the line [src4, src2] ### Step 2: Determine pipeline stage and apply correct review policy - **Inputs needed**: Total dossiers sent to date, historical meeting rate - **Output**: Pipeline classification (calibration vs production) and review policy (all-human vs threshold-based) - **Constraint**: If fewer than 100 dossiers sent, ALL dossiers require human review regardless of score — no shortcuts ### Step 3: Apply seasonal calibration to incoming signals - **Inputs needed**: Current date, raw signal weights from detection-rules, the CURRENT year's retail seasonal hiring and store-closure forecasts - **Output**: Seasonally adjusted signal weights - **Constraint**: Q4 dampening is mandatory October-December and Q1 amplification January-February, but re-derive the magnitude from this year's forecast — carrying the legacy 30%/20% constants forward is itself a calibration error now that holiday hiring has fallen toward a 16-year low [src3, src7] ### Step 4: Score, age-check, and route the dossier - **Inputs needed**: Seasonally adjusted signal scores, number of independent source categories contributing signals, timestamp of each contributing signal - **Output**: Composite score + routing decision (generate/watchlist/discard) - **Constraint**: Minimum 2 independent signal sources required for the 7.0 threshold — a single source scoring 9.0 still goes to watchlist, not generate. Additionally, drop any dossier whose newest signal is past its decay point, regardless of score [src5] ### Step 5: Deliver via appropriate channel and cadence - **Inputs needed**: Score, pipeline stage, retailer's quarterly dossier count, recipient timezone, current spam-complaint rate - **Output**: Dossier delivered (or queued for human review) - **Constraint**: Check per-retailer quarterly cap (max 3) before sending; treat midweek-morning delivery as a testable prior rather than a fixed rule [src6]; for compound signals >9.0 also fire Slack alert ### Step 6: Record feedback and run calibration - **Inputs needed**: Delivery outcome (opened, clicked, replied, meeting booked, deal closed, unsubscribed, marked spam), provider-reported spam rate - **Output**: Updated feedback scores; precision calculation if 50-dossier threshold reached - **Constraint**: Calibration must run after every 50 dossiers; if precision drops below 5%, pause auto-send and revert to all-human-review until root cause is identified. Spam complaints are not a soft calibration input — crossing 0.10% suspends auto-send immediately [src4] ## Decision Logic ### If the sending domain lacks SPF, DKIM, or DMARC, or exceeds 5,000 messages/day without RFC 8058 one-click unsubscribe --> Do not send anything automated. Fix authentication and unsubscribe headers first; Microsoft has rejected non-compliant bulk mail outright since 5 May 2025, and Gmail escalates from 4.7.x rate-limiting to permanent 5.7.x rejection. [src4, src2] ### If the Postmaster Tools spam-complaint rate is at or above 0.30% --> Halt all automated sending immediately, regardless of dossier scores or pipeline stage. Remediate targeting and list hygiene, and expect to hold seven consecutive days below 0.30% before Gmail restores normal delivery. Between 0.10% and 0.30%, suspend auto-send and drop to human-reviewed sending only. [src4, src2] ### If the pipeline has sent fewer than 100 dossiers --> Human-review every dossier regardless of score, including 9.0+ compound signals. Auto-send stays off until 100 dossiers are complete AND the meeting rate across them exceeds 5%. [src1] ### If a dossier scores >= 7.0 but all contributing signals come from a single source category --> Route to watchlist, not generate. Compound signals (2+ independent categories) convert at 5-10x single-signal outreach, so a high single-source score is a coverage artifact rather than evidence. [src5] ### If a dossier clears 7.0 but its newest contributing signal is past its decay point --> Discard or re-detect before sending. A hiring spike is stale from month 2, a funding round from week 8, and a new-executive signal by day 90 — the composite score does not decay on its own, so age must be checked separately. [src5] ### If the current month is October, November, or December --> Apply Q4 dampening, but re-derive its magnitude from this year's seasonal hiring and closure forecasts instead of reusing the legacy 30%. US holiday hiring was forecast under 500,000 for 2025 (lowest since 2009, versus 543,100 in 2024), so the hiring-surge noise the 30% was built to cancel is substantially smaller than it was. [src3] ### If the pipeline's dossier volume is running above forecast while meeting rates fall --> Suspect base-rate drift, not a threshold problem. Coresight's 2025 actuals came in at 8,270 US closures against an original 15,000 projection, and Deloitte's 2026 outlook has 96% of retail executives expecting revenue growth and 81% expecting margin expansion — a model tuned to a distress wave that under-delivered will over-generate. Recalibrate the detection thresholds upstream before touching delivery. [src7, src8] ### If a user asks which score triggers a dossier versus how the score is computed --> This unit answers the first; route the second to Retail Signal Detection Rules [signal-library/retail/detection-rules/2026], which owns trigger definitions, compound logic, and the scoring formula itself. ## Anti-Patterns ### Wrong: Optimizing for dossier volume over precision Generating dossiers at a 5.0 threshold to "fill the pipeline" floods the sales team with low-confidence leads and pushes complaint rates toward the mailbox-provider cliff. Generic, low-signal outbound replies at 1-3% versus 5-18% for signal-based outreach, so lowering the bar converts a working channel into a spam-rate liability. [src1] ### Correct: Hold the 7.0 threshold and invest in signal coverage Maintain the 7.0 minimum and instead focus on increasing the number of signal sources monitored — roughly 80% of pipeline comes from a small fraction of signal sources, so finding and adding the sources that matter beats loosening thresholds on the ones you have. [src1] ### Wrong: Treating spam complaints as a 2%-tolerance calibration input Older versions of this rule tolerated negative-feedback rates up to 2% before suspending auto-send. That is roughly 7x above the level at which Gmail and Yahoo begin throttling: the recommended ceiling is 0.10% and 0.30% is a hard limit that triggers rejection for the entire sending domain. [src4, src2] ### Correct: Treat 0.10% as the action line and 0.30% as a wall Suspend auto-send the moment the provider-reported spam rate crosses 0.10%, and stop all automated sending at 0.30%. Keep unsubscribes as a targeting-quality signal (weight -0.5), but escalate marked_spam (-1.0) to an immediate circuit breaker rather than an input to the next 50-dossier calibration cycle. [src4, src2] ### Wrong: Carrying the legacy 30% Q4 dampener forward unexamined Applying a fixed 30% Q4 weight reduction that was calibrated on an era of large holiday hiring surges. With 2025 seasonal hiring forecast under 500,000 — the lowest since 2009 — and retailers substituting automation and on-demand staff for seasonal waves, the noise being cancelled has shrunk while the correction has not, suppressing genuine Q4 distress signals. [src3] ### Correct: Re-derive the seasonal adjustment from this year's forecast Recompute the Q4 dampener and Q1 amplifier each year against the current seasonal hiring and store-closure forecasts before the quarter starts. Keep the direction of the adjustment (dampen Q4, amplify Q1) and let the magnitude follow the data. Note also that an absent seasonal hiring ramp is no longer, by itself, a distress indicator. [src3, src7] ### Wrong: Auto-sending before calibration is complete Enabling auto-send for >8.5 scores before completing the 100-dossier human-review calibration period. Early-stage scoring models have insufficient training data; auto-sending premature dossiers drives complaint rates up and poisons the domain — and unlike a bad threshold, a burned sending reputation is not a same-week fix. ### Correct: Complete the full 100-dossier calibration with human review Every dossier in the first 100 must be human-reviewed. Only after achieving >5% meeting rate across those 100 should auto-send be enabled for scores >8.5. If the 5% threshold is not met, extend calibration and adjust detection-rules thresholds. ## Counter-Arguments - Signal-based pipelines with high thresholds miss time-sensitive opportunities — a retailer entering distress rapidly may not accumulate enough signals to reach 7.0 before a competitor identifies them through less rigorous methods. The decay data sharpens this objection rather than answering it: a funding round wants contact within 48 hours for ~4x conversion, so a 7.0-with-2-sources gate that takes a week to satisfy may be structurally too slow for the fastest-moving signals. [src5] - The 3-dossier-per-retailer quarterly cap may be too restrictive for accounts showing genuine multi-phase transformation (e.g., new CTO + digital replatforming + store portfolio restructuring happening simultaneously). Some practitioners argue for per-signal-cluster caps instead. - Q1 weight amplification risks overcorrecting for post-holiday distress — some retailers show temporary January distress that self-corrects by March without any intervention, leading to outreach that arrives after the buying window closes. - The strongest thresholds in this rule (7.0, 100-dossier calibration, 50-dossier cadence) are house policy derived from this pipeline's own telemetry, not externally published benchmarks. They are defensible as operating defaults but should not be cited to a third party as industry standards. ## Common Misconceptions - **Misconception**: Higher dossier volume equals more meetings and more pipeline. **Reality**: Meeting rates are inversely correlated with volume below the 7.0 threshold, and volume has an external cost the internal metrics do not show — every additional low-confidence send pushes the domain's complaint rate toward the 0.30% wall that blocks all mail. [src1, src4] - **Misconception**: Auto-send should be enabled as soon as the scoring model is built. **Reality**: Scoring models require calibration data from at least 100 human-reviewed dossiers to achieve stable precision. Auto-sending before calibration drives negative feedback and can damage domain reputation faster than it can be repaired — Gmail requires seven consecutive clean days before restoring delivery. [src2] - **Misconception**: Seasonal adjustment is a constant you set once. **Reality**: The seasonal noise the dampener corrects for is itself moving. Holiday hiring fell toward a 16-year low in 2025 as retailers automated and flexed existing staff, so a fixed 30% Q4 reduction that was right in 2024 is an over-correction now. Re-derive it annually. [src3] - **Misconception**: The feedback loop is a reporting dashboard. **Reality**: The feedback loop is a calibration mechanism that directly adjusts scoring thresholds. Every 50 dossiers, precision is recalculated and, if below target, triggers threshold adjustments or auto-send suspension. Treating it as passive reporting allows scoring drift of an estimated 15-20% per quarter. - **Misconception**: Tuesday-Thursday 9-11am is an established, quantified send-time rule. **Reality**: The underlying evidence is a survey of marketer preference, not a measured lift — Tuesday was the most-cited best day at 27% and 9 AM-12 PM the most-cited window for 47.9% of B2B marketers. Treat midweek mornings as a starting prior to A/B test against your own recipients, not as a calibrated parameter. [src6] ## Comparison with Similar Rules | Rule/Framework | Key Difference | When to Use | |---|---|---| | Retail Scoring & Delivery (this rule) | Confidence thresholds, delivery cadence, deliverability gates, and feedback calibration for retail-specific dossiers | Configuring the output stage of a retail signal pipeline | | Retail Detection Rules | Signal triggers, compound logic, and scoring formula that produce the raw scores | Building the scoring engine that feeds into this delivery rule | | Retail Enrichment Mapping | Data enrichment steps that transform raw signals into dossier-ready profiles | Configuring the data pipeline between detection and delivery | | Mailbox-provider bulk sender requirements | Externally enforced authentication and complaint-rate limits that override any internal policy | Any time the sending domain exceeds 5,000 messages/day to a consumer provider | | Generic ABM Scoring | Account-based marketing scoring without industry-specific seasonal calibration | Non-retail verticals or multi-vertical pipelines where retail-specific Q4 dampening is inappropriate | ## When This Matters Fetch this rule when configuring the delivery, routing, and feedback calibration of a retail signal intelligence pipeline — specifically when an agent or operator needs to know what confidence score triggers dossier generation, which delivery channel and timing to use, what deliverability limits gate automated sending, how to handle seasonal noise, and how to calibrate the feedback loop to maintain >5% meeting rates. ## Related Units - [Retail Signal Detection Rules](/signal-library/retail/detection-rules/2026) - [Retail Enrichment Mapping](/signal-library/retail/enrichment-mapping/2026) - [Retail Distress Dossier Template](/signal-library/retail-assets/distress-dossier/2026) - [Retail Transformation Dossier Template](/signal-library/retail-assets/transformation-dossier/2026) - [Retail Signal Library Overview](/signal-library/retail/overview/2026) - [Signal Stack Pipeline Agent](/signal-library/agent-prompts/signal-stack-pipeline-agent/2026)