Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3166 Ideas

    Duncan I.New Participant

    Feature Request: Custom Data Validation Rules for Intercom Ticket FieldsSubmitted

    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. 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. 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. The Proposed SolutionWe 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 MattersThis 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 ImpactWith 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 YawnOperations LeadCoinme

    Duncan I.New Participant

    Feature Request: Workflow/Channel Level Rate Limits for Fin UsageSubmitted

    We are requesting a feature enhancement to enable workflow/channel level rate limits for Fin usage. This functionality would provide greater control over expenditures while empowering teams to expand Fin's application confidently across more workflows.Proposed Functionality 1. Workflow-Specific Spending Limits:Allow organizations to set monthly expenditure limits for Fin usage at the workflow and/or channel level. When a workflow or channel reaches its limit, the system should automatically transition to an alternative process that does not incur per-use costs.2. Alerts and Notifications:Provide configurable alerts as workflows approach their Fin usage limits, with thresholds (e.g., 80%, 90%). Notify designated stakeholders to ensure proactive monitoring and decision-making.3. Flexibility for Adjustments:Enable teams to adjust workflow-specific limits or reallocate resources both before and after the rollover occurs. Provide detailed usage data and projections to support informed adjustments.RationaleThis feature would significantly enhance our ability to manage Fin usage costs while maximizing its utility. By implementing workflow-level rate limits, we would:Gain confidence in using Fin across more workflows, knowing that expenditures are controlled. Maintain operational continuity by transitioning to predefined workflows when limits are reached, avoiding interruptions. Improve budget predictability and reduce unexpected overages.Example Use CaseSuppose we allocate $2,000 per month for Fin usage within a specific workflow, such as email responses. Once that limit is reached, the system could automatically shift to a backup workflow that avoids Fin usage, ensuring continued service. Alerts at 80% and 90% of the limit would enable us to proactively make adjustments, such as increasing the budget or modifying the workflow.Expanding this capability to other workflows where Fin is added would encourage broader adoption, allowing us to leverage Fin’s capabilities more effectively while maintaining financial control.We believe this enhancement would provide significant value by fostering confidence in Fin’s scalability across workflows, improving budget management, and ensuring seamless customer service.Thank you for considering this request. Please let us know if additional details or use cases would be helpful.Kindly,Justin YawnOperations LeadCoinme