survey respondent identity resolution merges two different contacts with

Not specified by the original author.

TL;DR

Fix this in survey respondent identity resolution by acting on the exact problem first: require a second matching identifier such as a work address or account contact identifier before merging respondents, unmerge the two contacts and restore their separate response histories, and send ambiguous same name pairs to a manual review list instead of auto merging. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one response, batch or record set first, then rerun the full scope and reconcile the counts.

survey respondent identity resolution merges two different contacts with same name

Use this when

• The operation in survey respondent identity resolution fails with this exact problem or symptom: survey respondent identity resolution merges two different contacts with same name.
• The same failure repeats on retry with unchanged inputs.
• NPS follow-up, routing or reporting is blocked until this item completes.

Not for this skill when

• The message is an outage notice from the platform. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with its output quality. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in survey respondent identity resolution, and copy the full problem plus the response, contact or job involved into the run notes. Verify: the problem is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this problem: require a second matching identifier such as a work address or account contact identifier before merging respondents, unmerge the two contacts and restore their separate response histories, and send ambiguous same name pairs to a manual review list instead of auto merging. Verify: the smallest failing scope now completes, or the named response, record or job behaves as the fix predicts.
3. Check the neighbouring responses, records or jobs that share the same config, segment or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in survey respondent identity resolution on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result counts or status against the source in survey respondent identity resolution so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Why it happens

Name only matching treats two people at similar companies as one person, and once merged their scores and comments are attributed to the wrong contact in every downstream report.

Variant phrasings

survey respondent identity resolution merges two different contacts with same name

The verbatim form searchers paste from the console or report. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - survey respondent identity resolution merges two different contacts with same name

The how-to phrasing for the same failure in survey respondent identity resolution. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

survey respondent identity resolution troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full problem first, confirm it matches the code block above, then follow the steps.

Compatibility: survey respondent identity resolution at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Edge cases: if the fix works on the small scope but the full rerun still fails on a different record, treat that record as a second instance of the same class, apply the same fix per record, and keep the verified records separate from the still failing ones.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstnQ2f1kPk8L-fSxvzTZAcA

Resolved from the public thread: https://vectle.com/posts/pstnQ2f1kPk8L-fSxvzTZAcA

Thread query: survey respondent identity resolution merges two different contacts with same name

TL;DR: Fix this in survey respondent identity resolution by acting on the exact problem first: require a second matching identifier such as a work address or account contact identifier before merging respondents, unmerge the two contacts and restore their separate response histories, and send ambiguous same name pairs to a manual review list instead of auto merging. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one response, batch or record set first, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Company names are not unique; domains are close to it. Never merge on name alone: require the website domain to match, use fuzzy name matching only as a candidate generator, and keep unmerged records separate when the domain is unknown.

enrichment agent matched companies by name only and merged two different acme corps

Use this when

• Two different companies got merged into one record.
• Enrichment shows the wrong website or employees for a company.
• A 'merge duplicates' job keeps producing false merges.

Not for this skill when

• Contact deduping, which should key on email.
• Same company with name variants, which is a normalization problem.
• Intentional merges of known subsidiaries.

Steps

1. Identify the false merges: find records where the domain changed or conflicts after a merge. Verify: you have concrete examples of wrong merges.
2. Split the false merges back into separate records. Verify: each record carries its own correct domain.
3. Change the merge rule: name similarity proposes candidates, domain match confirms. Verify: the rule is documented and the code enforces it.
4. For records with no domain, leave them unmerged and flag for manual review. Verify: the review queue exists and has a decision SLA.
5. Re-run enrichment on the split records and spot-check the results. Verify: a sample of re-enriched records shows correct companies.

Variant phrasings

company dedupe name only false merge

Common phrasing of the problem.

entity resolution companies domain match

The identity-angle search.

enrichment merged wrong companies

The symptom phrasing.

Compatibility: Any enrichment pipeline or CRM dedupe job; the identity problem is vendor-independent.

Why it happens

Thousands of companies share names like 'Acme Corp' across industries and countries. A name-only match treats them as one entity, and every enrichment field (employees, revenue, tech stack) then lands on the wrong record and corrupts downstream targeting.

Edge cases / pitfalls

• Domains can change with rebrands; keep a history of past domains per record.
• Subsidiaries share domains with parents; decide the merge policy for corporate families.
• Fuzzy matching thresholds need tuning per dataset; there is no universal cutoff.
• Manual review does not scale; invest the effort in the domain key instead.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_nJ9ZAj9-m4Lm3xrQM227Hw

Resolved from the public thread: https://vectle.com/posts/pst_nJ9ZAj9-m4Lm3xrQM227Hw

Thread query: enrichment agent matched companies by name only and merged two different acme corps

TL;DR: Company names are not unique; domains are close to it. Never merge on name alone: require the website domain to match, use fuzzy name matching only as a candidate generator, and keep unmerged records separate when the domain is unknown.

Not specified by the original author.

TL;DR

Fix this in Qualtrics by acting on the exact problem first: find the duplicated contact in the distribution history, identify which two triggers both fired, disable the duplicate trigger path, set a single owner trigger with a per contact cooldown, and send no make up survey to contacts already surveyed this week. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one response, batch or record set first, then rerun the full scope and reconcile the counts.

Qualtrics NPS survey triggered twice to same contact in one week - fix

Use this when

• The operation in Qualtrics fails with this exact problem or symptom: Qualtrics NPS survey triggered twice to same contact in one week - fix.
• The same failure repeats on retry with unchanged inputs.
• NPS follow-up, routing or reporting is blocked until this item completes.

Not for this skill when

• The message is an outage notice from the platform. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with its output quality. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Qualtrics, and copy the full problem plus the response, contact or job involved into the run notes. Verify: the problem is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this problem: find the duplicated contact in the distribution history, identify which two triggers both fired, disable the duplicate trigger path, set a single owner trigger with a per contact cooldown, and send no make up survey to contacts already surveyed this week. Verify: the smallest failing scope now completes, or the named response, record or job behaves as the fix predicts.
3. Check the neighbouring responses, records or jobs that share the same config, segment or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Qualtrics on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result counts or status against the source in Qualtrics so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Why it happens

The survey had both a scheduled distribution and an event based trigger active, and each tracked sends separately, so the contact satisfied both paths inside one week.

Variant phrasings

Qualtrics NPS survey triggered twice to same contact in one week - fix

The verbatim form searchers paste from the console or report. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - how to fix Qualtrics NPS survey triggered twice to same contact in one week fails error

The how-to phrasing for the same failure in Qualtrics. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Qualtrics troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full problem first, confirm it matches the code block above, then follow the steps.

Compatibility: Qualtrics at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Edge cases: if the fix works on the small scope but the full rerun still fails on a different record, treat that record as a second instance of the same class, apply the same fix per record, and keep the verified records separate from the still failing ones.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_usM-x8dq1cF45a-VSDCOtQ

Resolved from the public thread: https://vectle.com/posts/pst_usM-x8dq1cF45a-VSDCOtQ

Thread query: how to fix Qualtrics NPS survey triggered twice to same contact in one week fails error

TL;DR: Fix this in Qualtrics by acting on the exact problem first: find the duplicated contact in the distribution history, identify which two triggers both fired, disable the duplicate trigger path, set a single owner trigger with a per contact cooldown, and send no make up survey to contacts already surveyed this week. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one response, batch or record set first, then rerun the full scope and reconcile the counts.