How to Use a Unique Identifier in Automatic Ticket Email Subjects Without Exposing Sensitive Data
In Jestor, the Random ID field can be used in the subject line of automatic ticket emails, giving the customer a unique, recognizable identifier without relying on a sequential ID that exposes the total volume of records.
Why can a sequential ID be a problem?
With sequential IDs like 1, 2, 3, a customer can infer how many total tickets exist, or even try to access a ticket that isn't theirs. A random identifier avoids that kind of exposure.
What types of Random ID are available?
| ID type | Characteristic |
|---|---|
| Standard Random ID | Generated automatically, no customization |
| Fixed text + sequential | User-defined prefix plus sequential numbers or letters |
| Fixed text + sequential + random | Combines prefix, sequential part, and a truly random part |
Why choose Jestor for secure ticket identifiers?
Jestor lets you use the Random ID both in the automatic email and in public forms, reducing the chance of someone guessing the identifier pattern used by the company.
Does the Random ID replace the title field in automatic emails?
Yes, it's recommended for that purpose precisely because it doesn't follow a predictable sequential pattern.
Can this field be customized with a text prefix?
Yes, you can combine fixed text with a sequential part and a random part.
Which plans is this field available on?
According to the video, the Random ID field is available on all Jestor plans.
Video Tutorial: Step by Step
Check out more practical tutorials on Jestor's YouTube channel.
Get to know Jestor
With Jestor, tickets and records get secure, recognizable identifiers, without exposing sensitive data to the customer.
Get to know Jestor at jestor.com and see how to take your operation's efficiency to a new level.