Feature Requests

We've found the Custom Views feature on the main Tikit page to be very useful. However, it's unfortunate that an Agent needs to be a Super Agent or higher (in terms of permissions) in order to use it. I'd like to see it that each Agent can have their own, private set of views without needing the higher level of permissions. Having them be private (so that yours are only visible to you) would be helpful as well so that nobody can accidentally edit or delete Custom Views made by other people. A Super Agent or Admin could retain the ability to make Global Views that everyone can access, if a custom view is better suited to be used by a whole team.

We need a webhook option to automate pushing tickets to our external MSP. Would prefer not to use power automate.

In some use cases and organizations like ours, responding agents should remain anonymous to end users. Currently replying agents' and assigned agents' names appear to the end user. We would like the option to replace the agents' names with their tech groups' names in all instances where the agent name field may appear. This could be achieved with an anonymity toggle in Tikit's settings.

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

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.

Right now, the only way to add an attachment through Power Automate is through doing a Send an Email action to the helpdesk email we have connected to Tikit. It would be helpful to be able to add an attachment after creating or updating a ticket.

When sending a message in a ticket, the formatting appears differently when viewing the message from different locations. For example, when sending a message from web.tikit.ai that includes a double line break (press enter/return twice before a new line), the message appears with a single line break in the web.tikit.ai interface, with a double line break when viewed from the HelpBot in Teams, and has no line breaks in the email reply received by the requester. Also, Markdown formatting options seem to work when sending a message from the Teams HelpBot, but not from the web interface. Similarly, HTML code seems to work when sending messages from the web interface, and the formatting remains consistent in the email received by the requester, but the HTML code shows up as plain text in the Teams HelpBot.

Currently when adding an image to a comment, it adds it as an attachment. This creates two issues: Can't see the context of the image, especially if multiple images need to be added.The user has to click to open and view the attachment. Preferrably, you can upload/paste an image and have it embedded directly in the comment where intended.

The ability to search for what users type into the Custom Form Answers and for those to be able to be exported would be very useful.

Need Webhooks

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

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.