Bring back the Allow Duplicate Opportunities Checkbox in the New Create Opportunity action (Wofklow Level)
P
Puzzles Consulting
In the legacy version of Create/Update Opportunity, we have the option to check a box if we want to allow the creation of duplicate opportunities for the same contact, regardless of how that's set up at the subaccount level (business settings).
I'd love to see that in the new Create Opportunity action.
Here's the use case:
An elderly couple signs up to a service via a form submission.
A contact gets created for the first one to sign up, while it just updates for the second because they share phone numbers, have no emails and contact duplication is just insane.
However, that form submission also triggers a webhook to the client's software where they each get assigned a unique ID.
With the legacy action, after GHL got a response from that webhook, it would create individual opportunities for each person in an existing clients pipeline for the business, where they each get separate treatment and are easily identifiable by their IDs.
Now I'm getting errors on the last step because I can't have duplicate opportunities. I know I could just allow duplicate opps at the global level, but that would be troublesome for the overall process, and - in this specific case - I only need it for this purpose.
We used to be able to work beautifully by allowing it at a workflow level so, can we have that back, please?
Thanks in advance!
Log In
S
Simran Narula
This is definitely needed, we don't want to enable this sub-account wide but only in a granular automation step for a specific use case. If we do sub-account wide it will mess up a lot of other automations which depend on not allowing duplicates so the lead moves from one stage to another.
A
Ammon Allen
We would use duplicate opportunities to track re-purchase/multiple sales with the same client.
Much needed!
D
Daniel Illingworth
Please help us out with this. Granular duplicate permissions (per action rather than global) are incredibly useful, and I would like to migrate to the beta create/update actions but can't because of this missing feature.