Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mixing customers within one contact from different inboxes #7244

Open
hmoghtafari opened this issue Jun 2, 2023 · 3 comments
Open

Mixing customers within one contact from different inboxes #7244

hmoghtafari opened this issue Jun 2, 2023 · 3 comments
Labels
need-more-info This issue does not have enough information to start working on it.

Comments

@hmoghtafari
Copy link

Describe the bug

Description
When a customer sends an email to the EMAIL_... inbox from the email address .....yan_18@mail.ru, the system is incorrectly associated it with a different contact named ANDREY, who has a different email address (....mov@gmail.com). Instead of creating a new contact for the new email address, the self-hosted Chatwoot system mistakenly recognizes it as ANDREY, resulting in a mix-up of conversations.

Screenshots
1-1
1-2

To Reproduce

When a customer sends an email to the EMAIL_... inbox from the email address .....yan_18@mail.ru, the system is incorrectly associated it with a different contact named ANDREY, who has a different email address (....mov@gmail.com). Instead of creating a new contact for the new email address, the self-hosted Chatwoot system mistakenly recognizes it as ANDREY, resulting in a mix-up of conversations.

Expected behavior

The self-hosted Chatwoot system should create a new contact for the email address .....yan_18@mail.ru, as it is from a different customer, rather than associating it with the existing contact for ANDREY.

Actual Behavior
The email from .....yan_18@mail.ru is incorrectly associated with ANDREY's contact, causing the conversation history to display the wrong conversation.

Environment

Other [please specify in the description]

Cloud Provider

AWS

Platform

None

Operating system

No response

Browser and version

No response

Docker (if applicable)

No response

Additional context

No response

@pranavrajs
Copy link
Member

@hmoghtafari Can you please share the original email headers? Does it have reply-to email address set?

@pranavrajs pranavrajs added the need-more-info This issue does not have enough information to start working on it. label Jun 2, 2023
@hmoghtafari
Copy link
Author

@pranavrajs if you are asking for the user's email, I don't have access to that one, and reply-to is not set.

@hmoghtafari
Copy link
Author

Hi @pranavrajs ,
Do you have any updates on this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need-more-info This issue does not have enough information to start working on it.
Projects
None yet
Development

No branches or pull requests

2 participants