How to create custom record IDs
Custom record IDs give each ticket, order or client an identifier your team can say out loud, write in an email and search for later. In Jestor, a dedicated field generates them automatically, with a pattern you define rather than a bare sequential number.
Why the identifier matters more than it seems
An internal record number leaks out constantly. It goes into emails, gets read over the phone, appears in a customer reference and ends up in a spreadsheet someone else maintains.
If that identifier is ambiguous or easily confused with another number, every one of those interactions carries a small risk of error.
Where a proper identifier helps:
- Tickets referenced in customer communication
- Orders quoted over the phone
- Client codes used across systems
- Documents that need a traceable reference
- Records where a predictable sequence would reveal volume
Sequential or generated identifiers
| Approach | Characteristic | Best for |
|---|---|---|
| Sequential ID | Counts upward in order | Internal records, auditing |
| Generated ID | Not derived from the count | References shared externally |
| Custom pattern | Structured to your format | Identifiers people read aloud |
Step by step to configure one
- Add the identifier field to the table holding the records.
- Name it after the record type, such as ticket ID or order ID.
- Choose the generation style, sequential or generated.
- Define the pattern, since the field is customizable.
- Let it fill automatically whenever a new record is created.
- Use it in communication, in emails, messages and documents.
Why a sequential number is not always the right choice
A sequential identifier tells anyone who sees two of them how many records you created in between. For internal work that is harmless and even useful. For a reference shared with customers or partners, a generated identifier avoids disclosing volume you did not intend to share.
- Filled automatically: created with the record, no manual step
- Customizable pattern: the format follows your convention
- Works for any record type: tickets, orders, clients, contracts
- Searchable: a reference people can actually look up
Frequently Asked Questions
Is the identifier created automatically?
Yes. It is generated when the record is created, with no manual entry. See jestor.com.
Can I define the format myself?
Yes. The field is customizable rather than fixed.
When should I avoid a sequential number?
When the reference is shared externally and you would rather not disclose record volume.
Video Tutorial: Step by Step
With Jestor, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.