Make opportunities their own object within the database.this would allow us to treat them as own object, triggering events and workflows. Our clients use our services at least once a year. Sometimes multiple times a year.
complete
Log In
P
Pallavi Kothari
complete
You can now toggle multiple opportunities setting under automations to have multiple opportunities running in the same automation easily.
D
David Hall
Pallavi Kothari allowing multiple opportunities is good, but I think the more important thing as referenced in the title is the ability to have multiple opportunities AND have workflows select a specific opportunity for movement or change.
For example, let's say you have a home remodeler that is using opportunities to track job status. His client wants him to upgrade the kitchen and remodel a bathroom. Same customer, but 2 different jobs.
He wants to use automation to update the client on the status of the projects individually. Workflows can look for a specific opportunity in a specific stage, but what happens if both opportunities are in the same stage at the same time?
The capacity to "choose" which opportunity record gets changed or which workflows are triggered based on a specific opportunity record is important. This type of use case affects virtually every type of business.
K
Keith Besherse
David Hall YES! Multiple opportunities that are not individually indexable/searchable/findable are not complete opportunities.
P
Pallavi Kothari
Merged in a post:
Allow multiple opportunities to exist in a single workflow at the same time
D
Damian Surr
We need Opportunities to have the same capability as Appointments.
Multiple Appointments, for the same contact, can exist in a workflow at the same time.
Can you please enable that for Opportunities?
The reason is for businesses with date based events.
If we use custom value fields in the contact, then we can only process one event at the same time. But, a contact may have several open events at the same time.
We can't use Appointments, because they can't have their own custom values.
If we use Opportunity Custom Fields (instead of contact custom fields), then the problem is solved. Enabling Multiple Opportunities, for a single contact, to exist in a workflow at the same time would allow us to use the custom fields of the Opportunities in those workflows!
Suddenly, a contact could have endless enquiries and bookings open, on different dates, and all can be handled uniquely by the same workflows.
P
Pallavi Kothari
Merged in a post:
Multiple opportunities can enter a workflow simultaneously
P
Prasoon Dadhich
If a contact is having multiple opportunities and 1 of the opportunity is in the workflow, then another opportunity from the same contact will not be able to enter the workflow unless the other opportunity has moved out of the workflow.
C
Chris Grant
We have a similiar situation with use cases in businesses that are dealing with parents as the contact with multiple children who are being offered a service per child. The child is the opportunity and needs to receive various comms via the workflow.
A
Akshay Shah
HL Dev Team - this is a must - we need to get this going for business use cases that require multiple opportunities per contact. Very surprised this was not implemented yet
A
Antoine Feghali
A
Antoine Feghali
P
Prasoon Dadhich
Merged in a post:
Allow different opportunities, from the same contact, to be in the same workflow at the same time
D
Damian Surr
In the same way that multiple appointments, from the same contact, can be in the same automation at the same time.
We need this for Opportunities!
Especially for businesses that work with events.
If a single contact has multiple events, they have multiple Opportunities. This means that we can't use the contact's Custom Fields, because each event has different Custom Fields. But we COULD use the Opportunity Custom Fields!
Unfortunately, we can't, because only one Opportunity from a contact can be in a workflow at any time.
Please change this so that Opportuinites work more like appointments. They can each be in a workflow independantly, and at the same time. We can then use date fields, and other opportunity custom fields, to process the individual event.
This is how things work in Active Campaign.
The lack of this causes a huge issue with event-based businesses!
T
Tristan Martin
For Domain renewals 1 contact can have multiple domains all renewing on different dates.
For domains we don't look after - we have an opportunity to
- remind customers to renew their domains (so their emails don't go down)
- offer to look after the domain for them (so it always gets renewed)
We want an automated email reminder going out about the renewal and give this information about us being able to look after them
This is an "opportunity"
so 1 contact can have many opportunities in the same pipeline
That contact would need to be in a work flow multiple times, based upon each opportunity (so the opportunity would need to be the entity in the work flow, where as the contact just provides email and name information)
We have already got it that an opportunity stores the domain, renewal date and current registrar within it
We just need for an work flow to be able to send an email out 1 month before each opportunities renewal date and again 1 week before
then a check notice to us on 1 day after with a trigger so we can confirm they've renewed, be instructed to call them and/or send an urgent email about them letting their domain expire
Your workflow guide talks about service reminders specifically... but doesn't realise that customers can have multiple services from a business with multiple renewal dates within the same year
Y
Yusuf Young
This is essential for a B2B business, since we need to be able to send specific automated emails and follow ups to a contact based on which opportunity they are in and values within that opportunity.
Load More
→