Les grands esprits se rencontrent

Journey reports are challenging when trying to dial in on the time it takes to complete the steps in a journey. Current Restrictions/Limitations Only one way to control the time range of the journey (sure we can do a static range or rolling time range), it is still only one time setting. Other analytics tools we use have additional levels of time parameters, the lack of this in Hubspot journeys limits the value we get out of the reports. Lacking stat of median time between steps; we only see the average time between steps   Inability to refine time parameters on each step of the journey.   Control that the action was done the 1st time since the previous step (and then stop recording the event on that report for that contact)   ----- Further details We want to look at anyone who would enters the journey up to 30 days ago. THEN, we want to know, of those contacts, who completed the steps in the journey within 10 days of entering the journey. If a contact 'qualified' to be in the journey but dropped off before completing within 10 days, that's an interesting stat along with the 'success' rate of those that did complete within the 10 days. IF we limit the journey report date range to only include 10 days, we are NOT capturing the entire cohort of interest (like anyone who was sent the email in the last 30 days). IF we try to use the contact filter or apply a list to capture the cohort for the 30-day range, this doesn't work either. The reason being the date range on the report is set to 10 days because we want to know who completed the journey within 10 days, we will still only 'see' the contacts that did the first step in that 10-day range (even though we want to look at a cohort of contacts that did the first step in the last 30 days). ------ Median is good to see in addition to Average. OR at least allow us to decide which we prefer to see for each step. ----- We should be able to refine the parameters between each step as well and control how those actions are counted. (refinements) IF we are using a custom event or a page view, a person may do those events multiple times while in the time range of the journey. It appears that the most recent timestamp of firing those actions/event, overrides the first time after the prior journey step the contact may have done the event. This creates a challenge of knowing the time of completion between steps as the first time after the previous step is no longer recorded if the contact comes back and does the step again and again. Ex) Instead of opening an email, clicking a link, logging into our app showing seconds (confirming our engagement email is working); we are seeing opened an email, clicked a link and then the time to log into our app being hours or days later. When we dig into the contact record, we see this is due to the contact firing the event multiple times after having done the action in the previous step of the journey. We care to only see the time to complete as a reflection of the 'the first time after the previous step'. ... Afficher plus

Description: The current functionality within HubSpot allows any user to be mentioned in tickets and notes regardless of their availability. This feature request aims to introduce an enhancement that addresses the scenario where a user is mentioned (e.g., using the @ function) while they are on extended leave, such as a vacation, and thus unavailable to respond or take action. The lack of visibility into a user's availability before mentioning them can lead to inefficiencies and delayed responses in handling customer queries and internal communications. Proposed Solution: Out of Office Indicator: Introduce an "Out of Office" status that users can enable when they are not available. This status should be visible to others when they attempt to mention the user in a ticket or note. Mentioning Mechanism Enhancement: When an attempt is made to mention a user who has marked themselves as "Out of Office," the system should display a prompt or warning indicating the user's unavailability. This will inform the mentioning party that the user is currently out of office and may not respond promptly. Optional Mention Disablement: Provide an option to disable mentioning for users who are marked as "Out of Office," either automatically based on the status or through a manual setting that the unavailable user can enable before going on leave. Visibility and Accessibility: Ensure that the "Out of Office" status and any warnings or prompts related to it are easily visible and understandable within the user interface to prevent any confusion or oversight. Use Case: This feature is particularly useful in scenarios where team members are collaborating on tickets and notes within HubSpot. For example, if a user needs to mention a colleague for input or action on a ticket but the colleague is on a two-week vacation, the current system does not provide any indication of the colleague's unavailability. The proposed enhancement would alert the user at the point of mention, allowing them to make an informed decision about how to proceed. Benefits: Improved Communication Efficiency: By providing clear visibility into a user's availability, team members can make more informed decisions about whom to mention and expect a response from. Reduced Response Delays: Preventing mentions of unavailable users can help redirect queries and tasks to active team members, reducing wait times and improving customer service. Enhanced User Experience: The feature adds a layer of intuitiveness and consideration to the user interface, acknowledging the dynamics of team availability and the need for flexibility in communications. ... Afficher plus

Hi You have a new option of Tags on deals, its great and something we have been waiting for a while. We are using it, but there is a limit of 10 tags only for the whole system. Are you planning to increase it soon? That would be awesome, as we ca only use it if we can use it to the full extend, please consider increasing the amount of Tags allowed. Thanks Sam ... Afficher plus

HubSpot auto creates a contact for anyone that emails in - or is cc'd into a reply in conversations. For some customers who manage through support, this will mean a large number of contacts can enter the database. The only way to prevent this at the moment is by setting filtering rules, as all filtered emails do not create contacts. There is a use case from a customer in this post [Hyperlink removed by moderator as it linked to an archived Community post with duplicate information]   This is a request to build a "Create contact" rule giving us the option to disable automtically creating contacts for people we communicate with in Conversations.   ... Afficher plus

I'm in the process of setting up calculated properties to use the new "time between" feature in reporting, and realized that, in the 'time between' calculations for properties, I'd like to have access to the option 'today,' which would be a dynamic date set as the value of today's date. That would allow me to track dynamically how long has it been since a deal has been created ('today' minus 'create date' = how far along we are in the sales cycle up till now).  ... Afficher plus

    linked to these Forume messages, but no duplictates in the IDEA Forum:    I need to be able to respond to instagram messages via my Hubspot account.   Can you please look into utilizing the FB Business Manager API, to also integrate the Instagram Chat Messages.    I would like to be able to respond to those messages, in the same way, as I do with Facebook Messenger through HubSpot.    Hope this is being considered, and expanding the current beta chat scope.      FB Chat Beta: https://community.hubspot.com/t5/HubSpot-Ideas/Integrate-Facebook-Messenger-with-Conversations/idi-p/204375   Instgram Chat from Acedemy:  https://community.hubspot.com/t5/Academy-Learning-Center-Support/Answering-instagram-messages/m-p/273318 ... Afficher plus

We'd like to be able to disable a form after a certain number of submissions.  ... Afficher plus

Hey there!   For us to be able to create forms that use Deal Properties would be amazing.   Is that something easily feasible?   Thank you. ... Afficher plus