One prospective customer calls twice about the same project, and GoHighLevel now shows two opportunities in the pipeline. The dashboard looks busier while sales staff split their follow-up across duplicate records.
Opportunity identity should represent the business enquiry, not simply the number of calls or workflow executions.
Define when a new opportunity is genuinely new
A returning caller may discuss the same request, a new service, or another location. Those cases need different rules.
| Caller situation | Possible business treatment |
|---|---|
| Follow-up on one active enquiry | Update the relevant opportunity |
| Independent new project | Create a distinct opportunity under the approved policy |
| Ambiguous relationship | Queue review rather than guessing |
| Repeated event delivery | Recognise the original operation |
Do not deduplicate every opportunity for a contact. A customer can have several legitimate active projects.
Inspect every opportunity writer
Forms, call workflows, imports, and staff may each create opportunities. A local safeguard in one voice integration cannot govern the other writers automatically.
Use the account's current supported workflow and API capabilities, verified against HighLevel's documentation. Identify the rule that chooses an existing opportunity and the rule that creates a new one.
Separate matching from delivery deduplication
Matching decides which business enquiry the call belongs to. Delivery deduplication prevents the same event from repeating a write. Both are needed when a workflow can retry.
Keep a stable operation reference and an association to the intended opportunity. If creation times out, reconcile the original result before issuing another create.
The webhook deduplication article explains why a receipt store and remote recovery are separate responsibilities.
Handle existing duplicates with a reviewed process
Do not automatically delete or merge old opportunities merely because they share a phone number. They may represent separate projects, values, stages, or authorised owners.
Preventing new duplicates and cleaning historical data should have distinct acceptance cases and recovery plans. Preserve relevant notes and associations when staff resolve a confirmed duplicate.
Test repeat calls and real new work
Use fictional cases for two calls about one enquiry, a new project from the same contact, duplicate webhook delivery, a delayed creation result, and a manual opportunity created between lookup and write.
Inspect record count, associations, stage, and follow-up owner. The integration should preserve legitimate multiplicity while preventing repeated execution from inventing more work.
Duplicate-opportunity questions
Should every call create an opportunity?
Only when the business's enquiry definition supports it.
Is one opportunity per contact always correct?
No. Define identity around the actual business process.
What should a repair review include?
Map all writers, match rules, and uncertain-create recovery before changing the workflow.