Great minds think alike

Its incredibly painful that lifecycle stages cannot move backwards, if its something users leverage to assess an "actual" lifecycle stage. A contact/company can move through the stages, and then go back to stage (1) as its being contacted again by a new seller. Not being able to automate this workflow, is a huge pain for our team, as it requires the sellers to do this manual, with lots of errors down the line.. ...read more

Please, of the thousand different ways that we can filter companies and contacts, let us filter by call-outcome! Simple request, should take like five seconds to add this. Seems like a total no-brainer.   Thank you! Alex ...read more

Hi! As many of you probably know there is a beta since last month for HubSpot with a new data panel that gives you access to more CRM data in certain actions in your workflows. For example all the information from the most recently updated deal associated to a company.   This new feature will open many new opportunities and I only just started exploring, but I think it can also be of great addition for triggering a workflow. What if you can refine the trigger in your company workflow to only work when the most recently updated deal is in a certain deal stage? This will not only open many new opportunities but will also reduce the amount of workflows needed in many situations.   Upvotes are appreciated! 😄     ...read more

It would be great if approval requests could be sent to other notification systems e.g., Slack and Microsoft Teams. ...read more

I activated a workflow without selecting the existing deals and now need to enroll the previously existing deals in the workflow. There should be an option or workaround to manually enroll the records in bulk   ...read more

I have some automated emails from our application that create tickets in hubspot. Unfortunately, the ticket comes from a no-reply email so that hubspot contact cannot be used to assign the ticket. The body and subject are also not useful as they do not have any identifying characteristics. The only identifier that can be used to distinguish between different companies we have as clients is the sent-to email address. Such as: company1@mycompany.ca company2@mycompany.ca  If there were a way to reference this when building workflows to automate who the ticket is assigned to, that would be very helpful! I know that other ticketing systems I've used in the past had this so I was surprised it was not available here.   Looking forward to hearing if others are having similar issues! Who (what type of role or team) is the feature for? - Support team What is their goal? - Auto assign tickets correctly when sent from emails from no-reply@mycompany.ca What value will this add? - Having to manually assign tickets is very tedious and time-consuming. It makes us less productive and slow at responding to these tickets. Are there examples of other places or products who have this feature? - Zendesk Screenshots, pictures, drawings, process diagrams, are helpful. - N/A ...read more

View whether Workflow has goals and their performance against those goals in a column value on the new beta index page.    This would be useful as we want to ensure every worflow uses a goal. would also be nice to see which workflows are hgih performing / not working.    ...read more

There are other smaller CRMs that have built in texting and SMS automation. HubSpot already offers built-in calling, why not also have texting and allow us to add text messages to our workflows?   Texting has a much higher open/engagement rate than email, so it would make sense from a conversion perspective for both sales and marketing to have this. ...read more

Today, hubspot can be used as an email to ticket submission system.  For example: a system can send a group email that creates a ticket for a support team in hubspot.  leads can be sent from one system to hubspot in an email a customer may send an email to a company's support shared mailbox that creates a ticket in hubspot support portal for customer to assign. At the moment, hubspot allows workflows to automate the flow of tickets created in this format, but your support team regularly points your customers to use other tools like Zapier to complete this function (when some of your competitor CRMs offer this natively.).  It would be great to build in the ability to parse email information for incoming emails that create tickets or other data (i.e. parse information from a subject line).     Examples include: If an email to ticket is sent to HS ticket is created with the subject line: "New support request from customeremail@domain.com" I as an admin might be interested in parsing the email from the subject line and storing it into a property within the ticket for ease of reporting / tracking. If an email to ticket is sent to HS and a ticket is created with an email body that contains multiple information in a formatted manner such as the format below, an HS admin may be interested in parsing this information to populate ticket properties that can be used in later automations (i.e. automatic replies, automatic ticket assignments based on which user is assigned an account, etc.).  Email Body: Customer Name: TestCo; Customer Email: admin@testco.com; CSM assigned to account: CSM1@hs-customer.com; Link to ticket in external system: www.link.com; Here are some sample support tickets created by some of your customers requesting this functionality that didn't end up turning into ideas, although they should have:   https://community.hubspot.com/t5/APIs-Integrations/Parsing-Email-Body-Workflow/td-p/740138 https://community.hubspot.com/t5/CRM/Extracting-Contact-Details-from-Email-Body/m-p/397679 https://community.hubspot.com/t5/CRM/Parsing-email-content-into-crm/m-p/300730 ...read more