Gute Ideen sollten geteilt werden

If I want a certain property to be visible in the card view in 1 pipeline but not in the other, then I cannot. For example, in our customer service pipeline, the ticket descriptions are long and so they don't want them to show up in the card view. In my operations pipeline, it is crucial that I be able to distinguish between different kinds of cards quickly without having to click on each on, scroll down, etc. Fine if I have 10 tickets, but what if I have 50? I changed the property view in 1 pipeline and it created a mess in the CS pipeline.    Please work these kinds of basic UX features into your feature development when develop in the first place instead of retroactively. So many aspects of the HubSpot experience seem to be poorly conceptualized from the user perspective.   Thank you!  ... Mehr anzeigen

We have a field in our tickets for "Expected Launch Date"  In order to launch (or complete) said ticket, there are various tasks to be completed. Each task needs to be done within a set # of days prior to the set Expected Launch Date.   Seems like a logical functionality within automations to be able to create a task within a ticket with the due date being X days prior to date on ticket.  ... Mehr anzeigen

Hi   Our current Ticket ID number series are 9 digits long, if at any point we have to relay on this number to identify an issue the chanses it will be missread is significant.   Would be great if we could reset it to start from 1 again or if we could create our own with ticket ID:s relating to products or projects based on letter and/or number combinations.   Best Regards Björn A ... Mehr anzeigen

My team spends all their time in Tickets, using the List view. However, every day when we log in Tickets show the Board view.   Please create a user level preference setting so users can select whether they want Tickets to start in List view or Board view ... Mehr anzeigen

It would be very useful if you could connect the customer portal (ticket system) to the knowledge base (if it is set to private), so when users registrer for the customer portal, they would also automatically get access to the knowledge base. As far as I can gather now, they are two seperate entities, and our customers would need to register twice to access both.  ... Mehr anzeigen

Hey HubSpot We work with a number of organisations that are migrating to the Service Hub from other software purely for HubSpot's centralised automation and suite of products.  A recurring pain point is the lack of functionality to perform actions in their workflows based on ticket data-points/fields when working with contact-based workflows It seems every other object is supported, but Tickets aren't. This would solve so many non-scaleable complex workarounds currently in place. ... Mehr anzeigen

HubSpot needs to implement a Collapsible Tree element to all areas that have a history.  For instance, in a ticket, a contact Card, etc.  If I am looking for a conversation that took place four months ago, as things are now I have to scroll down forever, waiting for HubSpot to pull up the older conversations so I can scroll past them.    It would be very useful if I could just collapse May, April, March, February, etc to get to January and scroll through those.  Expanding that idea also to years would be great.    ... Mehr anzeigen

In the Professional Service Hub, we are wanting to have "pretty" email templates to send as auto-confirmation that a Ticket was recevied. I understand these templates are the bread & butter of what make HubSpot's Marketing platform great, but Service would like to be great too. I suggest letting the Professional Service Hub have a limited number of rich email templates without having to add the Marketing Professional Hub. For example, when I submit a ticket with HubSpot, I get the below automated "thanks" response. We want to be able to do something similar with only using the Professional Service Hub.      ... Mehr anzeigen

Would be incredibly useful to have a NEXT TICKET button next to the < TICKETS button that returns you to the ticket list. It's very slow and cumbersome to go back to the list just to get to the next ticket. Just let me click to the next one in the queue.   ... Mehr anzeigen