From c4c3783916c0ba03f3d573310f8061cf115aeaaa Mon Sep 17 00:00:00 2001 From: dq Date: Tue, 22 Sep 2026 15:23:51 +0100 Subject: [PATCH 1/2] Document inbound-email lead matching on the contacts email_verified field 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. --- descriptions/0/api.intercom.io.yaml | 4 ++-- descriptions/2.16/api.intercom.io.yaml | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/descriptions/0/api.intercom.io.yaml b/descriptions/0/api.intercom.io.yaml index 9538d528..95c55108 100644 --- a/descriptions/0/api.intercom.io.yaml +++ b/descriptions/0/api.intercom.io.yaml @@ -34572,7 +34572,7 @@ components: email_verified: type: boolean nullable: true - description: Whether the contact's email address has been verified. Set to true to indicate you have verified the contact owns this email address, or false to mark it as unverified. Must be supplied together with an email in the same request; sending it without an email returns a 400. + description: Whether the contact's email address has been verified. Set to true to indicate you have verified the contact owns this email address, or false to mark it as unverified. Must be supplied together with an email in the same request; sending it without an email returns a 400. Verifying a lead's email also makes that lead reusable for inbound email. When an email arrives from an address that no user has, Intercom matches the sender to a lead with that address whose email is verified, instead of creating a new lead. Leads with an unverified email are not matched this way. example: true phone: type: string @@ -42799,7 +42799,7 @@ components: email_verified: type: boolean nullable: true - description: Whether the contact's email address has been verified. Set to true to indicate you have verified the contact owns this email address, or false to mark it as unverified. Must be supplied together with an email in the same request; sending it without an email returns a 400. + description: Whether the contact's email address has been verified. Set to true to indicate you have verified the contact owns this email address, or false to mark it as unverified. Must be supplied together with an email in the same request; sending it without an email returns a 400. Verifying a lead's email also makes that lead reusable for inbound email. When an email arrives from an address that no user has, Intercom matches the sender to a lead with that address whose email is verified, instead of creating a new lead. Leads with an unverified email are not matched this way. example: true phone: type: string diff --git a/descriptions/2.16/api.intercom.io.yaml b/descriptions/2.16/api.intercom.io.yaml index 75272ea0..9281eec1 100644 --- a/descriptions/2.16/api.intercom.io.yaml +++ b/descriptions/2.16/api.intercom.io.yaml @@ -28088,7 +28088,7 @@ components: email_verified: type: boolean nullable: true - description: Whether the contact's email address has been verified. Set to true to indicate you have verified the contact owns this email address, or false to mark it as unverified. Must be supplied together with an email in the same request; sending it without an email returns a 400. + description: Whether the contact's email address has been verified. Set to true to indicate you have verified the contact owns this email address, or false to mark it as unverified. Must be supplied together with an email in the same request; sending it without an email returns a 400. Verifying a lead's email also makes that lead reusable for inbound email. When an email arrives from an address that no user has, Intercom matches the sender to a lead with that address whose email is verified, instead of creating a new lead. Leads with an unverified email are not matched this way. example: true email: type: string @@ -34827,7 +34827,7 @@ components: email_verified: type: boolean nullable: true - description: Whether the contact's email address has been verified. Set to true to indicate you have verified the contact owns this email address, or false to mark it as unverified. Must be supplied together with an email in the same request; sending it without an email returns a 400. + description: Whether the contact's email address has been verified. Set to true to indicate you have verified the contact owns this email address, or false to mark it as unverified. Must be supplied together with an email in the same request; sending it without an email returns a 400. Verifying a lead's email also makes that lead reusable for inbound email. When an email arrives from an address that no user has, Intercom matches the sender to a lead with that address whose email is verified, instead of creating a new lead. Leads with an unverified email are not matched this way. example: true phone: type: string From 225ecd91371f6294c532624768e4a6528f374b92 Mon Sep 17 00:00:00 2001 From: dq Date: Tue, 22 Sep 2026 15:53:48 +0100 Subject: [PATCH 2/2] Widen the lead-matching note beyond inbound email 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. --- descriptions/0/api.intercom.io.yaml | 4 ++-- descriptions/2.16/api.intercom.io.yaml | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/descriptions/0/api.intercom.io.yaml b/descriptions/0/api.intercom.io.yaml index 95c55108..750a3146 100644 --- a/descriptions/0/api.intercom.io.yaml +++ b/descriptions/0/api.intercom.io.yaml @@ -34572,7 +34572,7 @@ components: email_verified: type: boolean nullable: true - description: Whether the contact's email address has been verified. Set to true to indicate you have verified the contact owns this email address, or false to mark it as unverified. Must be supplied together with an email in the same request; sending it without an email returns a 400. Verifying a lead's email also makes that lead reusable for inbound email. When an email arrives from an address that no user has, Intercom matches the sender to a lead with that address whose email is verified, instead of creating a new lead. Leads with an unverified email are not matched this way. + description: Whether the contact's email address has been verified. Set to true to indicate you have verified the contact owns this email address, or false to mark it as unverified. Must be supplied together with an email in the same request; sending it without an email returns a 400. Verifying a lead's email also makes that lead reusable whenever Intercom matches an email address to a contact. When inbound email arrives from an address no user has, or an outbound conversation or ticket is created for one, Intercom reuses a lead with that address whose email is verified, instead of creating a new lead. Leads with an unverified email are not matched this way. example: true phone: type: string @@ -42799,7 +42799,7 @@ components: email_verified: type: boolean nullable: true - description: Whether the contact's email address has been verified. Set to true to indicate you have verified the contact owns this email address, or false to mark it as unverified. Must be supplied together with an email in the same request; sending it without an email returns a 400. Verifying a lead's email also makes that lead reusable for inbound email. When an email arrives from an address that no user has, Intercom matches the sender to a lead with that address whose email is verified, instead of creating a new lead. Leads with an unverified email are not matched this way. + description: Whether the contact's email address has been verified. Set to true to indicate you have verified the contact owns this email address, or false to mark it as unverified. Must be supplied together with an email in the same request; sending it without an email returns a 400. Verifying a lead's email also makes that lead reusable whenever Intercom matches an email address to a contact. When inbound email arrives from an address no user has, or an outbound conversation or ticket is created for one, Intercom reuses a lead with that address whose email is verified, instead of creating a new lead. Leads with an unverified email are not matched this way. example: true phone: type: string diff --git a/descriptions/2.16/api.intercom.io.yaml b/descriptions/2.16/api.intercom.io.yaml index 9281eec1..75d8fc86 100644 --- a/descriptions/2.16/api.intercom.io.yaml +++ b/descriptions/2.16/api.intercom.io.yaml @@ -28088,7 +28088,7 @@ components: email_verified: type: boolean nullable: true - description: Whether the contact's email address has been verified. Set to true to indicate you have verified the contact owns this email address, or false to mark it as unverified. Must be supplied together with an email in the same request; sending it without an email returns a 400. Verifying a lead's email also makes that lead reusable for inbound email. When an email arrives from an address that no user has, Intercom matches the sender to a lead with that address whose email is verified, instead of creating a new lead. Leads with an unverified email are not matched this way. + description: Whether the contact's email address has been verified. Set to true to indicate you have verified the contact owns this email address, or false to mark it as unverified. Must be supplied together with an email in the same request; sending it without an email returns a 400. Verifying a lead's email also makes that lead reusable whenever Intercom matches an email address to a contact. When inbound email arrives from an address no user has, or an outbound conversation or ticket is created for one, Intercom reuses a lead with that address whose email is verified, instead of creating a new lead. Leads with an unverified email are not matched this way. example: true email: type: string @@ -34827,7 +34827,7 @@ components: email_verified: type: boolean nullable: true - description: Whether the contact's email address has been verified. Set to true to indicate you have verified the contact owns this email address, or false to mark it as unverified. Must be supplied together with an email in the same request; sending it without an email returns a 400. Verifying a lead's email also makes that lead reusable for inbound email. When an email arrives from an address that no user has, Intercom matches the sender to a lead with that address whose email is verified, instead of creating a new lead. Leads with an unverified email are not matched this way. + description: Whether the contact's email address has been verified. Set to true to indicate you have verified the contact owns this email address, or false to mark it as unverified. Must be supplied together with an email in the same request; sending it without an email returns a 400. Verifying a lead's email also makes that lead reusable whenever Intercom matches an email address to a contact. When inbound email arrives from an address no user has, or an outbound conversation or ticket is created for one, Intercom reuses a lead with that address whose email is verified, instead of creating a new lead. Leads with an unverified email are not matched this way. example: true phone: type: string