クリエイティブな才能を開花させよう

We propose adding a configurable setting within the Customer Agent that allows users to control the automatic transfer behavior when a customer requests to speak with a human agent (e.g., by saying "transfer" or "حولني"). Current Limitation: The system currently initiates an immediate transfer upon such requests without evaluating if it's necessary. There is no built-in setting to disable or customize this behavior. This leads to premature transfers that could have been resolved by the Customer Agent, reducing its efficiency and increasing load on support teams. Proposed Benefits: Reduces unnecessary escalations to human agents. Improves customer experience by allowing the agent to attempt resolution first. Optimizes support team workload by filtering only critical cases for transfer. Suggested Solution: Add a toggle or rule-based setting to: Enable or disable auto-transfer on specific trigger phrases. Define pre-transfer behavior (e.g., ask a clarifying question, attempt to resolve the issue, or confirm the intent before transferring). ...その他を表示

Lets say you build a dev site and have a 100 pages. By default it uses a domain like hssites-xxxx.com. Once you change your primary domain the page URL's update but the files used on each page still use the old domain.   So you go and update the default file URL domain to your new primary domain. You assume this updates on all pages and your sitemap.xml... because you want it to be the default.  But this only works for any future updates you make and publish. All of the pages you created using the temporary domain are not updated. So in order to fix this, you need to open all 100 pages and then republish them. "ain't nobody got time for that" : ) Could you please add a way to click a checkbox that says "Update all pages and sitemap.xml with this new file domain".  Thank you. ...その他を表示

We have a website where we group 22 language variants under the en-US primary page. But there are technically multiple primary languages. So having the ability to make subgroups of languages would help tap into the fallback language options. The primary language for a group becomes the fallback for all languages. If you land on a page missing that language then it will go to the primary. But we may have several languages that are associated and we'd like to select a primary for that group. For example: fr-FR (primary for this set of language regions) fr-BE fr-CH So if fr-CH is missing, Id like it to fallback to fr-FR but still have it in the larger associated group of language page variants. ...その他を表示

With the new form editor it's currently not possible to set up different subscription types. In the old form editor the Data protection and consent field allowed to set up different subscription types including the option to mark them mandatory or optional.  This feature is highly needed in the new editor as well - especially for clients with a starter license as they can't use any workflows to mitigate this problem.  ...その他を表示

We use Hubspot for a multitude of channels and thus my role and use of the system in broker relationships and acquisitions is very different than investor relations. We both use worflows but today we can not build custom reports centered around specific workflows, just workflows as a whole, which renders the data entirely useless given the scope and work are completely different. We would like to create a custom report (and further a dashboard) full of custom reports tracking emails sent, opened and people in stages of the specific workflow vs all workflows.  ...その他を表示

With the popularity (and usefulness) of X continuing to decline, and more and more people transitioning their accounts over to either BlueSky or Threads, it would be useful to have the option to integrate BlueSky accounts into HubSpot's social media dashboard. ...その他を表示

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.    ...その他を表示

Currently in the text snippets and email templates tool, it's only possible to use tokens from standard objects such as contact, company and deals. It cannot pull any custom object fields which is a huge bummer.   It'd be really useful if HubSpot can implement this feature for enterprise accounts who have data spread out across multiple standard and custom objects. This is possible in marketing emails, so implementing this in custom objects just makes sense.   Please upvote this idea if you feel the same or have had similar painpoints! Thank you. ...その他を表示

Hola, comunidad.   Espero que estéis bien.   Escribo esta idea en la comunidad por uno de mis clientes. La funcionalidad sería que, al crear un objeto nuevo mediante un formulario de creación (de ticket, empresa, contacto, etc.) se rellenen automáticamente las propiedades de ese mismo objeto con propiedades del objeto asociado.   Un ejemplo: creo un ticket y tengo en el formulario de creación propiedades que ya están rellenadas en el contacto asociado con este ticket. Sin necesidad de crear un workflow adicional, me interesaría que se copiase el valor de la propiedad "correo" del contacto en la propiedad de ticket "correo del contacto".   Ojalá podamos ver una funcionalidad así pronto. Por favor, no dudéis en votar para darle más visibilidad.   Mélani HubSpot Support   ------   Hello, community.   I hope you are well.   I am writing this idea in the community on behalf of a customer.  The functionality would be that, when creating a new object through a creation form (ticket, company, contact, etc.) the properties of that same object are automatically filled with properties of the associated object.   An example: I create a ticket and I have in the creation form properties that are already filled in the contact associated with this ticket. Without the need to create an additional workflow, I would be interested in copying the value of the contact's “email” property to the ticket property “contact's email”.   Hopefully we can see such a functionality soon. Please feel free to vote to give it more visibility.   Mélani HubSpot Support Agent ...その他を表示