Dialer interactions: what about customers?

When the Dialer first sends a "lead" to HubSpot, it will create a new contact. Even on that first "create contact" push, the email address is mapping to "NuView Email" so there will never be an initial conflict of a duplicate contact. There is a change, however, that a customer with that matching email address exists in HubSpot, so you would get a task.

Example:

1. Customer A1 already exists in HubSpot with a Lifecycle Stage of "Customer" and email address known.
2. Dialer Lead A2 is created in HubSpot. Phone number maps to "Phone number" and email address maps to "NuView Email."
3. The workflow Ops: If Dialer Fields known, update Leads and check Customers for matches would check to see if the newly created Dialer Lead A2 is a Lead or a Customer. HubSpot will see this contact as a "Lead," so it will attempt to set source-of-truth "Email" to "NuView Email"
4. HubSpot will already know that Customer A1 has that email address, so the workflow will error:
1. 
5. Simultaneously, Dialer Lead A2 will enroll in the workflow Ops: Associate Contacts from Dialer if "NuView Email" matches "Email". This workflow will associate Dialer Lead A2 with Customer A1 with the label "Potential Merge."
1. Dialer Lead A2 will also enroll in the workflow Ops: Associate Contacts with "Potential Merge" when Phone number and First Name exactly match. If Customer A1 does not have an email address but the first name and phone number exactly match Dialer Lead A2, the association label "Potential Merge" will be applied as well.
6. After Customer A1 is associated with Dialer Lead A2, Dialer Lead A2 will go through this workflow: Merge Dialer Contacts if both Leads; create task for Deb if one is Customer. It checks to see if the associated contact is a Lead or Customer. If both contacts are Leads, they merge. In our example, Customer A1 is a customer, so they will not merge and Deb will get a task.
1.