Avoid applying customer mapping to HelpScout conversations when in excluded domains #6060
+218
−60
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
zoldar
force-pushed
the
helpscout-mapping-improvement
branch
from
34d8fc6 to
b6292f2
Compare
zoldar
force-pushed
the
helpscout-mapping-improvement
branch
from
b6292f2 to
3163f0e
Compare
aerosol
approved these changes
Feb 10, 2026
Member
aerosol
left a comment
aerosol
left a comment
There was a problem hiding this comment.
Looks fine, extract the migration please
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
This PR does two things:
This allows to preserve the mapping change in HelpScout integration for a particular conversation while preventing from that mapping leaking to other unrelated conversations (because, for instance, payment service representative is often starting new conversation threads for various customers).
The migration in this PR will be extracted and deployed separately before the rest of the changes after the PR is approved.
Tests