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

If a deal or ticket is already associated with a company, pull the contacts associated with that company into the Associate Contacts screen, allowing the user to select from that list or add other contacts using the search bar. This would save time and hassle by eliminating the need to search your entire contacts list by exact name/email for the contacts associated with a company that you have already associated with the deal or ticket but still allow flexibility for the user to choose the specific contact(s) that should be associated with that particular deal. ...その他を表示

Pourrie-vous développer la fonctionnalité de bloquer les droits de suppression de tâches à certains utilisateurs.  ...その他を表示

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

Having some setting to add HubSpot attachments to associated Jira tasks would save so much time and confusion. Does anyone know a workaround to this, either native or using third-party tools?  ...その他を表示

Hi! I was curious if you could add a feature that provides insights on who accesses the Customer Portal. We provided access to some clients, and we were wondering if we could have access to stats such as the last time they signed in, recent activity, etc.   Thanks! ...その他を表示

We have many customer use cases with Service Hub where we would like to be able to send automated emails, linked to a ticket, based on some criteria.  A few examples : - update / additional information on a ticket when moving to a certain stage in the pipeline - sending a recap of ticket information, especially when tickets are used for managing processes (onboarding, training, etc.) rather than "basic" customer service - reminder of an open / unsolved ticket (to the customer)   2 options are available now : - the basic "Ticket open" and "Ticket closed" automated emails, available with Service Pro - susbcribing an additional Marketing Pro, to be able to send additional emails. But in that case : the email may not be linked to the ticket, and the replies will not be included in the ticket. This is logic for a marketing email, but not for ticket management... - use sequences, that can be automated only with Service Enterprise, and are a bit odd for one-off emails   It looks like an important blind spot of the Service Hub (compared to other service tools), and a set of features where Hubspot is particularly strong and could get an edge on the market (workflows and automation features). Moreover, having to subscribe Marketing Pro is a huge ask and cost for customers that would be interested only in Service, or Sales+Service, that does not make much sense.   The solution could be to create a new "service automated" email type, available only on Service Pro and above, that would be triggered by a Ticket workflow, and whose answers would be included in the ticket. ...その他を表示

Veo imprescindible para un buen servicio de atención al cliente poder mandar un correo OOO. El problema de Hubspot, es que no tiene la propiedad de hora por lo que, los tickets que se inscriben en un workflow de OOO no se basan en horario activo de oficina o no.   Gracias. ...その他を表示

We are implementing Service Hub.  I started on the process of creating a workflow to fire off an email when a service ticket is submitted.  Also, we had planned on using email templates for responding to common issues, etc.  When I opened the Email Template builder, I found there was no Ticket properties available.     I'm assuming this is something that's planned/in progress already?  I guess I would expect all of your Service Hub users to require the email template functionality.  I actually submitted Support Ticket and was told to submit an Idea.  Seems like this is more of a major function than a simple idea.   ...その他を表示

If possible, we needed that the tickets time for closure were customizable as the date of closure. With the new metrics system of yours, when we close a ticket from yesterday with the date time of today, they turn out to be negative in the reports due that change. ...その他を表示