One email per person, not per account

When the same person holds two accounts in an org, the email is claimed by the first one and the second is silently dropped — the in-app row still lands on both.

What it is

An inbox claim staked synchronously before any dispatch begins, keyed on the lowercased email address. The dispatcher logs how many duplicate inboxes it collapsed.

Also called: duplicate emails · I got it twice · two accounts same email

See it
One email per person, not per account
Area
Operations
Group
Notifications
System
Notifications
Solves
1 named problem
01planDispatch walks the recipient list in order, claiming each email address the first time it appears.
02Later recipients with an already-claimed address get email_enabled false while keeping their in-app and SMS gates.
03Claims are staked before dispatch starts so concurrent sends cannot both win one inbox.
Two roster rows sharing an address, with the second's email column greyed. notify.ts planDispatch. Sample data — no customer information appears here.
How it works
  1. 1planDispatch walks the recipient list in order, claiming each email address the first time it appears.
  2. 2Later recipients with an already-claimed address get email_enabled false while keeping their in-app and SMS gates.
  3. 3Claims are staked before dispatch starts so concurrent sends cannot both win one inbox.
Why we built it

The comment names the shape of the duplicate: 'The same person can hold two accounts (a second Clerk sign-up, or an org_members row alongside a Clerk mirror); the bell row stays per-account, but the EMAIL is claimed by the first account holding a given address.'

The problem
  • Duplicate accounts producing duplicate mail
Sound familiar?
What you get
One email per human being
In-app history stays complete on both accounts

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →