We’re requesting a toolkit to create custom data validation rules for fields in Intercom Tickets. While the current field options are helpful, they have limitations that restrict our ability to tailor forms for specific use cases. Below are examples from our fintech cryptocurrency business to illustrate the need for enhanced flexibility and control:
Current Limitations and Use Cases
-
Number Field Enhancements:
- The existing ‘Number’ field only supports whole numbers. In the cryptocurrency industry, precision is critical. For example, Bitcoin values extend to 8 decimal places (e.g., 0.12345678), while other cryptocurrencies may use different decimal limits. A custom validation rule would allow us to define the precision required for each field based on the cryptocurrency in question.
-
Transaction ID Validation:
- Different transaction types have unique formats and validation requirements:
- A Debit Transaction ID is a 9-character alphanumeric string.
- An ATM Transaction ID is a 12-character string starting with “1337” and ending with three alphabetic characters.
- Currently, there’s no way to enforce rules like these, leading to potential errors and delays in processing.
- Different transaction types have unique formats and validation requirements:
-
Improved Date & Time Options:
- While the existing ‘Date & Time’ field is useful, splitting it into three distinct options—‘Date & Time,’ ‘Date,’ and ‘Time’—would significantly improve usability. For example:
- Sometimes we only need a date because the time is provided in a separate field.
- Other cases require a time but not a date, which is currently cumbersome for users.
- While the existing ‘Date & Time’ field is useful, splitting it into three distinct options—‘Date & Time,’ ‘Date,’ and ‘Time’—would significantly improve usability. For example:
-
Email Validation:
- Adding a rule-based ‘Email’ field would ensure proper formatting (e.g.,
user@example.com). - In cases where we need to collect multiple email addresses, having validation for comma-separated formats would streamline data collection and reduce errors.
- Adding a rule-based ‘Email’ field would ensure proper formatting (e.g.,
The Proposed Solution
We are requesting a toolkit that allows us to:
- Create custom field types with specific data validation rules.
- Define constraints like length, format, prefixes, suffixes, or character types.
- Implement precision controls for numeric values, such as the number of decimal places allowed.
- Enable advanced validation for text fields (e.g., regex-based validation).
Why This Matters
This functionality would empower us to build tailored forms for our customers, ensuring we collect accurate and actionable data. It would:
- Eliminate the need to repeatedly request new field types as requirements evolve.
- Enhance the customer experience by reducing confusion and errors in form submissions.
- Improve operational efficiency by ensuring data accuracy and consistency from the start.
Example Impact
With this feature, we could implement an ATM transaction field that accepts only values starting with "1337," a numeric field that allows 8 decimal places for Bitcoin, and an email field that validates multiple email entries in one field. These improvements would drastically reduce processing time and error rates while enabling us to use Intercom Tickets more effectively.
We hope this provides a clear picture of our needs and the value such a toolkit could deliver. Please let us know if additional examples or details are needed to assist in your evaluation.
Kind regards,
Justin Yawn
Operations Lead
Coinme