Resolution Note
Resolution Note is now available! This feature brings several changes across all of Tikit spanning the Agent Portal (Tickets, Knowledge, Automations, Lifecycles, Views, and Knowledge) Teams one on one chat, and finally Teams Channels.
From the outset, it's worth highlighting for all of our current customers this experience is opt-in. Given this experience alters how tickets are resolved, we want to make ensure the decision is in your hands as to when to enable this.
With that out of the way, let's get into it!
Updated Settings

With the introduction of Resolution Note, we've re-arranged a few things in the Settings area. Items are grouped a bit differently, but what you'll see above is that Tikit Configuration now contains the settings for Resolution Note and Surveys.
Once enabled, you can choose which parts of Resolution Note are required or optional. In the case of Draft KB, whether or not the option is visible. These are important distinctions to highlight because once Resolution Note is enabled. The Resolution Category, Resolution Note, and Resolution Note (Internal) will always be visible when resolving a ticket but they are required/optional based on the above. Whereas Draft KB controls visibility.
But the first item to configure here - Resolution Category - is a wholly new concept. What is a Resolution Category?
Resolution Category

With Resolution Categories, we're giving you a way to further classify tickets based on their resolution. In this way, a new reporting metric becomes available.
- How many Priority 1 tickets were self-resolved by the Requester? Resolved by an Agent?
- How many tickets with a Category of Networking, assigned to the Support Team, were resolved by an Agent? Automation?
- How many Tickets were self-resolved by a Lifecycle?
- How many Tickets resolved at a minimum of 3 days do not have an Internal Resolution Note?
But lets see this in action, how does this experience manifest itself across Teams and the Agent Portal?
Resolving a Ticket in the Agent Portal

With Resolution Note enabled, once you're ready to resolve a ticket by changing the Status to Resolved and clicking Save. The above popup appears asking for details on how the ticket was resolved. If you're looking closely, you'll see the fields made required vs. optional map to the Resolution Note configuration earlier.
It's also worth highlighting that Resolution Notes will go out to the Requester upon resolution of the ticket. Whereas Internal Resolution Notes, are more akin to private comments. The requester will never see them. So they are great for more technical breakdowns.
But what about Resolution Category? After all - it had a default value. So why is it blank instead of populated with "Resolved by Agent"? The reason is because if the field is required, an Agent must choose the Resolution Category. If the field is made optional, it will auto-populate as seen below.

With a Ticket Resolved, you'll also be moved into a new experience within a ticket on the Resolution Details tab. So long as the ticket is Resolved these fields can be edited.

That's the resolution experience in the Agent portal. But what about Teams?
Resolving a Ticket in Teams

If you're in a one on one chat with Tikit, just like before you can modify a ticket and resolve it. But upon doing so with Resolution Note enabled. You'll get a reply back from Tikit asking for more details.

Until this form is submitted, the ticket will remain in its current Status whether it be Active, Pending, etc. but it remains in this state within your one on one chat with Tikit.
When it comes to working within a Team and specifically one of its Channels (Tikit Groups) you'll have a very similar experience, but certainly geared toward the Team concept.
Resolving a Ticket within a Team's Channel
When resolving a ticket within the context of a Team as seen below:

Tikit will reply within the thread of the ticket prompting for a Resolution Note. However in this case, all members of the Team have access to it.

This means anyone has the ability to set the resolution or Cancel the resolution. In which case, you'll see who performed this action:

Closing the Loop on Knowledge Base Deflections
But in all of the above, Draft KB is a piece of functionality that anyone with the Knowledge Agent role can take advantage of. In this way, when a ticket is resolved:
- A Knowledge Article will be created
- It will be in Draft Status
- It will be Agent only
- The first phrase is the Request, the response is what was provided in the Resolution Note
Let's check it out!

Like any other Knowledge Base article, it can edited, switched to a Template, made available to all users or just agents.
Ticket Lifecycles
With changes arriving for how tickets are resolved, what happens for Tickets that controlled by Lifecycles?

With Lifecycles, we're bringing Resolution Note directly into the Lifecycle's configuration. Allowing you to set values and ensure consistency in your ticket resolutions. Best of all, these fields respect notifications so when the ticket resolved - notifications go out. If something didn't work out the way you were expecting, because the ticket is in a Resolved Status. Agents can access the Resolution Details tab and provide further commentary on tickets Resolved by a Lifecycle.
And don't forget - with Power BI or Excel, you could then report on Tickets with Lifecycles whose Resolution Notes aren't identical.
Automations
But if you're looking to do something custom whether. Resolution Note also is available within Automations!
When

Build Automations based on when Resolutions are created on tickets
Do

Add Resolution Notes to tickets that meet a given criteria
Views
And last but not least, Resolution Note makes its way into Views giving you the ability to choose these properties as columns to view, filter on, create new Views with, and included in Export to CSV.


Wrapping up
That was a lot! As you can see, Resolution Note touches so many different aspects of Tikit. We're excited to get this feature out and looking forward to our next release that will see some radical changes to Custom Forms and Adaptive Card Designer.
Until Technically Speaking!