Feature Requests

Please add a feature for auto refresh on the tickets board at https://web.tikit.ai/tickets/board We use this to track all tickets and us not refreshing has caused us to miss tickets. An autorefresh would mitigate that.

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.

We need users to be able to add another staff to affected users. Currently this is only possible if they use email and CC other staff. We want them to be able to add the using the agent or web. There is often times when they need to be able to have multiple people on the ticket.

Some users will attempt to bypass the tikitbot via email or just ignoring the bot's suggestion, thinking that if they talk to a tech their problem is resolved quicker. To reinforce that some items are in fact intended to be self-service, i'd like to be able to have an option to search the KB and add a response to a tikit from there, right from the tikit response dialog.

Allow/set automations to run at a scheduled time of day i.e. only during business hours.

I know that Tikit currently sends surveys through Teams, but email is more commonly used here, and so having an option to send an email with the survey would be very handy. Also, we would want to specify who can access the surveys, and perhaps even get an email alert when one is filled out.

The ability to create scheduled or recurring tickets would be very beneficial. You could set the ticket description, category, requestor, future start time, and recurrence pattern as minimum requirements. Optional would be things like assignee and due date. Once set, when the future start time is reached, the system would create the requested ticket. Some examples of the types of tickets that could be scheduled are: Renew domain registrations, SSL certificates, software licensing annuallyReview backup logs dailyPerform server updates monthly Scheduled tickets with the ability to set recurrence would not only serve as reminders to complete the scheduled task, but would also serve as records that the tasks were completed as desired.

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.

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.

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.

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

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!

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

This feature would be extremely beneficial as it prevents duplicate responses to the same requester. I ran into two situations today where my co-worker and I responded to the same ticket and accidentally unassigned one another since the ticket didn't update in time. I believe if we were notified when others were viewing tickets we're working on, it would allow for stronger communication and overall better organization of our tickets.

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