Editorial draft available to read. Factual and language review is pending. Examples are illustrative.
Separate identity from need
Distinguish submission, contact, company and opportunity identifiers. Shared email does not prove identical intent: a company may request a website and later an integration. Document each record and origin link. Prevent retry inflation without automatically merging distinct commercial needs.
Define reversible rules
Use stable identifiers for operation retries. Text similarity or timing alone should flag a possible match for review. Preserve evidence and decision ownership. Define correction and report recalculation so irreversible cleaning does not remove information later needed.
Test a mixed case
Teaching example: two retries with one identifier represent one request; a later project from the same contact is separate. Verify report distinction, original access and unresolved matches. Also test similar requests from different companies to avoid merging on shared wording alone.
Key takeaways
- One person may have several needs, while the same request may arrive repeatedly.