J
Julien Fiset
The current behavior of the two-way email sync feature causes emails to be routed incorrectly when duplicate contacts are involved. This creates a critical breach of data privacy and directly contradicts the "Only Assigned Data" permission.
🔑 Key Issue:
  • When two users have duplicate contacts for the same person, emails are not routed to the correct contact’s conversation. Instead, emails appear in the conversation linked to the wrong duplicate, exposing confidential information to unintended users.
  • The affected user also cannot see the email in their CRM, causing operational inefficiencies.
🌎 Real-World Example:
In a real estate team:
  • Realtor 1 has a contact for Notary A, and Realtor 2 has a duplicate for the same notary for their own transaction.
  • If Notary A sends an email to Realtor 2, it appears in Realtor 1’s conversation, violating confidentiality and rendering the email invisible to Realtor 2.
âť“ Why It Matters:
  • This flaw undermines the "Only Assigned Data" permission, which is essential for maintaining data security.
  • It poses a significant risk to industries like real estate and legal services where data privacy is non-negotiable.
  • It’s only a matter of time before this issue causes widespread user dissatisfaction and damages trust in Go High Level.
🛠️ Proposed Fix:
Each contact already has a unique ID visible via the URL. Email routing should respect this unique ID to ensure emails are linked to the correct contact and assigned user.
🚨 Urgency:
This is not a feature request; it is a critical bug affecting data confidentiality. Addressing this issue immediately will protect the integrity of the platform and avoid potential reputational harm.