Great minds think alike

If HubSpot really wants to be a comprehensive CRM and RevOps platform, we need to be able to use all the objects in goals. The current capabilities for creating and tracking goals do not include the ability to set true revenue goals. Payment income doesn't count toward goals at all if it comes through a payment link or a subscription, and there aren't even ways to work around this in workflows.  Plus, revenue goals are tracked based on when a deal is closed, won, not when the payment is received. For any kind of recurring revenue situation, the goals tool is basically useless. ...read more

We would like to request that HubSpot add the ability to display lead scores directly on Lead records in the Leads Pipeline, similar to how deal scores are displayed on Deal cards in the Sales Pipeline.   Justification: Currently, lead scores are stored within Contact properties but are not visible on Lead records in the Leads pipeline. This creates a disconnect when trying to prioritize and work with leads that have been scored based on engagement. As a workaround, we have created a workflow to copy the lead score properties to the Leads object when a lead record is associated with a contact. While this approach ensures that lead scores are available within the lead record, it requires additional setup and manual management. This workaround feels like a missed opportunity for HubSpot to provide a more seamless integration. By adding the ability to display lead scores directly within the Lead cards in the Leads pipeline, teams could more effectively prioritize high-scoring leads and take action quickly based on lead engagement. This feature would improve efficiency in the lead qualification process and align with the existing functionality of deal scores. Benefit: Enhanced lead prioritization. Streamlined workflow for teams handling the leads pipeline. Clearer, more actionable insights directly within the Leads pipeline, without the need for additional workflows or manual management. ...read more

In Settings > Tickets > Pipelines > Automate > Templated automations, it’s possible to enable workflows, but they can’t be renamed or deleted. It’s great that they can be easily turned on, but there is no going back once that is done. I would like a way to delete these (not just turn them off) so that our portal can stay cleaner. If they can’t be deleted, I would at least like the option to rename them so that it’s easier to see at a glance in the Workflows tool what they are & that we aren’t using them. ...read more

Are there any cases where you would like the HubSpot app for iOS to be compatible with Microsoft Intune? If you are running iPhones and iPads under MDM in an Intune environment, I think that for security reasons, copying and pasting text from Office-related apps to the HubSpot app would be restricted from being taken outside the organization. In this case, Intune compatibility would be sufficient, but I would like to hear if there are any similar cases. ...read more

I'm working on a project that started with Production and a Legacy Sandbox. A lot...and I meant almost a full year...of changes went into that Sandbox. We used a 3rd party tool to attempt to move all the customization and configuration to Production. It wasn't great, but we worked through all the issues and misses.   Once Production was validated we created a new Standard Sandbox. Which was very disappointing because a large amount of the customization that has now been built twice (once in Legacy Sandbox and again in Production) did not show up at all in the new Sandbox.   I welcome all HubSpot users to use this thread to ask for a 100% replica of Production when building Standard Sandboxes going forward. Please use this thread to note anything that gets missed when you build your Sandbox and ask HubSpot to account for it.   The new Standard Sandboxes do not bring custom layouts down to the new Sandbox. This is a HUUUGGEEE miss for the project I'm currently on. We have massively configured Team layouts for Deals and so many Custom Objects.    While I'm pointing out things that are missing:   Teams Also the rules for which Teams can update certain properties were removed because there are no Teams? Now I have to go through approval properties with a fine tooth comb or risk overwriting them in Production when I deploy back? This has yet to be determined. Permission Sets Notification Presets In this particular custom solution and configuration, we relied on these items and their capabilities to provide a solution to the client. To have them ignored and having to spend time rebuilding them for a 3rd time is not going to be a fun conversation to have with the client. ...read more

We use Marketing Events synced from Zoom, and are building out an "event afterglow" process to include follow-up emails to participants. Currently, we have to create or clone a segment/list for every single marketing event/webinar that we have in order to pull participating contacts. We’d like workflows to be able to automatically create segments/lists when a new Marketing Event is created, e.g., an active segment named Webinar – {{Event name}} – Registered. We don’t necessarily need the workflow to set filters, although it would be best case scenario to have it dynamically filter the associated event; at the very least, we just need it to create the empty segment/list, so we can then configure filters manually. ...read more

Summary PLEASE enable your AI Customer Agents to be directly deployed to "Forms" as a supported channel, allowing the AI to immediately process, analyze, and reply to form submissions via email without complex inbox workarounds. There are millions of "Contact Us" forms out there for Hubspot AI Agents to manage, your customers need this! The Problem Currently, AI Customer Agents can only be deployed to conversation-based channels: Facebook, WhatsApp, Calling, Live Chat, and connected Email inboxes. However, a massive volume of support and sales inquiries originate from standard HubSpot Forms (e.g., "Contact Us" pages). Users attempting to route these form submissions to an AI Agent via Workflows which then replies by email is currently not possible. As confirmed by Hubspot Support, while a workflow can assign a Ticket created by a form to an AI Agent, the Agent cannot actively reply because it lacks a "Form Channel" deployment. The result is a "dead end" ticket: the assignment happens, but the AI remains silent, and the customer receives no response. 😞 The Current Workaround & Its Limitations Support currently recommends connecting the Form directly to the Conversations Inbox. However, this creates friction for enterprise users who: Use complex Workflows to route forms based on logic (e.g., If Region = Other, assign to AI). Do not want every form submission dumping into a shared inbox. Want the AI to act as a specific "step" in a larger automation sequence. The Proposed Solution Add "Forms" to Agent Channels: Update the Customer Agent setup (Service > Customer Agent) to include "Forms" as a deployable channel, alongside Chat and Email. Workflow Action - "Handover to AI Agent": In Workflows, introduce a specific action: "Process with Customer Agent." Input: The Agent reads the form submission data (fields) as the "User Prompt." Output: The Agent generates an email reply based on its knowledge base and sends it via the connected portal email/Help Desk address. Context Awareness: The Agent should be able to read standard form fields (Message, Problem Description, Product Interest) to formulate a contextual reply immediately, using its knowledge base (indexed web pages, landing pages, custom answers, etc) for complete context. Use Case Example Trigger: A prospect fills out a "Contact Us" form on a Saturday asking about pricing for a specific region. Workflow: The prospect is marked as "APAC" due to their IP address.  Action: The Workflow assigns the ticket to the "Parrot Analytics AI Agent." In addition, the prospect's Hubspot owner is set to be the APAC sales leader and a reminder is set for the APAC sales leader to check in on the prospect 24h later. Result: The AI Agent instantly analyzes the query, checks the knowledge base for pricing, and sends a helpful, personalized email reply within seconds- without a human agent ever touching the ticket. The optional human-in-the-loop (assignment to APAC sales leader) ensures we have a QA step in there to monitor AI agent quality in the early stages of the agentic AI roll-out.  Business Value True 24/7 "Contact Us" Coverage: Drastically reduces "Speed to Lead" and "Time to Resolution" for form-based inquiries. Bridge the Gap: Closes the functional disconnect between Marketing Hub (Forms/Automation) and Service Hub (AI Agents). Reduction of Manual Triage: Eliminates the need for humans to manually read and route form submissions that simple AI could resolve instantly. ...read more

At the moment, the export permission is universal, meaning that if a user has an export permission, they can export literally everything out of Hubspot.   With rampant data breach via social engineering, this poses a great risk for organizations with a large amount of personal data stored in HubSpot.   Ideally, we should be able to choose what kind of data can be exported out of HubSpot. For example, only reporting or only companies but not deals and contacts, etc. If we can set this up per object, that would be perfect. ...read more

Let worflows reference each other for example allowing delays to trigger after a task in another worflow has been completed or trigger an action if the other workflow has been completed ...read more