Visit Freshworks.com Visit Freshworks

Best practice for the use of TAG's for a software developer.

  • 24 August 2023
  • 3 replies
  • 35 views
Lorentz
Rank
Userlevel 1
Badge

Hello

We are implementing Freshservice and are uncertain on how to best utilize the tags function to support our servicecenter. We deliver software in the energy sector both on premise and as hosted/SaaS. We have dedicated custom fields to store Software application information on incidents so that part should be well cowered.

Anyone care to share their usage and experiences?

 

Br.
Lorentz

3 replies

Daniel Söderlund
Rank
Userlevel 7
Badge +13

Hello

We are implementing Freshservice and are uncertain on how to best utilize the tags function to support our servicecenter. We deliver software in the energy sector both on premise and as hosted/SaaS. We have dedicated custom fields to store Software application information on incidents so that part should be well cowered.

Anyone care to share their usage and experiences?

 

Br.
Lorentz

I use tags most in workflow automations(WFA), to set tags when the flow is done/failed, to prevent loops if you use the update event. 

If you use the service catalogue, you can add the name of the service item as a tag then you can filter or create reports based on that. 

Use tags when using the Supervisor Rules to prevent loops.

Solution consultant @ synerity.eu, A new error is always a sign of progress!
eeha0120
Rank
Userlevel 6
Badge +11

Hi.

Adding to Daniel’s response, you can use tags for Analytics, not only for service items, but in general.

 

Regards,

Elvis Henriquez
Meetemmajhone111
Rank

Implementing Freshservice for your service center in the energy sector is a great step. To effectively utilize the tags function, consider categorizing incidents based on common themes like software types (on-premise, SaaS), specific application names, urgency levels, or even the location of the issue. This allows for streamlined tracking and sorting of incidents. Additionally, using tags to denote the stage of resolution (e.g., "Open," "In Progress," "Resolved") can enhance workflow management. Leveraging dedicated custom fields for software application information is a good approach, ensuring comprehensive coverage. Learning from others' experiences can provide valuable insights tailored to your industry and workflows.

Reply


Terms of UseCookie settings