Skip to main content

Freshservice Ticket's Numbering


Forum|alt.badge.img+3
  • Skilled Expert
  • 8 replies

Hi, I have a query about ticketing in Freshservice.
Can anyone please tell me, is there possible to use a custom prefix number on ticketing around Incident / Problem / Change / Release?

Thank you. 🙂

Did this topic help you find an answer to your question?

6 replies

eeha0120
Skilled Expert
Forum|alt.badge.img+12
  • Skilled Expert
  • 732 replies
  • June 8, 2023

Hi,

Currently, it is not possible to use a custom prefix number.

I’d particularly love this too.

If you submit or have already submitted this as a Feature Request, please share the link in order we could vote.

 

Regards.

 


Forum|alt.badge.img+1

This is something we’re currently missing as well. TOPdesk provided the option to use prefixes to ticket numbers, which made them more recognizable and familiar. It’s a feature that we’d like to use again now that we’re using Freshdesk.


Forum|alt.badge.img+3
  • Author
  • Skilled Expert
  • 8 replies
  • July 2, 2024

Hi,

Consider that will be helpful for any organizations to understand their customer/ employee queries, I have been raise an Idea related the Ticket Prefix.
You can join to vote the Idea to have Include in the Product Roadmap. 😄

Custom Ticket Prefix in Workspace


Forum|alt.badge.img+1

Hi Aldo,

 

I just submitted one myself as well: 

https://community.freshworks.com/ideas/configure-a-prefix-for-ticket-numbers-37353

I upvoted yours too. I see your idea is to have a prefix per product, which is something that would be useful for us as well, but we mostly would like to have a prefix (even if it’s for the entire environment).


Forum|alt.badge.img+3
  • Author
  • Skilled Expert
  • 8 replies
  • July 2, 2024

Hi kees.brandsema,

I already upvoted yours also, it should be helpful for helpdesk as well to have a prefix for every product they have.


daisy812932
Community Debut
Forum|alt.badge.img+1
  • Community Debut
  • 12 replies
  • November 15, 2024

It might be possible.


Reply