Skip to main content

FluentSupport

#Feature Request

Randomize Ticket Numbers with Prefix

Hey, quick question — is there a way in Fluent Support to randomize the ticket number and add a custom prefix? Right now, when setting up a new business, the numbering starts from 1, 2, 3, 4… but it would be great if we could either randomize the sequence or set a starting point with a prefix so it doesn’t look like a brand-new system.

  • 3 likes
  • 6 comments

Marjan Crabtree

Do you really think people care? Quick solution: a notificaton that you have moved to a new ticketing system. Then it makes sense that the numbers are low

Manoj Sharma

Marjan Crabtree People who? If you mean startups — hell yeah they care. It’s a trend, bro. Check out invoicing and support tools — you think they wanna kick off from invoice #1 or support ticket #1? No chance.

FYI

Support ticket systems that allow randomised/non-sequential ticket IDs:

  • Zendesk – Supports custom ticket ID formats with random prefixes/suffixes via triggers and APIs.
  • Freshdesk – Can use custom ticket ID patterns and include random characters.
  • Help Scout – Allows unique, non-sequential ticket IDs.
  • osTicket (open source) – Lets you configure ticket number formats, including randomisation.
  • Jira Service Management – Supports custom keys and IDs; you can generate randomised formats with automation.

Marjan Crabtree

not your bro, mate. I think they can crack on with more pressing matters.

Manoj Sharma

Marjan Crabtree  This is one of the pressing one mate, I would kindly suggest do your research before you comment, why do you think all the top ranking ticketing solutions out there has randomised and non-sequential ticket ids ? unbelievable lol

Rasel Siddiqe

We're discussing the randomizer function. However, due to our technical limitations, adding string prefix to Ticket ID will not be possible.

Manoj Sharma

Thanks you Rasel Siddiqe - I understand currently we have the following and because of that prefix is not possible.

  • When a new ticket is created, Fluent Support inserts a row into its fs_tickets table.

  • That table’s primary key is id (integer, auto-increment).

  • So the ticket number is literally the database ID:

    • First ticket → 1
    • Next → 2
    • Then 3, 4, 5 … sequential forever.

    Never the less, I am glad to hear that you are discussing randomizer , which is also amazing to have , and it will definitely would be a nice feature for the startups and will give some boost to your sales I hope!