Correction email after a factual error in a sent outreach batch (severity x reach rule)
Harvested 2026-10-27 (skills harvest, tied to the project lead 12:21: Parcel A / 1970 green — "Emails might have been sent causing confusion too").
The rule practitioners converge on
Decide by two things only: how SERIOUS the error is (does it change a decision the reader could make?) and how many recipients it REACHED. - Cosmetic / low-reach (typo, broken link to a non-essential page, under ~5% affected, nobody replied within an hour): send nothing. A correction draws more attention than the mistake. - Substantive (wrong fact, wrong price, wrong scope, anything a reader could act on): correct fast — practitioners quote 90 minutes to 2 hours — in a short note.
Practitioner testimony (Westfield Creative expert roundup, posted 1 May 2026, read 27 Oct 2026)
- Smarfle CRM (Natalia Lavrenenko): under 5% reached + no support emails in an hour -> do nothing; money/segment errors -> apology in 90 min, subject "fixing this from earlier", two sentences. A groveling "important update" correction for a $30 price typo made unsubscribes SPIKE: people had not noticed, and the subject read as the wrong urgency. Tone of a customer-service reply works better.
- Discount listed 30% but applied 10%, caught 6 h after send: honoured 30%, short note acknowledging the glitch -> 42% open on the correction; "it actually built trust".
- Expired code: correction within 90 min + 48 h extension -> correction outperformed the original, +23% click rate.
- Plan features wrongly listed (false expectation that could drive decisions): correction within 2 h, plain subject "Correction: We got the plan details wrong", no elaborate apology, just the corrected facts.
- HubSpot resend: only to people who opened but did not click, new subject, "We've fixed your link", no "sorry for sending this twice" -> CTR up (no figure given).
- Really Good Emails school (Apr 2025) cites "one survey" (8% more positive attitude with an apology; apology + discount +120% purchases) — source not named, NOT checked; don't quote it. All of these are single-company anecdotes (marketing lists), not controlled tests.
How to write it (cold B2B / institutional version)
- Confirm the error against the primary record FIRST (drawing, register entry). Never correct a correction.
- Reply IN THE SAME THREAD to each recipient (same subject, "Re:"), so it sits next to the original — no new campaign, no tracking pixels.
- Subject (if a new thread is unavoidable): "Correction:
in my email of 27 October". Plain, factual. - Body, 3-5 lines: one line naming what was wrong; one line with the correct fact and its source; one line pointing to the corrected page (same URL); one line of thanks. No grovelling, no re-pitch.
- Send only to people who received the wrong statement. If the error was only on the linked page (not in the email body), fixing the page is usually enough; correct by email only those who replied, clicked, or might act on it.
- Log it (CRM task note: what was wrong, when fixed, who was told).
How we apply it to Cedwyn
- Parcels outreach (30 businesses, 27 Oct): the worker checking the green/Parcel A must first answer "did the EMAIL BODY state the green is in Parcel A, or only the page?" Page-only -> fix the page (same URL) and send nothing unless a recipient replied. Body stated it -> one in-thread correction per recipient, drafted as HubSpot tasks "[PARCELS CORRECTION DRAFT — DO NOT SEND without the project lead]"; the project lead sends.
- Draft skeleton (raising-a-concern tone, no banned words): "A correction to my email of 27 October: the area described as Parcel A ends before the village green registered in 1970; the green is a separate parcel. The page at the same link now shows this. Thank you for your patience."
- Never pair a correction with the parcels follow-up (2-4 Nov); keep them separate so the follow-up isn't read as a second correction.
Sources
- westfield-creative.com (posted 1 May 2026; read 27 Oct 2026)
- reallygoodemails.com (Apr 2025; survey figures unsourced, not checked)
Raw Markdown: correction-email-after-factual-error-severity-reach.md · version and changes: changelog · machine index: agents.json