We are not currently using HubSpot to manage support tickets. But are really wanting to consolidate resources into one platform (HubSpot).
Our SaaS organization has multiple business lines; we categorize our customers to the city they are in (i.e., Los Angeles, CA), but that city might have multiple products they are purchasing.
When a support ticket would come in, what is the best way to set up the company's & contact's so that our support team can quickly find the correct organization information to best help the customer?
Would using a parent-child company relationship be best? Los Angeles, CA (Parent) - Product 1; Product 2; Product 3 (Child)?
I assume other organizations have experienced this challenge before, just looking for some general advice as we work towards using the service feature.
I think the answer to this will depend on how similar the stages and processes would be for solving the tickets between different products.
If they are substantially different, you may want to consider creating multiple ticket pipelines. To do this go to your tickets view and click “All Pipelines” > Edit Pipelines.
Then in select a pipeline you can select create pipeline.
From here you can build new pipelines “product 1, product 2, etc.” and configure the stages to your liking below.
Then once you have them built out in your pipeline view “all pipelines” to see the parent view, or select a specific pipeline to see a particular product.
To solve for having teams in different cities, what may make sense here is to have a regional property built for your tickets that you can create custom views for each team to work out of.
To do this:
In the top right corner of your ticket pipeline view, click Add views > Create view.
Once you name it and save it, select advanced filters.
From there customize the criteria you would be looking for (ie. Ticket region = Los Angeles).
Once you update that, just remember to save the filter criteria (top right corner)
Then you will have a vew specific for that regions tickets, and can make others for the other regions you use.
You can also create a custom property for your ticket products and filter them in ticket views instead of creating new pipelines if that’s easier. I’d recommend doing that if all of your pipeline stages are the exact same for each product.
Hope this helps,
Ben
Did this answer your question? If so, please help the community by marking it as a solution.
I think the answer to this will depend on how similar the stages and processes would be for solving the tickets between different products.
If they are substantially different, you may want to consider creating multiple ticket pipelines. To do this go to your tickets view and click “All Pipelines” > Edit Pipelines.
Then in select a pipeline you can select create pipeline.
From here you can build new pipelines “product 1, product 2, etc.” and configure the stages to your liking below.
Then once you have them built out in your pipeline view “all pipelines” to see the parent view, or select a specific pipeline to see a particular product.
To solve for having teams in different cities, what may make sense here is to have a regional property built for your tickets that you can create custom views for each team to work out of.
To do this:
In the top right corner of your ticket pipeline view, click Add views > Create view.
Once you name it and save it, select advanced filters.
From there customize the criteria you would be looking for (ie. Ticket region = Los Angeles).
Once you update that, just remember to save the filter criteria (top right corner)
Then you will have a vew specific for that regions tickets, and can make others for the other regions you use.
You can also create a custom property for your ticket products and filter them in ticket views instead of creating new pipelines if that’s easier. I’d recommend doing that if all of your pipeline stages are the exact same for each product.
Hope this helps,
Ben
Did this answer your question? If so, please help the community by marking it as a solution.