Great minds think alike

There is currently no way to get notified when an account ,especially paid seat accounts, gets deactivated. If an "account status" property existed, it would be easier to get notified of these changes and set up workflows in place to update contact ownership of deactvied accounts.  ...read more

Right now I can use negative statements to say a property value "does not have X" "is not X" or is empty. However this falls apart a bit when we start working with associated objects in workflows.    For example, I want to enroll a company into my workflow if they have not had a closed won deal in the past 12 months, off the top of my head I might build a filter like this that says bring me in anyone who has had a deal close in the past 12 months and that deal has not been closed won:      However, if a company in my account had a deal 4 months ago that was closed lost, and a day 2 months ago that was closed won, they would still enroll in this workflow because they are still associated with a deal that is not closed won within the past 12 months.    There are two, very messy workarounds for this:  1. Use association labels for "open" deals, or "won"/"lost" deals, to target these deals specifically in the workflow criteria.  2. Just create a list, I can create a list of all companies who have closed won deals in the last 12 months and just set my enrollment criteria to be "company is not on this list".      2 works perfectly to be honest but introduces another asset to be mantained and considered when trying to keep a CRM clean. Using lists as workflow enrolment criteria is unwieldy and will almost always become an unscalable mess in the long run.    Can we just have an associated object filter for "is NOT associated to an object with this criteria" is seems like a huge oversight that has cause some absolute stresses trying to think through the double negatives and filter criteria tbh.    ...read more

It would be really useful if we could create workflows based on meetings, as we do with contacts or deals. To give you an example, I wanted to create a workflow that would change the stage of the deal automatically when a meeting is created with a future date. Even though I found a way to create the workflow, I could not use it as it did not allow me to re-enroll due to using meeting properties. For a lot of businesses, you can have multiple meetings with a customer before selling, so it would only make sense that you can re-enroll data in the workflows. ...read more

Hi team, at this moment when we have a delay until calendar date and the date has already passed, the next action in the workflow is execute as mentioned here However this can cause confusion and make the workflow process not accurate, in my case I have a workflow that send emails, the delays where set to execute until April 29th but the workflow remains on and people was enrolled the 6th of May and the email was sent again causing the customer to reach and manifest their discontent for this action.    It would be useful if, instead of continuing the workflow, we stop the workflow if the date has already passed, just to make sure we're not performing an action that is not supposed to be performed.  ...read more

Building out many workflows for our business and we can't add a Team to a workflow. We have either to add the sales team individually or create a list with them in and reference the list. It would be so much easier if we could add the 'Teams' into a workflow. Settings>Users & Teams>Teams>Sales https://app.hubspot.com/workflows ...read more

I would like the option to manually enrol a ticket from the records page into the workflow. ...read more

I would love a workflow delay action that allows you to release only a certain number of records from it every spcified amount of time. For example if I enrolled 10,000 contacts into a nurture workflow I would love for 500 to move through the workflow every 24 hours (if you could take into account business days on this too that would be excellent). Then every 24 hours 500 records get released to recieve emails, SMS, or tasks.   This would work really well in pairing with other delay actions as well to be able to stagger outreach on a larger scale so that replies never get overwhelming ...read more

Provide additional routing options for the Customer Agent to route to a ticket. This is currently limited to a hand-off only, which requires a user to be assigned to the live chat.   Who it's for: Service Hub users with access to the Customer Agent (currently in beta)   What problem it solves: Not every team has capacity to be available 24/7 for the AI Agent to hand-off the conversation to a live person, being able to create a ticket allows it to flow into existing processes/queues.   submitting on behalf of Patrick O'Keefe, reference ticket #19929723027 for additional details about the limitations. ...read more

I would love to be able to add in the new association labels using a workflow - rather than needing to do this manually. this would enable businesses who have contact A who makes a booking and Contacts B, C, D etc who attend a course or an event flagged as attendees. so a business knows which are valuable contacts.   It would also be helpful to be able to use a workflow to send different communications to clients based on their association tag. ...read more