Tighten email_verified wording on contacts create/update/bulk (#696)

Author: adisan19

descriptions/0/api.intercom.io.yaml

@@ -31022,7 +31022,9 @@ components:
                 type: boolean
                 nullable: true
                 description: |-
-                  Whether the contact has proved they own this email address: `true` records that proof, `false` marks the address unverified, and omitting it leaves the current status unchanged. Send it in the same contact object as `email`; a contact object that includes `email_verified` without `email` is rejected. Behaves exactly like `email_verified` on [Create a contact](/docs/references/preview/rest-api/api.intercom.io/contacts/createcontact), which describes the field in full.
+                  Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected.
+
+                  Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address.
                 example: true
               name:
                 type: string
@@ -31171,7 +31173,9 @@ components:
                 type: boolean
                 nullable: true
                 description: |-
-                  Whether the contact has proved they own this email address: `true` records that proof, `false` marks the address unverified, and omitting it leaves the current status unchanged. Send it in the same contact object as `email`; a contact object that includes `email_verified` without `email` is rejected. Behaves exactly like `email_verified` on [Update a contact](/docs/references/preview/rest-api/api.intercom.io/contacts/updatecontact), which describes the field in full.
+                  Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected.
+
+                  Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address.
                 example: true
               name:
                 type: string
@@ -34960,13 +34964,9 @@ components:
           type: boolean
           nullable: true
           description: |-
-            Whether the contact has proved they own this email address, for example by completing a confirmation link or one-time code you sent to it. Send `email_verified` in the same request as `email`, for example `{"email": "jane@example.com", "email_verified": true}`. A request that includes `email_verified` without `email` fails with a `400`.
+            Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected.
 
-            - `true`: ownership is proved.
-            - `false`: ownership is not proved.
-            - Omitted: the current verification status stays the same.
-
-            New contacts start unverified. If you change a verified contact's email, the new address is unverified until you verify it. Only send `true` when you have that proof. When an inbound email, outbound conversation, or ticket matches a verified address, Intercom reuses that lead instead of creating a new one.
+            Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address.
           example: true
         phone:
           type: string
@@ -43361,13 +43361,9 @@ components:
           type: boolean
           nullable: true
           description: |-
-            Whether the contact has proved they own this email address, for example by completing a confirmation link or one-time code you sent to it. Send `email_verified` in the same request as `email`, for example `{"email": "jane@example.com", "email_verified": true}`. A request that includes `email_verified` without `email` fails with a `400`.
-
-            - `true`: ownership is proved.
-            - `false`: ownership is not proved.
-            - Omitted: the current verification status stays the same.
+            Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected.
 
-            New contacts start unverified. If you change a verified contact's email, the new address is unverified until you verify it. Only send `true` when you have that proof. When an inbound email, outbound conversation, or ticket matches a verified address, Intercom reuses that lead instead of creating a new one.
+            Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address.
           example: true
         phone:
           type: string

descriptions/2.16/api.intercom.io.yaml

@@ -28848,13 +28848,9 @@ components:
           type: boolean
           nullable: true
           description: |-
-            Whether the contact has proved they own this email address, for example by completing a confirmation link or one-time code you sent to it. Send `email_verified` in the same request as `email`, for example `{"email": "jane@example.com", "email_verified": true}`. A request that includes `email_verified` without `email` fails with a `400`.
+            Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected.
 
-            - `true`: ownership is proved.
-            - `false`: ownership is not proved.
-            - Omitted: the current verification status stays the same.
-
-            New contacts start unverified. If you change a verified contact's email, the new address is unverified until you verify it. Only send `true` when you have that proof. When an inbound email, outbound conversation, or ticket matches a verified address, Intercom reuses that lead instead of creating a new one.
+            Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address.
           example: true
         email:
           type: string
@@ -35667,13 +35663,9 @@ components:
           type: boolean
           nullable: true
           description: |-
-            Whether the contact has proved they own this email address, for example by completing a confirmation link or one-time code you sent to it. Send `email_verified` in the same request as `email`, for example `{"email": "jane@example.com", "email_verified": true}`. A request that includes `email_verified` without `email` fails with a `400`.
-
-            - `true`: ownership is proved.
-            - `false`: ownership is not proved.
-            - Omitted: the current verification status stays the same.
+            Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected.
 
-            New contacts start unverified. If you change a verified contact's email, the new address is unverified until you verify it. Only send `true` when you have that proof. When an inbound email, outbound conversation, or ticket matches a verified address, Intercom reuses that lead instead of creating a new one.
+            Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address.
           example: true
         phone:
           type: string