Role-based address flagging

Role-based addresses (info@, admin@, support@, noreply@) route to shared inboxes staffed by multiple people, none of whom opted in personally. They generate disproportionate complaint rates because recipients feel no ownership of the subscription and report spam at 3–5× the rate of personal addresses. Campaigns sent to role addresses also score lower engagement — shared inboxes are typically managed for task completion, not reading newsletters — which trains ISP filters to classify your domain as low-value. Elevated complaint rates from these addresses can trigger CAN-SPAM enforcement scrutiny, since complaints are one of the signals ISPs forward to the FTC.

Detect role-based prefixes at ingest and store a flag on the contact record to gate campaign eligibility:

const ROLE_PREFIXES = [
  'info', 'admin', 'support', 'hello', 'noreply', 'no-reply',
  'postmaster', 'webmaster', 'contact', 'sales', 'team',
  'abuse', 'hostmaster', 'help', 'feedback'
]

function isRoleBased(email: string): boolean {
  const local = email.split('@')[0]?.toLowerCase() ?? ''
  return ROLE_PREFIXES.some(prefix => local === prefix)
}

await db.contact.create({
  data: { email, is_role_address: isRoleBased(email) }
})

Add where: { is_role_address: false } to cold campaign segment queries. Transactional sends (receipts, password resets) can still reach role addresses — exclude them from marketing campaigns only.