# Ticket Templates **URL:** \ **Category:** HubSpot Ideas\ **Tags:** help-desk\ **Created:** [January 16, 2019, 1:56pm UTC](https://community.hubspot.com/t/ticket-templates/12340 "2019-01-16T13:56:29Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![MKruseck87](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mkruseck87/32/86357_2.png) [@MKruseck87](https://community.hubspot.com/u/MKruseck87)\ **Post date:** [January 16, 2019, 1:56pm UTC](https://community.hubspot.com/t/ticket-templates/12340/1 "2019-01-16T13:56:29Z")
It would be awesome to have different properties for different types of tickets, and even further customization to be able to have different tickets for different pipelines. That way each team/client gets its own ticket types. ---
**Author:** ![PeterC](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/peterc/32/20935_2.png) [@PeterC](https://community.hubspot.com/u/PeterC)\ **Post date:** [January 30, 2019, 1:36am UTC](https://community.hubspot.com/t/ticket-templates/12340/2 "2019-01-30T01:36:32Z")
I agree. Can’t believe this only has two upvotes, and one of them is mine! When trying to set up something like “sales” and “support” tickets, the two ticket types (pipelines) need different property sets - but you can’t currently achieve this. So you end up “dumbing down” the ticket properties to the point where both teams can use them - only to find half the information you need is now not being collected! Frustrating. ---
**Author:** ![KarolinaOlczak](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karolinaolczak/32/22074_2.png) [@KarolinaOlczak](https://community.hubspot.com/u/KarolinaOlczak)\ **Post date:** [March 4, 2019, 7:11pm UTC](https://community.hubspot.com/t/ticket-templates/12340/3 "2019-03-04T19:11:35Z")
I would love to be able to customise my tickets as well a bit. In my case, I need to be able to access easily Background URL from the ticket - this is one of our custom contact properties. To solve customer’s issue we need to be able to move quickly to his account within our application - at this moment we have to manually copy his email address and search it or go to the contact page and access it from there. I’m dreaming about the possibility to simply click this from the ticket’s right side, where I can see contact information 🙂 ---
**Author:** ![PeterC](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/peterc/32/20935_2.png) [@PeterC](https://community.hubspot.com/u/PeterC)\ **Post date:** [March 6, 2019, 9:19pm UTC](https://community.hubspot.com/t/ticket-templates/12340/4 "2019-03-06T21:19:48Z")
Great idea @KarolinaOlczak! Hope you don’t mind me copying it ![16x16_smiley-tongue.png.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/9/e/9ee85ed32f43bd1e26f190560e13ba27d75117cd.png) (I’m giving you an upvote as payment.) You can do it with a Workflow - but only if the **Contact** related to the ticket is associated with a Company. (The enrolment options are different for Contact-based workflows… Why HubSpot?!) 1. Create a “URL” custom property on your Tickets (if you haven’t already). I used a single-line text property. When the text contains a url, HubSpot presents an icon to open the link in a new browser tab. It works great. 2. Create a **Company** based Workflow with the enrolment trigger set to check the **Ticket** property: “URL” = Unknown. 3. Use an If/Then branch to check the “URL” on the Company **Is** **known** (this is just error-checking because some of our companies don’t yet have the URL data filled in.). 4. If “URL” on the Company **Is** **known** , use a **Copy Property** action to copy the **Company’s** “URL” to the **Ticket’s** “URL” You may need to edit the default properties on your tickets to show the “URL” link. ---
**Author:** ![KarolinaOlczak](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karolinaolczak/32/22074_2.png) [@KarolinaOlczak](https://community.hubspot.com/u/KarolinaOlczak)\ **Post date:** [March 7, 2019, 11:22am UTC](https://community.hubspot.com/t/ticket-templates/12340/5 "2019-03-07T11:22:51Z")
@PeterC Thanks for the suggestions 🙂 I’m trying to set it up, although due to the specifics of our company, the backend URL may differ between company and contact. Unfortunately, as you have mentioned, the contact based workflows are different and the company based workflow doesn’t allow me to choose my custom contact property. I tried as well with ticket-based workflow - but then my end result is to copy the backend URL from ticket to the contact, so the other way around than I actually need it. ---
**Author:** ![macbleser](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/macbleser/32/3365_2.png) [@macbleser](https://community.hubspot.com/u/macbleser)\ **Post date:** [November 7, 2019, 12:58pm UTC](https://community.hubspot.com/t/ticket-templates/12340/6 "2019-11-07T12:58:24Z")
Came here in search of the exact same feature. We really need the ability to customize the default ticket properties for each ticket pipeline. This would be hugely beneficial when both creating and viewing tickets. This feature would be even more powerful in tandem with this other feature request regarding the ability to set default email templates for each ticket pipeline: [https://community.hubspot.com/t5/HubSpot-Ideas/Default-Email-Templates-per-Inbox/idc-p/300884](https://community.hubspot.com/t5/HubSpot-Ideas/Default-Email-Templates-per-Inbox/idc-p/300884) ---
**Author:** ![User22](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/user22/32/99949_2.png) [@User22](https://community.hubspot.com/u/User22)\ **Post date:** [December 2, 2020, 3:30pm UTC](https://community.hubspot.com/t/ticket-templates/12340/7 "2020-12-02T15:30:44Z")
My vote is submitted as well for this. The ticket can quickly become ‘irrelevant’ when there is too much to choose from when each pipeline has a unique workflow/user need. ---
**Author:** ![mikloso](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mikloso/32/52512_2.png) [@mikloso](https://community.hubspot.com/u/mikloso)\ **Post date:** [December 2, 2020, 10:54pm UTC](https://community.hubspot.com/t/ticket-templates/12340/8 "2020-12-02T22:54:27Z")
Agreed! ---
**Author:** ![Ashleymccu](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/ashleymccu/32/95715_2.png) [@Ashleymccu](https://community.hubspot.com/u/Ashleymccu)\ **Post date:** [January 6, 2021, 5:59pm UTC](https://community.hubspot.com/t/ticket-templates/12340/9 "2021-01-06T17:59:31Z")
Agreed! And even further ability to add prepopulated fields in the ticket description ---
**Author:** ![ElBr](https://avatars.discourse-cdn.com/v4/letter/e/53a042/32.png) [@ElBr](https://community.hubspot.com/u/ElBr)\ **Post date:** [November 25, 2021, 9:21am UTC](https://community.hubspot.com/t/ticket-templates/12340/10 "2021-11-25T09:21:07Z")
Agreed!! ---
**Author:** ![LChatchatrian](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/lchatchatrian/32/78108_2.png) [@LChatchatrian](https://community.hubspot.com/u/LChatchatrian)\ **Post date:** [November 26, 2021, 9:28am UTC](https://community.hubspot.com/t/ticket-templates/12340/11 "2021-11-26T09:28:07Z")
Agree! it will also save lots of time for people who work with Tickets often. ---
**Author:** ![SSimon7](https://avatars.discourse-cdn.com/v4/letter/s/c68b51/32.png) [@SSimon7](https://community.hubspot.com/u/SSimon7)\ **Post date:** [March 31, 2022, 4:00pm UTC](https://community.hubspot.com/t/ticket-templates/12340/12 "2022-03-31T16:00:36Z")
I agree. Can’t understand why this feature has been delivered. ---
**Author:** ![AGiam](https://avatars.discourse-cdn.com/v4/letter/a/85f322/32.png) [@AGiam](https://community.hubspot.com/u/AGiam)\ **Post date:** [June 24, 2022, 5:03am UTC](https://community.hubspot.com/t/ticket-templates/12340/13 "2022-06-24T05:03:03Z")
Posting on behalf of a customer - He uses the ticket system to log service jobs and to record various bits of information. It would help to have different ticket properties for different pipelines, and to be able to create templates for ticket properties such as the ticket description to save time filling it up again and again. A further ability to set the template to be dependent on another set property would be good too! ---
**Author:** ![KDavisNY](https://avatars.discourse-cdn.com/v4/letter/k/7c8e57/32.png) [@KDavisNY](https://community.hubspot.com/u/KDavisNY)\ **Post date:** [July 28, 2022, 3:05pm UTC](https://community.hubspot.com/t/ticket-templates/12340/14 "2022-07-28T15:05:44Z")
Companies and departments have different types of requirements and tracking for tickets. It is not a one size fits all. Having different fields and layout depending on the ticket type will be a helpful addition and would increase use of the Hubspot platform. ---
**Author:** ![BHorvath](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/bhorvath/32/66176_2.png) [@BHorvath](https://community.hubspot.com/u/BHorvath)\ **Post date:** [August 18, 2022, 1:16pm UTC](https://community.hubspot.com/t/ticket-templates/12340/15 "2022-08-18T13:16:22Z")
It is very much needed. Different ticket creation templates should be available and customizable based on pipelines and teams! ---
**Author:** ![jpleht](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jpleht/32/31851_2.png) [@jpleht](https://community.hubspot.com/u/jpleht)\ **Post date:** [August 23, 2022, 11:23am UTC](https://community.hubspot.com/t/ticket-templates/12340/16 "2022-08-23T11:23:36Z")
This feature would be really helpful to our organization, please prioritize this! ---
**Author:** ![06684](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/06684/32/19503_2.png) [@06684](https://community.hubspot.com/u/06684)\ **Post date:** [October 11, 2022, 7:49pm UTC](https://community.hubspot.com/t/ticket-templates/12340/17 "2022-10-11T19:49:25Z")
Agreed! ---
**Author:** ![Lowe](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/lowe/32/74713_2.png) [@Lowe](https://community.hubspot.com/u/Lowe)\ **Post date:** [November 23, 2022, 5:24pm UTC](https://community.hubspot.com/t/ticket-templates/12340/18 "2022-11-23T17:24:10Z")
Please bring this feature to Hubspot! I’d love to be able to have a variety of templated tickets for our teams. we could integrate day to day jobs into HubSpot so much better! ---
**Author:** ![Stonehands](https://avatars.discourse-cdn.com/v4/letter/s/d9b06d/32.png) [@Stonehands](https://community.hubspot.com/u/Stonehands)\ **Post date:** [April 26, 2023, 4:09pm UTC](https://community.hubspot.com/t/ticket-templates/12340/19 "2023-04-26T16:09:53Z")
This is a much needed feature that can further optimize workflows and save time when creating tickets. If you have a common type of ticket that is created frequently, a template makes ticket creation trivial, consistent and mistake-free. ---
**Author:** ![daisyalmaguer](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/daisyalmaguer/32/15497_2.png) [@daisyalmaguer](https://community.hubspot.com/u/daisyalmaguer)\ **Post date:** [June 23, 2023, 5:35pm UTC](https://community.hubspot.com/t/ticket-templates/12340/20 "2023-06-23T17:35:45Z")
Dear Hubspot, I am the Customer Success & Community Manager at my company and this idea would be incredibly useful. Reason being is that my personal method of keeping track of all tickets is through my Support Pipeline. That said, I also open up “internal-facing” tickets with my team, which usually happens in another system (in my case, it’s Notion). That said, we have a template that we use for tickets in Notion, similar to snippets. It’d be really useful to apply the templates functionality to tickets as it would save me time in not having to copy/paste between both places. That said if anyone has a workaround, I’d love to hear from you! Sincerely, Daisy P.S. I’m new to posting in the Hubspot forum, appreciate any tips [Next page](https://community.hubspot.com/t/ticket-templates/12340.md?page=2)