The moment the platform creates a contact in a builder's CRM — sending a message to someone new, creating a lead from an estimate, an owner reminder — that contact's id is recorded as app-created. Both sync paths honour that list, so the echo can never re-enter. Genuinely new people the platform did not create are untouched.
Also called: lead came back after merging · CRM automation created a duplicate · resurrecting leads
- 1Recorded as a suppression key at the moment of creation, not after the fact
- 2The sync engines check the suppression list first, before any other verdict
- 3Suppression is durable and cross-device, not a per-browser flag
When the platform created a contact in a builder's CRM, that builder's own automations fired on it — new contact, send the new-lead email, create an opportunity — and the lead sync then read that opportunity as a brand-new lead. The result was a duplicate card that came back after every single merge, because the CRM opportunity behind it never died. Contacts the platform creates are now recorded on a suppression list, so the round trip cannot bounce back as a fresh lead. The reasoning is exact: a contact we created always belongs to someone who already exists in the pipeline, so their new-lead echo is never news.
- The platform's own writes bouncing back as new leads
- Merges being undone by the next sync
- Duplicates that survive every cleanup
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →