Feature Requests

Is it possible to add internal accounts even if they haven't scanned the QR Code for the Viber account? Currently, only requestors are assigned tags. However, I would like to use the form internally within our team as well. This is because, in the customized form settings, I’m unable to tag those who are handling the accounts.

Would it be possible to include the requestor's tag when exporting all requests? This would make it easier to sort and filter the data based on the company they are associated with or connected to. Having this information readily available in the export file would help streamline the tracking and organization of requests by company.

Currently, you don't have to options to pre-select the items or a group items to be displayed in a service request form. [Perse School]

Create a cancel button for request tickets submitted.

In the current Custom Service Request form builder, once options are created under a question (e.g., dropdown, radio button), their order is fixed unless manually deleted and re-added. This becomes problematic when users want to: Insert new options in alphabetical order Reorganize options for better clarity or grouping Maintain existing logic conditions tied to specific options [CPF]

Currently, the Fault Type question in Custom Service Request has a fixed system name and cannot be renamed like other custom questions. While the system needs to recognize it as a Fault Type for categorization and workflows, users should have the flexibility to rename the displayed question for better alignment with their internal terminology or user preferences. Proposed Functionality: Allow users to set a custom label for the Fault Type question while maintaining its system mapping. Ensure that the selected Fault Type still links to system parameters for reporting, workflows, and analytics. [NIE x Certis]

I would like to request the addition of Account Tags under the Request Setting in FacilityBot. This feature will be used purely for internal purposes to help us organize and categorize forms that are intended for internal use only. By enabling Account Tags, it will be easier for us to create and manage internal forms that need to be filled out by employees, such as equipment borrowing, fuel requisitions, and other non-client-facing processes. This will not only help streamline our internal documentation but also allow us to filter and retrieve specific types of requests more efficiently based on the assigned tag. Having this tagging option will greatly improve our internal coordination and tracking without relying on external systems.

Requesting the inclusion of the Requestor's Tag in the Excel export file from FacilityBot. This will help us better organize and track requests by category or department during data analysis and reporting. Ideally, the tag should appear alongside the requestor’s name or other requestor-related fields in the export. Thank you!

Cancellation Button with a Cancellation Remarks field will improve efficiency by allowing ADMIN USER to cancel unnecessary requests, even after completion. Requiring a reason ensures transparency, prevents errors, and maintains accurate records for better workflow management.

To have trigger terms for each request type, allowing requestors to make specific requests using these triggers in messaging channels.