Feature Requests

With Intune integration, if the user is the primary user on a device it will show up under linked devices. The ability to add a device as an affected item on a ticket would be helpful if a device does not have a primary user (Multi-User Device) or when a user is calling about an issue on a device where they are not the primary user. Being able to add an affected item and conduct a lookup from Intune and having the device information (Like the card that is on the linked devices page) available from the ticket would help in the above situation. It would also mitigate the number of clicks needed to find a user's device if they are the primary user.

When handling a ticket via mail connector, evert time the user replies, the logo from the signature becomes an attachment. It would be great, if this did not happen.

Right now, when we complete a lifecycle phase, we either need to refresh the page or switch to activity for a second or two and then back to Lifecycle. It would be awesome if it could trigger that refresh on it's own though

This would allow you to make a lifecycle with tasks that could be partially completed allowing the ticket to be resolved. For example new employees. Maybe the tasks are to set up a laptop they need because they were hired in Admin. While another new employee wont need a laptop because of a different department. Allowing the agent to mark a tasks as Non-Applicable so the ticket can be marked resolved. This affects the Agent and makes tasks more seamless without having to make multiple templates per department.

In many cases, in a lifecycle there will be a group of people that need to be notified about the task instead of just one person. Adding the ability to assign to a group would be helpful.

Would be handy to be able to bulk delete ticket, say a auto reply loop happens or any other reason needed to bulk delete

We have had users mention that they need a way to save filters (for them to view only) so they can quickly reference them later.

Have a log for when ticket runs an automation and the results of that process

I would like to see a way to separate knowledge bases. We have many sites and there are different procedure or tech at each one, and it would be cool for employees at site A to only be able to see KBs for that site.

When Agents use a knowledge article to resolve a user's incident or request the Agent should be able to connect the knowledge article to the ticket. When users are directed to a knowledge article to self-resolve their incidents, that knowledge article should be automatically connected to the corresponding incident. This function (especially if those connections are automated) will help to identify knowledge articles which would benefit from enhancement, which could be disabled, and which are particularly helpful.

For certain groups within our department, we assign a ticket to a group, then they can take the ticket or assign it to an individual of the group when ready. I think the automations could be easier to use if you had fields to complete for notifications, like Type of notification (Teams, email), Notify (Requestor, Assignee, Group), etc. Either way, if we could notify a group, that would be awesome, thanks!

Is it possible to show Triage members when agents are Out of Office and for how long? When Triage members have to assign the ticket to the agent, they have no visibility whether the agent is in the office or not.

We have common responses that we often send to our users. One such response we send is asking for them to provide us with their Teamviewer information so we can remote in. I have to tell them where to find it, which numbers to give us, and that they need to keep the program up and running on their machine so we can complete the remote connection. It would be fantastic if we could create response templates that already has all of this information typed in that we could simply select and have it filled out in the response box. It would save me and my team a lot of time and typing.

Currently, if a user submits a ticket to Tikit via email, and we reply to the user via email (in order to send a message with better formatting, insert an image in the message, or CC users on the message), the next email reply from the user will create a new ticket, which we will then need to merge into the original ticket. Similarly, if the user submits a ticket to Tikit via email and CCs other people on the request, if the CCd users reply to the email, it will also create new tickets for each new email sent by the CC'd users, or by the original user if they reply again. We then need to change the requester to the original requester and merge all the tickets (which also sends each user a few ticket status update emails). Auto-replies from the requester to the Tikit status notification emails when updating the ticket also seem to create a new ticket.

Would like a Every Weekday (Monday - Friday) trigger in automations.