Tikit not only builds on Teams, but Microsoft's Adaptive Card Designer framework to support customizations so you can:

• Apply Templates with Custom Forms
• Have Tikit Virtual Agent respond with those very same forms to gather input at ticket creation
• Build Custom Forms using the Microsoft Adaptive Card Designer

And up until this point, we've rendered that exact Microsoft experience throughout Tikit. But today, we're taking the Adaptive Cards Designer even further to give you even more flexibility, more customization, and all within an experience you already know.

New Options in Adaptive Card Designer

Today's update introduces all Ticket Properties, some Ticket Extras, and a new Input (People Picker) when designing Custom Forms.

So if you're looking to:

• Let an End User pick other Affected Users when submitting a ticket
• Set a Category or Tags on ticket creation
• Let an End User upload Attachments on initial ticket submission
• Remove the "Status of My Requests" button from the New Ticket card
• Wholly customize the default New Ticket card
• Give fields entirely different names
• Dynamically control the Request with variables

YOU CAN!

Inputs

Let's start with one of the first items you can bring into a form, which is a request we've heard from several customers - "I really want to be able to provide a People Picker."

Just like you'd expect, this control can be drag and dropped directly into a form. Like other controls, this can be renamed to something else, set to optional or required, and most importantly define whether or not to accept one or many selections. With the People Picker control, regardless of the people chosen - the selection does not map to any underlying ticket property. But the selection is available on the form, and thus able to be used inside of Excel, Power BI, and of course Power Automate.

Ticket Properties, Variables, and The Default Template

But controlling things like the Status, Tags, and Adding Attachments have a much more tangible impact to tickets being worked. Once placed on a form, the underlying ticket property will shift accordingly. Whether you are applying the Template yourself or it's being served via Deflection. Bringing Ticket Properties to forms allows End Users and Agents to directly control those properties before (and even after) the ticket is submitted.

Default Template: Requester Create Ticket

To help explain how these properties and variables are used. Today we're also addressing another long standing request, which is the ability to edit the New Ticket card.

Now, whenever you say "new ticket" to Tikit Virtual Agent or there is no Deflection to serve, the card above will be presented. While this Template shows "Created By Tikit", it can be modified as little or as much as you'd like and no less with all of the functionality in this update.

Recreating the Email Experience in Teams

Continuing along the "New Ticket" experience, lets explore some more customization arriving with this improvement.

As you're no doubt aware in Tikit's email connector:

• the Subject becomes the Request
• the Body becomes the first comment on a ticket

With today's update, you can now optionally build that experience to be served by Tikit Virtual Agent. Best of all, this could be your Default New Ticket template, a new process you want to create for Deflection, or both.

In the above, we're using the:

• Request property (renamed to Summary)
• Add Comment (renamed to Detailed Explanation)

You'll notice that with regards to Add Comment, you can optionally enable support for Internal Notes. Perfect when you're making forms just for Agents. But in regards to the Request field, we have just a few more options to explore:

Apart from being able to rename the field, you can also perform three additional actions with the Request field:

• declare if the field is Initially Visible to the person filling the form out
• process variables from the Teams Conversation and/or the Card itself
• declare the contents of the request for the End User. Wait. What?

Ticket Variables and Form Variables

Historically when chatting with Tikit Virtual Agent, when no Knowledge can be served the message sent to TVA auto-fills out the Request portion of the card.

Since it's now a variable you could hardcode some text in front of {{message}}, after it, or remove it entirely.

But where this might make the most sense is for example an Onboarding Request. You could:

• remove {{message}}

• uncheck Initially Visible

• modify an existing Template to use the Id of other inputs on the form to control the Request without having to use Power Automate to update it.

Let's take a look at the following example with a few fields that will drive the Request instead of the {{message}}.

First Name = firstName

Using {{firstName}} and {{lastName}} in the Request

Ticket has been submitted and Request set per configuration above

This grants total flexibility over the message that triggered the TVA response, the Request, and if the chosen fields are even shown initially to the user filling the form out.

Default Template: Multi-Department Picker

Since the default Template can be modified to include a Team picker, we're removing the following setting from Bot Configuration.

But don't worry! Whether or not you had it enabled or disabled - we've migrated that experience into your respective Default Template for you.

Add Attachment, Collaborators, and Assignment

There are a few of other controls here in this update that are a bit more unique but still remain straightforward in their use.

Add Attachment

One of our biggest requests has the ability to enable support for uploading files on initial ticket creation. By simply dragging the "Add Attachment" control into your form that's exactly what you get.

Collaborators

If you're looking to define who else should be assigned to a ticket, you can drag the Collaborators control out onto a form. This control features two presentation choices, Lookup which is the default behavior seen below.

Or alternatively, List. In this case, all of the Agents are listed out and can be checked off on the form.

Which presentation layout you choose above ultimately depends on your preference.

• If you only have a few agents, List might make more sense as there is a small list of Agents to choose from.
• If you have tens or hundreds of Agents or are heavily leveraging Multi-Department scenarios with Tikit, Lookup will help keep your form tidy

But no matter what, the choice is yours as to how you want to present Collaborators.

Assignment

We're also introducing support for a unified control that helps you scope the assignment of a ticket.

With the Assignment control, you can narrow down the list of potential Assignee's on a form based on their Team/Group. In this case, you could imagine a scenario where Change Requests for IT should only allow IT based Assignment.

Data Sources

We're also addressing another request with this release and it's the ability to customize the choices a Requester has when filling out a form. Specifically:

• What if on Multi-Department picker, you only want to show 3 of your 7 Teams?
• What if you want the Requester to pick from 5 of your 40 Categories?
• What if you want the Requester to pick from 7 of your 100 Tags that are "locations"?

With Data Sources, we're giving you more ways to present what exists in your environment to Requesters without oversharing on a Template by Template basis. Best of all, Data Sources are configured globally. So you can create, edit, and delete Data Sources as you see fit. Data Sources are applicable to all pickers you use in Tikit today. Teams, Groups, Tags, Categories, and so on.

Take the following example, where we've created a Data Source to show a trimmed down selection of Teams but only for the Default New Ticket experience. In this case, we want our users to experience the Multi-Department Picker, but we only want to show a subset of Teams for them to be able to create tickets for.

The Agent Experience

But after all is said and done and your forms are configured/submitted by your fellow employees.

• What happens on the Agent side?

• What if you're using a Template that sets the Category but the person filling out the form can pick the Category?
• What if you want to alter the answers that control ticket properties after the ticket has been created?

Let's change some answers on the form and click on "Update Answers"

In this case, you are still allowed to change answers however it will shift the underlying ticket properties where applicable. As you'd expect, this change is audited in full.

That's all for now!

It feels like just yesterday Resolution Note went out, and now today - Adaptive Card Designer enhancements are live! We hope you are as excited as we are for this release, and can't wait to see the kinds of things you build with it.

As we covered the other day on Technically Speaking, we've got a few more items on their way after this. Talk soon!

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!

First thing tomorrow you'll be able to take advantage of all new functionality arriving for Lifecycles, Approvals, Tasks, and Transitions. All alongside even more ways to empower Super Agents within the organization. LET'S GO!

Approvals

Whether it's in a Lifecycle or added on the fly to a ticket, Super Agents and Admins can now edit an Approval. This is great because if someone is out of the office now you can flip approvers. Best of all, all changes to Approvals are audited within the ticket itself.

Tasks

Let's just get right to it. Not only can you now assign Teams and Groups to a Task. But you can also assign Collaborators as well!

Plus, we're introducing an additional Status of "Skipped" to Tasks. This new Status functions identical to Completed but introduces a new way to mark Tasks and of course report on them.

This Status is more relevant than ever within Lifecycles as the "Use Default Logic" Transition respects Skipped in addition to Complete as a means to progress a Lifecycle forward.

These new fields on Tasks can also be seen within My Work and My Group Work views!

Lifecycle - Manual Transitions

Since we introduced Lifecycles, Logic Builder provided a way to define how to move forward, backward, or wherever you'd like within a Ticket's active Lifecycle. What's more, the optional "Reason" field provides a way to show why you are returning to a specific Phase of work.

But up until now, you've always had to respect the rules as defined within the Lifecycle. You're either always moving forward through Phases of work or you've moving elsewhere when some condition is met.

But now Super Agents and Admins can now manually transition into any Phase of work using that same Reason field. This change is audited against the ticket so it's clear as to where you've come from, and why you've transitioned to a particular phase.

But if you're looking closely above, you might notice something else. Also available is the ability to add Tasks and Approvals on the fly into a Ticket with an active Lifecycle!

Automations

And all of these changes come with updates to Automations!

Power BI/Excel updates

Also worth mentioning that a simple refresh (manual or scheduled) of your Power BI or Excel templates will automatically introduce these data points on those respective queries. We'll have another update of the these reporting templates shortly to include new dashboards.

Also available if you missed it are several new date fields that are automatically getting set for you directly on Tickets. They are:

• First Assignment Date

• First Private Agent Comment

• First Agent Comment

• First Requester Comment

Again, all it takes is a simple refresh of your dashboards to unlock these new data points for you to report on.

Technically Speaking for December

We're also moving Technically Speaking up to this Friday the 20th. We'll go over these features and what's next. See you there!

Interested in experimenting with how your KB could respond to different prompts? With Chat Studio, we're giving Knowledge Agents more ways to further tune Knowledge thresholds. Let's dive in!

Chat Studio

Up until this point, tuning your Knowledge Base has always involved some back and forth between editing the Knowledge Base and testing those responses out with Tikit Virtual Agent. While recent improvements to the Knowledge Base, introduced support for KB Status, Agent Only responses, and OpenAI on Azure. There still wasn't a good way to experience everything the KB had to offer in a test environment.

Now featured alongside where you configure Knowledge Articles and Synonyms. Chat Studio gives you the ability to test out responses without having to interact with Tikit Virtual Agent. Best of all, you can control what responses are returned. Such as:

• including Draft and In Review articles
• including Agent only articles
• including Azure OpenAI results
• including the deflection score of the returned response
• how many responses are returned to simulate multi-response
• setting a unique scoring threshold for Chat Studio

We'll cover this and more on Technically Speaking, this Friday September 27th!

As the title of this announcement might imply, there are just a few things arriving with this release of Tikit. We're excited to get into the details about all of them, so no use in waiting, let's talk features!

@Mention

Let's start with one of our highest requested features, @Mentions. With @Mentions, we're giving Agents the ability to call other agents out from a comment within a ticket.

Once sent, we're letting Tikit Automations take over with a new out of box automation called @Mentions.

Within this Automation that is enabled by default, you're free to customize just like you are today how that notification is sent. By default, we'll:

• send to Teams and Email
• use the Generic Ticket Card
• let you you enable/disable the automation
• let you customize the notification in full
• let you use @Mention-ed users as properties within Automations
• leave the Message blank as Generic Ticket Card will handle all of the details

Once mentioned, Agents will receive notifications from Tikit and Teams will even distinctly color the mention as well.

Agent Only Templates

With our last release focused around KB Improvements, we introduced support for Agent only KB Articles. What's more, Agents could now retrieve knowledge just like the rest of the organization through TVA.

But what about Agent Only Templates? Forms that are linked to agent specific processes and Lifecycles? This release continues to extend Tikit Virtual Agent's capabilities providing Agents access to Templates that only will be seen by them!

• Someone needs access to a server? Azure resource?

• Add an employee to a private Team?

• Perform a one time virus scan against a computer?

Templates and Lifecycles created for by Agents, for Agents, can now be served through TVA!

Email Improvements - Minimum file size for Attachments

When it comes to working tickets generated from email, something we've seen is that signature graphics aren't technically attachments. Well. They are, but they are certainly less important file attachments when working a ticket.

If you're an agent, you might be deleting irrelevant attachments or performing some quick visual filtering to recognize the real attachment you're looking for. With our latest update to Tikit, we're giving you functionality to prevent files from being attached that do not meet a specific file size.

We've set this at 25kb for you, which should handle most scenarios. But as always, it can be tuned up, tuned down, or completely disabled by setting the value to 0. Now anytime an email is sent, each attachment's file size will be compared before attaching the file.

Knowledge Base and Template Links

When you’re talking about an issue or request with someone, you might already know the exact Template or Knowledge Article that would help them out. Rather than have them message Tikit Virtual Agent, it’d be even easier to just send them exactly what they need. That’s why “Get Link” is an option now available on Knowledge Articles and Templates!

Improved Agent Commenting experience

A small change, but a change none the less arriving with this release is how private comments are handled. Previously, the experience to leave a private comment required you to check a box and then send the comment.

But now you'll be able to do this with one less step. Now when leaving a comment, you'll have the option to Send as you always have in which case the Requester/Affected Users receive the communication. But you'll now also have the option to "Add Internal Note" which immediately makes this a private comment.

But let's not forget about Attachments, let alone Private Attachments. Because something else arriving with this update is support for dragging and dropping attachments and copying and pasting from your clipboard directly into the chat experience.

Best of all, this also carries over into other attachment experiences alongside @Mentions as well!

InTune - Device Manufacturer

And last but not least, we're also bringing in a small update to the InTune connector. Now when looking at a user's Linked Devices you'll see the Manufacturer of that device.

As always, we'll cover this and more at the next Technically Speaking happening next week. Until then!

The latest round of updates for your Knowledge Base are arriving first thing this Thursday, August 15th. This update brings more intelligence, features, and performance improvements to make your Knowledge Base more flexible than ever before.

Confidence Improvements

Tikit's native artificial intelligence is improving with enhancements to KB save times and Tikit Virtual Agent request times. But that's not all! We're also improving the actual underlying AI engine used by Tikit and as such raising confidence levels to a new bar.

Whether you have chosen to predominantly use keywords or full phrases, we are moving the default confidence level to 65% for all customers.

As always, you can change and tweak this to your liking. Coupled with Multiple KB Responses, employees will continue get exactly the information they are looking for with even higher confidence levels.

Knowledge Base Layout and Status

Up until this point there was no way to draft articles, save your progress, or ensure only agents could see specific articles. What's more, who created a specific article? Who was the last person to modify it? And last, depending on the size of Knowledge Articles the layout of the page could vary.

Now you can control the Status of a KB Article by setting articles to Draft, In Review, or Active. Additionally, you can mark articles as Agent Only to keep knowledge a bit more siloed. How is this all experienced?

With Tikit Virtual Agent, only Active Knowledge Articles will be returned to the employee interacting with Tikit Virtual Agent. But if that employee happens to be an Agent, they will also receive Active, Agent Only articles as well. Now Agents can experience Tikit Virtual Agent like the rest of the organization!

Integration with OpenAI on Azure

You can now you can integrate OpenAI on Microsoft Azure to ensure privacy and security. All uploaded documentation stays with you, within your Azure tenant, and only visible to your organization. Best of all, every single Knowledge Article you have configured up until this point is respected entirely.

After you've configured, interacting with Tikit Virtual Agent will continue to work as you've come to expect. Ask it questions and it will search your configured Knowledge Base for answers or Templates.

But if Tikit Virtual Agent cannot find anything in your Knowledge Base. It will then look to OpenAI in your Azure Tenant for any documentation you have uploaded to then provided a generative AI based response. In addition, you can enable use of citations to see just exactly how the response was created.

We believe this strikes the correct balance between the articles you've created for Tikit's Knowledge Base and the power of generative AI. Best of all, using generative based responses allows you further close the loop on additional phrases or even answers, to make available in Tikit's Knowledge Base.

Wrapping up

We've still got even more updates planned for the Knowledge Base and other highly requested roadmap item features in active development. That's all for now. Don't forget everything above is arriving this Thursday, August 15th!

Tikit has always been available globally. But today, our signup experience now includes the ability to provision closest to where you work to offer the best possible performance.

When signing up, just tell us where your team is located and we'll handle all of the work of getting things setup closest to you.

But to all of our current customers who might want to shift where their Tikit instance and data are stored. Migrations have already taken place for Germany, Asia, and Australian regions. No work necessary on your part!

We'll go over this at Technically Speaking later this week. See you there!

Tikit Virtual Agent has grown up quite a bit since it first launched. In that time you've been able to customize it's branding, iconography, train up its artificial intelligence to deflect tickets or provide Templates, return multiple responses, and today - customize the very first experience available to users across the organization with support for customizing the Help card.

Updates to Bot Configuration

Here you can customize and style the text as you see fit, but more importantly introduce buttons directly into the Help card.

If we were to restyle a few things, we could build out a help card that offers access to common requests without knowing how to ask for them. Best of all, we can introduce a mix of different kinds of buttons.

With the Add Button menu, you can add in:

• Knowledge Articles: No need to ask, just push the button to get the answer as configured for the chosen KB article

• New Ticket: Need a quick way to get a ticket opened for a specific Team?

• My Requests: Need to check in on your open requests?

• Template: Need to jump right into a specific request?

• Open URL: Need to go somewhere else like an internal company website? Perhaps a Microsoft Form?

Regardless of your choice, you have the ability to customize the text that appears in the button. Edit the button afterwards by clicking on it, or deleting it by hovering and clicking the red trash can. You'll also notice all buttons are given iconography to provide the context of what they do.

With our card built out, lets test it out inside in Teams with Tikit Virtual Agent. We'll use the "help" command, send the message, and we'll see our new updated card. Then we'll choose "Wifi password"

What's worth pointing out here is just like Multi-KB response, when you select a Knowledge Article. You will always see the first question that you've configured for a specific Knowledge Article. That way employees have a quick way to find what they are after next time should they choose to converse.

New Ticket

But there is one more item available with this update and that is the ability to move directly into ticket creation by either using the "New Ticket" button, or just saying "New Ticket" to Tikit Virtual Agent.

With all of that said, let's combine everything above into a brand new help card that enables employees across the organization quick access to common Templates and Knowledge Articles.

Now you can customize, style, and provide a host of service offerings from different Teams using Tikit!

Wrapping up

We're excited to get this feature out and look forward to seeing what you build with it. If you have something you want to share, make sure to bring it to Technically Speaking at the end of the month!

As your Knowledge Base grows, dialing in confidence levels and figuring out how to phrase what your fellow employees could be asking could become increasingly challenging. With the latest updates to Tikit, we're making Tikit Virtual Agent even more flexible and configurable than before.

Updates to Bot Configuration

Apart from the minimum confidence to return an answer, you can now additionally configure:

• The number of responses to return

• Whether or not to return a single response IF the most confident response is greater than the configured threshold

• The message delivered on the Multiple Responses Card
• The Create Ticket Message when a response couldn't be determined

With our settings configured, let's see what this new experience is like as there are several things happening:

1. When interacting with Tikit Virtual Agent, you'll receive several responses from your Knowledge Base that are a mix of Articles and Templates you've configured
2. Knowledge Articles will always show a brief summary of their content. Whereas Templates will show their Title and Description
3. If none of the responses look like what you're after, you can move straight into ticket creation which respects Multi-Department picker if you've toggled it on by selecting "No, create a ticket"

But what about interacting with the results? Clicking into any result will show the first response that you've configured for a specific Knowledge Article. That way employees have a quick way to find what they are after next time.

But if you're looking closely, there is also updated functionality around the Templates returned. As you can now back out of a specific Template and go straight into ticket creation that once again continues to respect Multi-Department picker functionality.

That's all for now

This has been a long standing request we're excited to finally be able to deliver. We'll be back soon with even more updates to Tikit Virtual Agent!

Since the launch of Tikit, we've done everything we can to ensure agents and requesters always stay in the loop of communication. But with that has come a host of genuine needs from all of our customers to customize those experiences.

Whether you want to turn off notifications when the Status changes, customize your own notifications from TVA, have even more fields to use within Automations, or have the opportunity to Apply a Template from Automations. Today those items and more are now available! So...

Some light re-arranging of Settings

The first thing ITSM customers will notice with Notification Center is that Email Connector settings continue to move into Teams centric configurations. Here's a quick before and after:

5.20.2024 and before:

5.21.2024 and after:

As you can see, Notification Center takes over by providing some of that Email Connector customization that you had before + offering the ability to disable several out of box notifications to Requesters whether it it be via Teams or Email.

While cutting down on some notifications is great, it's also possible you're here disabling the out of box notifications because you're looking to build your own and further customize Tikit to your organization's needs. So let's head over to Automations next to check out the new items that have arrived there.

Updates to Automations - Entities

Tikit offers an automation engine to drive everything from simple to complex workflows. With updates to Notification Center we're giving you more entities and more actions.

Previously you've had access to Tickets, Approvals and SLAs. We're now extending this list further to include Tasks and Lifecycles.

Tasks

With support for Tasks, you can not only perform automations centered around them. But key off of their respective properties such as the Assignee, Status, Title, or even the Phase of Work they might be included in.

Lifecycles

With support for Lifecycles, you can now build automations that key off of a Lifecycle's properties such its Title, Phase Name (so you could capture Phases across different Lifecycles), Active Phase (is a specific Phase the Active one), and finally the Status of the Lifecycle.

Tickets

And you can also now filter on the Template of a Ticket.

Updates to Automations - Action Types

We're also introducing even more flexibility to Actions with the introduction of Apply Template and Notification Center.

Apply Template

When a Ticket meets a certain criteria, a specific comment is left, or anything else you wire up within Automations occurs - Apply Template. With this action, even applying a Template can become an automated process within your organization for agents or requesters.

Notification Center

And now we can come full circle with Notification Center. The ability not just to send email in response to an Automation. But the ability to send a Teams notification as Tikit or Tikit Virtual Agent based on the role of the user within a ticket.

The first thing you'll notice after enabling a Teams notification, is the choice to pick who the message should go to. Based on your selection either Tikit, Tikit Virtual Agent, or both will become enabled offering you the ability to edit and style the message to your liking.

Messages to:

• Assignee
• Group
• Team
• Task Assignee
• Collaborators

will always come from Tikit.

Whereas messages to:

• Requester
• Approvers
• Affected Users
• Selected Users

will always come from Tikit Virtual Agent.

Best of all, customizing either experience is the same and offers support for variables within the message.

What's more, we're letting you choose the styling of the cards that go out. Just click on "Selected Card:" to see your options AND preview your changes.

Simple Card

Generic Ticket Card

Edit Ticket Card

Finally, you'll notice one last checkbox after you've made your selection - "Update Message/Card." Checking this off results in notifications about a single ticket to remain a single notification that always appears as the most recent conversation from Tikit/Tikit Virtual Agent. You'll still receive notifications in Teams about the update, except with this checkbox you can ensure there will only ever be a single notification about a given ticket.

Wrapping Up

There is no doubt, a LOT happening in this update. We're excited to get this shipped and can't wait to see the kinds of notifications you'll build with it. We'll go over Notification Center and what else is coming down the pipe at our next Technically Speaking happening next week on May 31st.