Feature Requests

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.

Why is my idea useful? -Visual Representation: A calendar view provides a clear and intuitive visual representation of scheduled events, tasks, appointments, and deadlines. It allows users to grasp the timeline and understand the sequence of activities more easily. -Scheduling and Planning: Service Desk teams can use the calendar view to schedule and plan their work effectively -SLA Compliance Monitoring: SLA's have specific response and resolution times. -Coordination and Collaboration: Calendar views allow different teams and team members to synchronize their schedules and collaborate more effectively in and out of TIKIT. -Better User Communication: With a calendar view, service providers can communicate timelines to customers more clearly; also helps with scheduling 1:1 or 1:n meetings. Who would benefit? End-Users and Agents How should it work? The Calendar view should be placed on the main web.tikit.ai page in the left sidebar. The view should be able to toggle between Agenda, Weekly, and Monthly. The Calendar view should contain toggle-able data on Due Dates, SLA Breach Date/Times, Shared Calendars from M365, The Calendar view should have RBAC for what data gets shown to End-Users vs Agents. (e.g. End-Users should not be able to see a shared department calendar; End-Users should see their ticket displayed.) Clicking on a data point within calendar should take you to it's prospective link (e.g. M365 Event: opens that Outlook event in another tab; TIKIT Ticket: Opens the web.tikit.ai/ticket/#### view for that ticket in the same tab.) The Calendar view toggled data point and Agenda, Weekly, and Monthly view should persist between sessions.

I think it would be helpful if there was an option to require an assignee before a ticket is resolved/closed. Similar to the setting for a Resolution Category or Notes. This would help to make sure that all tickets have an assignee (or person who worked on and closed the ticket).

To include an option where I can review and restore deleted tickets from my teams or myself, as other ticketing systems do

Currently the URLs returned for documents/links via TVA and OpenAI integration force the user to download the documents/webpages instead of opening in the browser. It would be useful to have the documents/webpages open via defaults set by the user (ie. open a new tab, view in browser, open from a temp file location). In our use case, we crawl a website to index in our OpenAI implementation, the URL for the referring source is displayed, however when the user clicks on the URL, it downloads the indexed blob from Azure storage instead of opening the referring URL. This is likely due to TVA using the "filepath" as the citation instead of the source URL, with a download action instead of opening in a new browser/viewer, etc.

It would allow us to use Tikit for approvals for processes that require logging for the reasons for the decision.

Most systems I have worked in, supported, or been a customer in, allow the users to cancel a ticket they have submitted. I had not really noticed until one of my users brought it up.

Sometimes the pictures attached to comments for via email is too small. Perhaps having the ability to zoom in would resolve this issue.

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

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

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.

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.

Currently we have started tracking resolution time as an average of the resolved time function on our PowerBi daily reports Is there is a way that we can “stop the clock” when tickets are in a certain status. For our environment in particular we are looking to not have time count when they are in a Awaiting vendor, Awaiting user, or Problem status. Its not as simple as removing any tickets that are currently in that state from the average as they will still have that time when they enter the resolved state. I also realize this is difficult as it does not keep time as it more reflects time as a function X amount of time from creation date. Any ideas on how this can be achieved?