[Capture] Duplicate-interaction detection (passive + manual coalescing) #114

New issue

Closed

opened 2026-06-29 19:24:07 +00:00 by Mark · 0 comments

Mark commented

2026-06-29 19:24:07 +00:00

Owner

Problem

As #105–#108 (passive ingestion) land, users will end up with both a passive candidate ("Bob called at 3pm") and a manual entry ("called Bob at 3pm") for the same interaction. They need to merge, not duplicate.

Scope

When a passive candidate lands within ±5 min of an existing interaction with the same person, surface a "Merge?" prompt instead of two rows
Tap-to-confirm keeps the manual entry as canonical (notes + type come from the manual one; passive becomes the source-link)
Settings toggle to disable deduplication

Sibling

Depended on by: #105, #106, #107, #108 (passive sources)

Out of scope

Across-person dedup ("Bob called" and "Alice was on the line too" remain independent)
Backfill / retroactive merge after the fact

## Problem As #105–#108 (passive ingestion) land, users will end up with both a passive candidate ("Bob called at 3pm") and a manual entry ("called Bob at 3pm") for the same interaction. They need to merge, not duplicate. ## Scope - When a passive candidate lands within ±5 min of an existing interaction with the same person, surface a "Merge?" prompt instead of two rows - Tap-to-confirm keeps the manual entry as canonical (notes + type come from the manual one; passive becomes the source-link) - Settings toggle to disable deduplication ## Sibling Depended on by: #105, #106, #107, #108 (passive sources) ## Out of scope - Across-person dedup ("Bob called" and "Alice was on the line too" remain independent) - Backfill / retroactive merge after the fact