Feature Requests

Summary Allow tickets to include additional users as collaborators, beyond the single primary requester currently supported. Problem A ticket today can only be tied to one user. In real cases, mo...

Allow agents to record time spent working on individual tickets, including multiple work sessions and entries by different staff members. Time entries should support reporting by ticket, technician, t...

We'd like to create an A or CNAME record in our DNS, e.g. helpdesk.MYDOMAIN.org, to point directly to our Manage1to1 instance.

I know I have a request in to add the ability to click on the device from an incident to open the device page. But it would also be great to have more information about the user as well. If we could h...

Align the platform's behavior with its documentation and legal/retention expectations by locking replies from being edited after they're posted, while allowing notes to be edited — restricted to the o...

When you click to view rooms show responsible staff on first screen.

It would be helpful to include the Battery health field in MDM Information from Google. This would be helpful for staff to quickly troubleshoot potential power issues, rather than having to pivot to t...

A report that shows users with multiple devices currently checked out would be helpful.

Add Configurable SLAs by request type/department/other criteria. Ensure the dashboards reflect these SLAs and flag at risk tickets through multiple options (highlights, email/notifications) prior to S...

The system should identify potential duplicate or recurring tickets by analyzing similarities in ticket subject, description, category, affected service/device, location, user, and/or timeframe. When...