# Tiered Tickets Help

**URL:** <https://community.hubspot.com/t/tiered-tickets-help/18718>\
**Category:** Tips, Tricks & Best Practices\
**Created:** [February 11, 2020, 8:51pm UTC](https://community.hubspot.com/t/tiered-tickets-help/18718 "2020-02-11T20:51:00Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![porton](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/porton/32/38114_2.png) [@porton](https://community.hubspot.com/u/porton)\
**Post date:** [February 11, 2020, 8:51pm UTC](https://community.hubspot.com/t/tiered-tickets-help/18718/1 "2020-02-11T20:51:00Z")

</div>

I am trying to set up our brand new Service Hub ticketing system. I want to be able to enable users to create tiered tickets. The examples below would actually form a decision tree based first on Product Type chosen, then specific instrument, then specific problem

**Choose Product Type:** Instrument or Consumable

**Instrument:**

CP Select, CP 150, Bobcat ACD-200, LVC

**CP Select**

**Choose Problem:**

Elution, Sample, Power, Software, Operational Mode, Shipping Damage, Extreme Failure

**Elution:**

Describe the problem in detail: Free flowing text…

**Consumable:**

.45 Tip, .2 Tip, .05 Tip, Ultra Tip

**.45 Tip**

Describe the problem in detail: Free flowing text…

Does anyone have experience building this type of ticket /these types of tickets

---

<div class="post-metadata">

**Author:** ![Jenny](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jenny/32/24_2.png) [@Jenny](https://community.hubspot.com/u/Jenny)\
**Post date:** [February 13, 2020, 9:24pm UTC](https://community.hubspot.com/t/tiered-tickets-help/18718/2 "2020-02-13T21:24:26Z")

</div>

Hi @porton,

I want to tag in a few subject matter experts who may be able to assist with this! [@Mike\_Eastwood](https://community.hubspot.com/t5/user/viewprofilepage/user-id/9259), @johnelmer, @joshua-paul do you have any suggestions for @porton?

Thanks,  
Jenny

---

<div class="post-metadata">

**Author:** ![porton](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/porton/32/38114_2.png) [@porton](https://community.hubspot.com/u/porton)\
**Post date:** [February 13, 2020, 9:42pm UTC](https://community.hubspot.com/t/tiered-tickets-help/18718/3 "2020-02-13T21:42:14Z")

</div>

Any suggestions will be greatly appreicated, thanks!

---

<div class="post-metadata">

**Author:** ![Mike\_Eastwood](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mike_eastwood/32/70075_2.png) [@Mike\_Eastwood](https://community.hubspot.com/u/Mike_Eastwood)\
**Post date:** [February 13, 2020, 9:43pm UTC](https://community.hubspot.com/t/tiered-tickets-help/18718/4 "2020-02-13T21:43:48Z")

</div>

Hi @porton , thank you [@jennysowyrda](https://community.hubspot.com/t5/user/viewprofilepage/user-id/3685)

I was literally about to write some code to do a Category, Sub Category manager for Tickets (I think this is called constructive procrastination).

We’re working on a HubSpot Integration, for a client of ours, that will allow the Support Team to classify a Ticket with Categories and Sub Categories. They have over 150 Categories and Sub Categories so a single list is a bit clunky.

But it looks like you want a Customer to be able to Categorise the Ticket when they submit a Ticket… is that correct?

Mike

---

<div class="post-metadata">

**Author:** ![porton](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/porton/32/38114_2.png) [@porton](https://community.hubspot.com/u/porton)\
**Post date:** [February 13, 2020, 9:50pm UTC](https://community.hubspot.com/t/tiered-tickets-help/18718/5 "2020-02-13T21:50:46Z")

</div>

Yes, that is correct. But we are just getting our feet wet with Service Hub so we also want our Customer Service employees (all 3 of them!) to be able to categorize/tier the tickets, too; if that makes sense.

Thanks!

---

<div class="post-metadata">

**Author:** ![briansweat](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/briansweat/32/2008_2.png) [@briansweat](https://community.hubspot.com/u/briansweat)\
**Post date:** [February 16, 2020, 4:28pm UTC](https://community.hubspot.com/t/tiered-tickets-help/18718/6 "2020-02-16T16:28:21Z")

</div>

We use a single service hub form currently, but are looking at using the chat bot to ask a few questions to better categorize tickets. It’s so much more flexible than a regular, single form.

---

<div class="post-metadata">

**Author:** ![Mike\_Eastwood](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mike_eastwood/32/70075_2.png) [@Mike\_Eastwood](https://community.hubspot.com/u/Mike_Eastwood)\
**Post date:** [February 16, 2020, 11:02pm UTC](https://community.hubspot.com/t/tiered-tickets-help/18718/7 "2020-02-16T23:02:40Z")

</div>

Hi @porton ,

@briansweat idea is great!

Does that work for you?

Mike

---

<div class="post-metadata">

**Author:** ![porton](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/porton/32/38114_2.png) [@porton](https://community.hubspot.com/u/porton)\
**Post date:** [February 17, 2020, 2:29pm UTC](https://community.hubspot.com/t/tiered-tickets-help/18718/8 "2020-02-17T14:29:41Z")

</div>

That sounds like a great potential solution! How difficult was it to build your chat bot?

---

<div class="post-metadata">

**Author:** ![joshua-paul](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/joshua-paul/32/78096_2.png) [@joshua-paul](https://community.hubspot.com/u/joshua-paul)\
**Post date:** [February 25, 2020, 5:52pm UTC](https://community.hubspot.com/t/tiered-tickets-help/18718/9 "2020-02-25T17:52:30Z")

</div>

Hi Porton, This is a fun one and not too hard to build in a chat bot! The most time-consuming part will be thinking through your business rules on paper before clicking around in the chat bot builder.

The good news is that your options for messaging, rules, and routing are endless with HubSpot chat bots. Given that I don’t know all of the ins and outs of your use case, here is how I would approach this in its simplest form. (For instance, you’ll have many more branches and actions based on the selection that the user makes.)

 ![](https://d2qpr2jzcazej7.cloudfront.net/original/3X/d/1/d12b0b1ac9b34e89d9a939c4dc17ad2cf798b8e8.png)HubSpot Chat Bot

---

<div class="post-metadata">

**Author:** ![porton](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/porton/32/38114_2.png) [@porton](https://community.hubspot.com/u/porton)\
**Post date:** [February 25, 2020, 7:15pm UTC](https://community.hubspot.com/t/tiered-tickets-help/18718/10 "2020-02-25T19:15:23Z")

</div>

Wow, this is extremely helpful, Joshua-Paul! Your example flow is very easy to understand and has really turned the light bulb on for me! I look forward to working on this; thanks again for your great suggestions!
