Feature Requests

Why an Expanded Search is Crucial for Both End-users and Agents: Swift Issue Tracking for End-users: Sometimes, users might recall a specific comment they made or a keyword from a related knowledge article rather than the exact ticket details. An expanded search would allow users to quickly locate their past tickets, follow up on ongoing issues, or even avoid submitting redundant requests. Efficiency Boost for Agents: Agents juggle multiple tickets simultaneously. Being able to search using varied parameters like assignee, type, category, or phase can immensely help them prioritize, categorize, and resolve tickets faster. For example, an agent could pull up all 'High Priority' tickets in 'Phase 2' in a matter of seconds, ensuring urgent issues get timely attention. Holistic View and Analysis: Agents often need to review the history of recurring issues, analyze patterns, or even identify potential solutions suggested in comments or knowledge articles. An all-encompassing search function means less time hunting and more time resolving. Improved Collaboration: In scenarios where teams collaborate on a ticket, it's invaluable for agents to search by 'Group' or 'Team', ensuring seamless communication and faster resolution. Enriched User Experience for All: By catering to diverse search habits and memory cues, we are enhancing the experience for everyone, whether they're submitting a ticket or resolving one. Advanced Analytics and Insights: With more comprehensive search capabilities, team leads can generate in-depth reports to identify bottlenecks, strategize improvements, or even allocate resources more effectively. What would be searchable? Comments, Tags, Ticket Number, Resolutions, Knowledge Articles, Assignee, Type, Category, Phase, Priority, Group, Team, Status, Attachment Names, Custom Forms, and other relevant fields

When a ticket is already closed and users reply to this old ticket via mail, their mail is being “lost”. The mail connector does not pick up the mail as it identifies the closed ticket. The user on the other side is not informed that the ticket is already closed. So this mail is lost in the mailbox. It should be possible to either set an automation task (which isn't right now as a proper trigger is missing) or to enable this automated reply on closed tickets somewhere in the settings.

There are many choices for columns, but if I select more than 12, I can't scroll right to see them all. Chrome and Edge. Support informed me that this is not currently available.

It would be great if we could have a button to attach a KB article to a message being sent for a ticket. For example, we want to be able to have requesters create a ticket and fill out a template, then we (the agents) manually determine which KB article is relevant to their very specific scenario and simply send the KB article in response instead of having to type all of the content in a ticket comment.

If multiple employees are submitting tickets that are all related to the same ticket - it would be great to give help desk employees the ability to create a single Parent Ticket, then relate all of employee submitted tickets as Child Tickets. Given this functionality, you may then want to: Perform mass communication from a single Parent ticket Change how you report on tickets Control properties of all of the Child Tickets via the Parent Ticket Still allow individual communication on Child Tickets so Analysts could work with Requestors one on one Per: https://roadmap.tikit.ai/roadmap/ability-to-merge-tickets

Whether submitted in Virtual Agent, in the main application or via Power Automate flows, it would be nice to have the ability to format entries. Being able to push in multi-line comments, bulleted lists and even tables would be very helpful. Many times the entries get condensed into one line, making it really hard to read.

On the left side of the screen when you have a single ticket open in the web interface, there is a list of all the tickets. You can pick a default view, but it would be nice to be able to also pick a custom view that has been created. It would also be nice to be able to collapse that list of all the tickets. An extra feature that would be great is being able to navigate to the next ticket in the list via a next arrow some thing similar.

Cut down on tikit teams notifications by allowing the analyst to select the notifications they wish to get.

Small one but it would be nice to have the option of changing the colour of text in KB articles. I appreciate BOLD/Italic is there but it would be useful to indicate important info in red for example.

We provide monthly reporting to our IT Committee that includes a listing of our tickets. We require there be a resolution description in the report. Currently TIKIT does not have a field to leave a resolution. I would like for there to be a required resolution description upon closing/resolving a ticket. Sometimes tickets are closed without any notes and then we can't even refer back to old tickets to get the resolution.

I just want to be able to assign a unit of time. Like 0.5 hours spent on the ticket. This helps tracking resolution times and expectations for how long a type of ticket should need to be resolved. Thanks!

We are getting hundreds of tickets a day in some cases and it would be much easier to work the tickets for a group if we could see more than 20 tickets on the screens, something like 50 would be much easier to work with.

I would like to be able to schedule meetings from a ticket and add a tikit tab to the meeting so that I can interact with the Ticket the meeting is about.

I would like a full featured ticket mobile app. This would allow a wider range of devices to be used with ticket which would allow agents not to be restricted to web browser only. This would also allow for more control over push notifications and ease of more timely updates. IOS First priority.

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.