Custom code email typo detection (common domain misspellings)

Outcome. Contacts with a likely misspelled email domain, such as "gmial.com" or "yahooo.com", get flagged with a suggested correction, instead of bouncing silently on the first send and never being noticed until a campaign report shows a dead address.

Workflow map Enrollment, branches and actions at a glance data-quality-028

flowchart TD
    A[Email known or changed] --> B[Custom code: check domain against misspelling table]
    B --> C{Domain matches a known typo?}
    C -->|yes| D[Flag Possible typo, set suggested correction, create task]
    C -->|no| E[Status: Looks fine]

When to use it, when not to

• UseUse it right after contact creation or an email edit, catching typos before the first nurture email or sales outreach goes out and bounces.
• UseUse it as a flag-and-suggest tool, not an auto-correct. Changing someone's actual email address without confirmation risks sending to the wrong person entirely if the "typo" was actually correct and unusual.
• SkipDo not use it expecting full email validation, syntax, mailbox existence, or disposable-address detection. This fiche only checks the domain against a fixed list of common near-miss misspellings of major providers.
• SkipDo not use it on a portal where most contacts use varied, unpredictable business domains; the fixed-typo-list approach only pays off for the handful of very common consumer domains people mistype often.