Feature Requests

As an agent, I want to see the Request column bigger so I can read the full subject field. I am resizing this column a couple of times a day because its state is not saved upon refreshing/changing the Tickets page.

Someone in our office found a hole in our ticket generation policy after they realized that they can skip around using our company templates by simply typing "New Ticket" into the virtual agent. To see what I'm talking about, type "Help" into the virtual agent and you will see the phrase "New Ticket" mentioned. For now, we have been deleting this employee's tickets because it requires too much effort to apply a template/re-enter all of their data for them. Can you please investigate an option to disable the phrase "New Ticket" and its associated functions? We have been working hard to funnel requests into our very curated templates to make sure all information for requests is captured and sent to the right people. Every department has templates they use now, nobody should be entering default tickets anymore.

Is there a way to add ticket survey field to the filters so I can filter to those tickets that do not have a "Positive" feedback and try to fix any issues?

For audit purposes, I need to provide a extract of data between months. It would be useful to have a filter for Created Date whereby I can select In between dates

For example, we had a team who wanted their assignees to receive an email notification when any ticket was assigned to them. We can do that using automation, but it will also send them an email when they take a ticket and assign it to themselves. It would be useful if we could set a filter to say "if [Assignee] is Not Equal to [User who made the change]". That way, they would still get notified when someone else assigns a ticket to them, but they would not get the notification when they assign one to themselves.

Including options for PowerBI cloud native data access would allow for scheduled refreshing of Tikit data using OAuth and other supported OData authentication methods. For organizations like ours taking a cloud first approach eliminates the need for on-premise semantic model refreshes, and provides a simplified reporting approach.

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.

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

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!

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.

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

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

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

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.