Feature Requests

Action.ShowCard and Action.ToggleVisibility allow the card to change dynamically based on user input. As a one-man-band covering help desk, data management, systems admin and more, the less I have to switch systems/interfaces, the more efficient I can be. These actions would allow me to build a single card that can gather multiple unique sets of data and require minimal end-user input. Adaptive Cards: add Action.ShowCard and/or Action.ToggleVisibility

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.

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

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.

We have had users mention that they need a way to save filters (for them to view only) so they can quickly reference them later.

We love the Custom Form Answers but we'd like them to be more front-and-center when a ticket with a form is submitted. We'd like to see the Custom Form Answer in the response field as if it is a response from the user or IT. Right now, the Custom Form Answers are buried in a menu off to the right side and the only visual cue a form is there is the black text vs. greyed out text.

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.

When viewing chat history in TVA through adaptive cards, new messages are added to the chat at the top. It would be more intuitive if the message history grew from the bottom, as this is the convention in Teams itself.

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.

There are some systems that allow for automatic error reporting from a no-reply email (i.e. xerox printers). When these systems generate errors, they usually have error/fault codes, identifiers, location, and other useful information. By having an automation be able to merge tickets. The tickets that come in can be merged to a MAIN ticket for that error/fault code, location, identifiers, and/or the other information. There should be a date range for the automation to check if there are tickets within that range that meet the criteria for the merge. This saves agents time by not having to merge manually. Keeps the queue nice and orderly. Keeps relevant information to a specific ticket.

On the left side of the screen when you have a single ticket open in the web interface, there is a list of all the tickets. You can pick a default view, but it would be nice to be able to also pick a custom view that has been created. It would also be nice to be able to collapse that list of all the tickets. An extra feature that would be great is being able to navigate to the next ticket in the list via a next arrow some thing similar.

When a ticket of a specific Template is created, the virtual agent could respond back with information to the end user such as: Average resolution times Who they should expect to hear from For example: New Laptop Requests typically take 7 business days to complete You should hear from John shortly about your password reset In this way some type of expectation is set out of the gate for End Users based on current ticket metrics.

To give attention to the custom form answers that have been submitted with a ticket, it would be nice to have it auto expanded to show the answers so that it will grab the agents attention when looking at a new or existing ticket.

When you know you need to wait a certain amount of time before following up on a ticket, it would be useful to be able to set a date on which the ticket would automatically set its status back to Active, to help serve as a reminder for when to follow up on the ticket. A couple of examples: If a request is low priority, and the requester would like to come back to the request after a week. If you are waiting for someone else to do something and you want to make sure to follow up with them after a week.