Skip to content

Document inbound-email lead matching on the contacts email_verified field - #674

Merged
dan0505 merged 2 commits into
mainfrom
document-email-verified-lead-matching
Sep 23, 2026
Merged

dan0505 merged 2 commits into
mainfrom
document-email-verified-lead-matching

Conversation

@dan0505

@dan0505 dan0505 commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

Why?

The email_verified docs explain how to assert that a contact owns an address, but not what that assertion buys you. It decides which contact a later inbound email lands on: an email from an address no user has will reuse a lead only when that lead's email is verified, and otherwise creates a duplicate.

How?

Appends the matching behaviour to the field description in the create and update contact request schemas, on both spec versions that carry the field.

Generated with Claude Code

…ield

Inbound email reuses an existing lead only when that lead's email is
verified, so the field also decides which contact a later inbound email
from that address lands on. Adds that to the create and update contact
request descriptions.
Outbound conversations and tickets resolve a recipient the same way
inbound email does, reusing only a lead whose email is verified, so
scoping the note to inbound email understated it.
@dan0505
dan0505 merged commit 6a58852 into main Sep 23, 2026
3 checks passed
@dan0505
dan0505 deleted the document-email-verified-lead-matching branch September 23, 2026 07:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants