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

Ticket properties" includes "Create date."  The option to include the time would be useful as well: "Create date / time".   ...その他を表示

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

My service teams have a few monthly tasks that we track as tickets. I currently use Zapier to generate these tickets on a schedule but would like to do this natively in HubSpot. ...その他を表示

Script to embed Knowledge Base and Tickets in our website as a pop-up modal. User can click on 'Help' button on any page (just like we can do in HubSpot). Can also incorporate Conversations/Messages and Calling.   Helps to provide self-service support, contextual support and reduce ticket volume. ...その他を表示

Posting on behalf of a customer -    Currently, we only provide the ability to create 'Center on a date' or 'Center on a date property' contact-based workflows. It would be amazing if we offer the same options for ticket-based workflows as well.    Use case: Customer is looking to create a workflow that is revolving around 'Next activity date' on tickets to send automated emails, create tasks, etc.    Thanks for your consideration team!  ...その他を表示

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

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

Currently if you merge two tickets, they are combined into a new ticket with a new ticket ID.    Since we often communicate the ticket ID to our customers for reference, it would be much preferred if one of the original ticket IDs were kept, instead of creating a third new one. ...その他を表示

When looking at tickets in board view it's only possible to sort based on one property, I would like to be able to sort on multiple properties. Tickets in each stage should be possible to sort based on for example priority first and created date second (or any other properties).   Along with filters this would allow for a clear and complete overview of which tickets should be handled by whom and in what order. Work instuctions could then be as simple as working from left to right (stages) and top to bottom, rather than jumping between filters.     ...その他を表示