Great minds think alike

Currently in the support hub you can toggle for everyone having access to all company tickets or not. It would be ideal if we could allow specifc contacts access to all of their company tickets instead of allowing it for everyone or no one. ...read more

From the index view on any object type, we can check boxes to select multiple records and a Bulk Actions menu appears:   Please add the ability to "Bulk Associate" records to this menu.   This should honor the association settings and limits defined on the object settings. For example, if Ticket associations are not enabled, the option to associate a Ticket record won't appear.    Or if there is a finite number of maximum associated records, it would prevent the user from exceeding it via the Bulk Associate action.   It would be even better to set Association Labels in this same manner or remove associations entirely.     ...read more

I was very excited to see the new Help Desk feature then I got into using it. The very first thing I tried to led to, what is in my opinion, a major issue related to the default views and users with paid service seats. The current default views are setup that anyone with a paid service seat has the ability to view "All Open". This view is for ALL open tickets in Service Hub. The permissions that manage the views and access in pipelines/teams/user permissions do not extend to the Help Desk feature.    We have multiple teams, parent and children, each with indivdiual user permissions that limit their access to only tickets related to their teams. While this feature would be great for letting them see all the tickets related to their teams in one view plus adding workflow to channel tickets to the best agent, we do not want them to see all tickets. This negates our ability to utilize the feature at all.  ...read more

It is very much needed to have the possibility to edit the ticket owner in the Helpdesk in bulk.   For example if an employee leaves the company and open tickets should be handed over the another colleague. Or if open unassigned tickets need to be divided between colleagues. Now we have too many clicks to change the owner in bulk. ...read more

Since everyone is looking to move from conversation inbox to Help Desk, I think it would be better if you add the button Compose to send emails directly outside without creating a ticket first. ...read more

Currently no mails from a ticket are shown in the activity feed of a company when the company has been associated after the ticket has been created. This is not a good UX since I always need to open the different tickets to see what is going on. As a user I expect the mails to show in the company's activity feed once I associated it to the ticket. ...read more

After briefly playing around with the open beta Help Desk funcationality, I wanted to submit an idea for a use case that neither the current Inbox nor the new Help Desk seem to work with.   Currently all of our internal communication that happens on a ticket happens via Notes on the ticket. These notes are only accessible when opening the ticket and going through the activity, or specifically the notes.   In the old Inbox, you can also add Comments, which our team also do. However, we have noticed that Comments and Notes seem to fulfil a similar purpose, but are at odds with one another. If I leave a comment on a conversation that is associated to a ticket, then I am not able to see that comment when viewing the ticket. Similarly, if I leave a note on the ticket, I am not able to see that note on the Inbox conversation.   I had hoped that the Help Desk might do something to unify this experience, as it seems to be being pushed as a way to manage the support process all in one place. However, this still seems to be an issue. I can't see Help Desk comments on a ticket, nor Ticket notes on a help desk conversation.   My idea to unify this would be to do one of two things: 1. Show Ticket Notes on Inbox/Help Desk Conversations, and Inbox/Help Desk Comments on Ticket Activity When a note is associated to a ticket, and that ticket is associated to a conversation, also show that note in the conversation at the same timestamp the note was created at. Note-comments (comments made on the ticket note) should also show in the conversation-comments, either as their own entries or like they currently do, under the note. Similarly, when a comment is made on a conversation, and a ticket is associated to that conversation, show that comment on the ticket activity as it's own entry at the timestamp it was made at. or 2. Unify Ticket Notes and Inbox/Help Desk Comments Instead of showing a note on a conversation, and a comment on a ticket, get rid of one (e.g. keep notes, get rid of comments) and have a single source that shows on all associated records. The UI look and feel could be the same, but now when I leave a "comment" on a conversation, that is actually a note that is associated to records that conversation is associated to. I can interact with that note on the conversation, or on the ticket, or the contact, or anything, and that interaction will sync across all records.   Who (what type of role or team) is the feature for? This would be aimed at the support teams who work closely with Tickets and the Inbox/Help Desk.   What is their goal? Communicate on tickets and have those communications be consistent and visible across HubSpot   What value will this add? This will allow the support team to stay in one place. Whether the Help Desk or the Ticket, the person will be able to see all commincations without needing to search around. This will also make Comments more visible, as currently the only way to see a comment on a conversation is to navigate to the Inbox/Help Desk and scroll to when the comment was made.   Are there examples of other places or products who have this feature? The notes on all HubSpot records work great for their purpose. They just fall short specifically on conversations, which is an issue when conversations and tickets are so closely linked together. ...read more

Currently there's no easy way to see all the tickets connected to a contact from the ticket view in help desk. This would be helpful in:    1) identifying related/past issues 2) identifying duplicates created from new threads ...read more

With the recent expansion of associations in HubSpot (same object association, many-to-one associations, association labels, etc) it would be great if we could allow for a set association with an association label when creating an object.   This would be done via customising the "Create a record" form, under "Associations". Instead of just one association per object type, allow for multiple per object association label.   Example: Edit the "Create a deal" form. Under associations, you see two entries for the Company association. One is Primary company as usual, but then underneath you have Partner company, Partner being an association label that has been set up, either optional or mandatory.   Now when creating a deal, I must select the Primary company, but I also can/must select a Partner company.   This feature would be great for teams/users who input data into HubSpot. By allowing the option to be set to mandatory, it also improves data robustness.    Currently, we have no way to ensure that association labels are actually used. At our business we have internal processes that should be followed, but people forget to follow the process. This can lead to records that don't have all the correct information, which then leads to manually having to check records are correct.   Example image:   ...read more