Feature Requests

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

If a life cycle gets applied to a specific ticket by someone or a template and it happens to be the wrong one or not needed there needs to be a way to remove said Life Cycle from the ticket.

When creating or updating tasks via Power Automate it would be helpful to be able to assign tasks to a group and/or team instead of only being able to assign to an individual.

To utilize Tikit, we require the ability to print or export a PDF of a completed tikit to include the custom form answers, and any correspondence throughout the resolution process. There are situations that require us to show our process and resolution on certain incident reports and not being able to do that limits our use of tikit.

Zendesk has this feature called "macros" ( https://support.zendesk.com/hc/en-us/articles/4408844187034-Creating-macros-for-repetitive-ticket-responses-and-actions ) where you can create text templates that can be searched while in a ticket and then inserted, so that you can have pre-made text for common replies. I know there's the Knowledgebase, but that assumes you've corrected guessed all the ways a user will ask a question that leads to a particular prompt. And sometimes you might want to mix and match if it's multiple questions, or just want to copy the structure from a reply, but the exact macro wouldn't apply. Thank you for your consideration!

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 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!

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

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.

The "When a Ticket Created" trigger is too soon. If you use "When a ticket is updated" it fires off the flow constantly. The flow automation only needs to run once, but after the template is applied to the ticket.

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.

When a request triggers a Knowledge article, the requestor is given the opportunity to mark the response as not helpful so they can proceed with opening a new ticket rather than being deflected. However, when a request triggers a template, no such option is given, and the user has to ignore the template and try to figure out a way to rephrase their request so it doesn't trigger the template.

Why is my idea useful? -Enables precise targeting of specific tickets to apply specialized SLAs -Allows Analysts to customize SLAs to their unique organization's needs -Offers a quick and easy way to apply a specific SLA to a ticket by just adding that SLAs tag Who would benefit? Analysts How should it work? On the page https://web.tikit.ai/settings/sla , open an SLA, then go to "Ticket Criteria". An analyst should be able to select "Tag" from the "Property" dropdown menu. The "Operator" menu should be the same as the other operators. The "Value" menu should be a picker input box that pulls from the current list of tags. If a tag is not present you should get the same option to add the tag as you would when entering a new tag in a ticket.

The ability to rearrange and to delete templates and lifecycles would be useful with organizing, as we have many set-up and it's not as simple to take inventory of them all. Archiving is good, however, the ability to delete them would be helpful.

Currently one has to save a screenshot as file before uploading.