Feature Requests

It is not very helpful to follow the flow of comments, mails and actions for a ticket, especially in interaction with other systems, if those show in Tikit only imprecise date/time stamps like "2 days ago". Please replace this with an exact date & time like "2026-09-10 15:30:33"

Because private comments aren't being sent to anyone, I think that it would make sense to be able to edit them. It would be useful to be able to fix typos or update the information in notes taken within private comments.

When viewing the list of tickets, it's hard to tell which tickets have had responses or updates since the last time the ticket was viewed. I think it would be helpful to mark the titles of tickets with unread updates in a bold font or in a slightly different color to make it easier to easily tell when a ticket has updates that need to be reviewed. Having a timestamp in the "Last Modified Date" column is another thing that would also help differentiate newly updated tickets. The idea in this post is sort of related and may help this issue as well: https://roadmap.tikit.ai/b/6vre6g0l/feature-requests/last-received-message-in-list-view

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

Please integrate tikit with MS copilot. It would be useful in scanning the tikit to draft a reply to the customer.

The "When a Ticket Created" trigger is too soon. If you use "When a ticket is updated" it fires off the flow constantly. The flow automation only needs to run once, but after the template is applied to the ticket.

There are some systems that allow for automatic error reporting from a no-reply email (i.e. xerox printers). When these systems generate errors, they usually have error/fault codes, identifiers, location, and other useful information. By having an automation be able to merge tickets. The tickets that come in can be merged to a MAIN ticket for that error/fault code, location, identifiers, and/or the other information. There should be a date range for the automation to check if there are tickets within that range that meet the criteria for the merge. This saves agents time by not having to merge manually. Keeps the queue nice and orderly. Keeps relevant information to a specific ticket.

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!

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.

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

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

I think that having a way to send alerts/notices about outages or other IT related alerts via the TVA would be nice to have. It has the potential to back-fire a bit I guess if users begin replying to the alert and potentially creating tickets saying, "Thank you for the heads up".

It would be more efficient if we could copy and paste images into ticket replies via the Tikit online portal. I understand there is an upload image option, however you must first copy and save the image before uploading it. To view the image, the requester still needs to click on it. If the option to paste was available, it would save time for both Agent and Requester.

It would be good to have the information on who the ticket has been assigned to in the active tiles.

We would like to be able to add email addresses to groups. We have several application teams that receive their own tickets, and it is cumbersome to have a MS team set up for each of them or have someone sort them manually into the proper channel.