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

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 an approval is needed, there is often an attachment that needs to be viewed in order to execute the approval. It is my understanding an approver should have access to view the ticket and any attachments. When I test this, the notification comes through with a view ticket option but when you click view ticket, the Tikit Virtual Agent says "I am sorry I don't have information regarding that topic..." How can an approver view the ticket and attachments in order to approve?

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 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 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 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.

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.

I have not really found any timers within Tikit.. am I missing something (could very well be). Certainly I think timers should be built into a ticket application to understand a variety of metrics including: How long a ticket takes to close How long a ticket is in the system before it is claimed How long a ticket stays in certain state (Pending, Open, etc) Further, it would be good if certain timers only ran when tickets were open and/or had eyes on them, as opposed to a timer that just runs. This could give better understanding of actual time worked on a ticket.

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

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

We attach SLAs to tickets assigned to one of our support teams... expectation is that tickets are moved out of the "pending" stage and into the "active" stage within a specific timeframe. We've noticed a number of tickets breaching that SLA due to the timing of ticket submission. After business hours, we obviously aren't expecting the team to hit their target time, so think it would be an awesome feature to add time limits to when an SLA would actually go into effect.

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

I would like the ability to select "Weekdays Ago" and "Weekdays from Now" Relative Date in Automations. For Example, it would be useful for "Auto close tickets resolved for 3 days or more days" Automation so the tickets do not get closed on the weekend when nobody is in the office.

I have been working in Power Automate to generate weekly e-mails to our agents with SLA, open assigned tickets and other stats. It's been a little tedious and even more tedious to modify or add multiple data sets to the emails. I'd love to see automated email reporting built in.