# Bi-Weekly Product Release Notes - Feb 12, 2025

## Features

The following features have been added to the Aisera GenAI Platform in this release.

### Channels <a href="#heading-h.pnsne3pe4d39" id="heading-h.pnsne3pe4d39"></a>

The following features have been added to **Aisera Channels** in this release.

#### Copilot Channel Can Access Documents and Templates <a href="#heading-h.3fsflm68yvbd" id="heading-h.3fsflm68yvbd"></a>

You can now access documents and templates from the Aisera Copilot channel.

**To access Documents and Templates:**

1. Navigate to **Settings > Channels** in the Aisera UI.
2. Choose an existing Copilot channel.
3. Click the **pencil icon** at the top right in the Channel Details page.<br>

   <div align="left"><img src="/files/gZjt6t9zhdh4DQSOb2aU" alt="Edit Channel to Enable File Handling" width="375"></div>
4. Select the checkbox next to **Enable File Handling**.
5. Click **OK.**
6. Double-click the Channel URL at the bottom of the **Channel Details** window to open your Copilot bot.

![AI Copilot with Libraries Expanded](/files/n4n0MneNgZY0KAvWP4hK)

Now you can see the **Document Library** on the left side of the window, and if you hover over the **Account icon** at the right-top of the window, you will see the **Template Library** option.

<div align="left"><img src="/files/GHantT3HyP26Y9MAzXa9" alt="Copilot Document Options" width="563"></div>

Either of these options allows you to upload a file.

#### Webchat Supports Notification History <a href="#heading-h.826dz6a2do3u" id="heading-h.826dz6a2do3u"></a>

You can now see a history of notifications that occurred when you don’t have the Webchat bot open. For instance, if you received notifications from an email campaign when you weren’t interacting with the bot.

**To turn on the Notification History for your bot:**

1. Navigate to Settings > AiseraGPT in your Aisera Admin UI.
2. Choose the bot you want to modify.
3. In the Channels section of your bot **Details** window, double-click your Webchat bot.
4. Choose the **pencil icon** in the upper right corner of your **Channel Details** window.
5. Check the box next to **Enable Notification Service** in the Edit Channels window.

<div align="left"><img src="/files/nwDprCaePoawd0dm2r0a" alt="Enable Notification Service" width="563"></div>

Now your bot will have a **bell icon** in the upper right corner.

\
![](/files/Qp7EfEuK50pzJ5svT2JZ)

Choose the **bell icon** to see a list of your Notifications.

If you’re responding to a Campaign notification, you can now choose and respond to the notifications that you missed.

![Campaign Messages in Webchat](/files/cebIGa8xfXoMFcEOVwjg)

### Ticket Concierge <a href="#heading-h.tait8serg74k" id="heading-h.tait8serg74k"></a>

The following feature has been added to **Ticket Concierge** in this release.

#### Using Event Studio for Ticket Concierge <a href="#heading-h.liegl8vizjn9" id="heading-h.liegl8vizjn9"></a>

Ticket Concierge is a feature that looks at all the tickets that are already created in the external system and dispatches a tailored solution to the user.

With this release, there is a new Event Studio Handler that works specifically with the Ticket Concierge feature. If you are using a previous Ticket Concierge setup, it will continue to work and is still supported.

Before you begin, make sure that you have integrated a data source, ingested ticket data, and created an Aisera application or bot.

**To set up Ticket Concierge with Event Studio:**

1. Navigate to **AI Automation > Event Studio**
2. Choose **+ New Event Trigger** in the upper right corner.
3. Select the **Ticket Concierge** option in the New Event Trigger window.

<div align="left"><img src="/files/lpOSl0zzhrtXQliKHHLC" alt="" width="563"></div>

Choose Ticket Concierge as Event Handler Type

1. Choose your Ticket Type from the pull-down menu. In this example, the **Ticket Type** is Zendesk.
2. Click **OK**.
3. Choose the **Ticket Type** again from the pull-down list in the next window. This Data Type (Ticket Type) contains the mapped fields for your data source with Ticket Concierge).
4. Select **RecordCreated** as the Event Type.<br>

   <div align="left"><img src="/files/oL1EwC3xwoOghX5CL9fa" alt="Triggering Condition" width="375"></div>
5. Define triggering conditions for the tickets you want to process. In this example, tickets with **IT Help** in the subject and a **Ticket Reporter Email** that is not **<Automation@aisera.com>** will proceed, while those created by **<Automation@aisera.com>** will be excluded.<br>

   <div align="left"><img src="/files/YJXT4nfH4T1l9p5O9JzU" alt="AI Ticket Fields" width="375"></div>

To process a ticket, three mandatory Aisera fields—**ticket\_id**, **ticket\_url,**, and **ticket\_reporter\_email**—must be mapped to the corresponding fields from your ingested data source.

![](/files/5siQGTU7sQVFyPAtAVNx)<br>

6. Select the **Prehandling Flow** and **Ticket Action** flow that you want to associate with Ticket Concierge.

* **Prehandling Flow:** Flow invoked prior to processing a ticket.
  * **Use Case:** If you want to enable ticket concierge even when the reporter email address is private.
* **Ticket Action Flow:** Flow involved if the fulfillment is found but before sending out the fulfillment to the end user.
  * **Use Case:** If the users wants to initiate a workflow to update certain ticket fields via API.

7. Check the **Use Custom NLU Policy** check box if you want to define a custom fulfillment for Ticket Concierge. You can drag the policy to select the priority order. If unselected, the event will use the same NLU policy as the application/bot.
8. Select the ticket fields you want to include to extract intents from the user Request. Previously, we were able to extract only **Title** and **Description**, but now you can include custom fields as part of the intent extraction.

<div align="left"><figure><img src="/files/FjTVLi5mICl0j9pWGYO9" alt="" width="563"><figcaption><p>Trigger in Event Studio</p></figcaption></figure></div>

9. Click **OK** to complete the Ticket Concierge setup in the Aisera Admin UI.

If you click on the Trigger link for your new Event Trigger, you will see the **Details** for your Trigger.

![Data Type View in Event Studio](/files/PsYbA5KrF3rhPR4gwZ3m)

If you click on the **Data Type** link for this Trigger, you will see a list of the mapped fields for Ticket Concierge in this Data Type.

![Mapped Fields](/files/0lot2NEUpBEvaL5gF5jL)

10. Create an Event Trigger for your Data Source to complete this setup.

![](/files/2cmnujZLyQV3Zh7bzhLW)

11. Ask your Data Source Administrator to use the tokens from your Data Source (shown in your App Details window) to create a webhook on your Data Source system. Each Data Source system has their own webhook creation instructions.

## Enhancements <a href="#heading-h.hcta1tv4lday" id="heading-h.hcta1tv4lday"></a>

The following enhancements have been added to the Aisera GenAI Platform in this release.

### Channels <a href="#heading-h.rwg5yf14enks" id="heading-h.rwg5yf14enks"></a>

The following enhancements have been added to **Channels** in this release.

#### Webchat Supports Customized Auth Message <a href="#heading-h.apt8xt80qmfu" id="heading-h.apt8xt80qmfu"></a>

You can now customize the message that users will see if they have a failure during an SSO login to your bot.

**To customize the SSO Failure Message**:

1. Navigate to **Settings > AiseraGPT** and choose your bot.
2. In the **Channels** section of the Application **Details** screen, double-click on the Webchat Channel where you want to modify the message.
3. Choose the **Authorization** tab in the **Edit Channel** window.
4. Select the **SSO-SAML** radio button.

![](/files/8rhYC6kW2zQ2Zi54GqSU)

5. Add your custom message.
6. Click the **OK** button.

#### Notification Messages for Aisera Copilot <a href="#heading-h.als6tqj5300t" id="heading-h.als6tqj5300t"></a>

You can now set notification preferences in the Aisera Copilot channel.

1. Click on the bell icon in the upper right corner of your Copilot bot.

<div align="left"><img src="/files/GAiwAqeVnyi215AL1RXI" alt="" width="563"></div>

2. Select **All**, **Read**, or **Unread** Notifications.

<div align="left"><img src="/files/jP2wPuWLNV6ap6TP6cx6" alt="" width="563"></div>

3. Select Notification for **All**, or for the last **5**, **10**, **30**, or **50** days.

**To set your notification options:**

1. Click the **bell icon** in the upper-right side of your Copilot window.
2. Set the **Status** option for the notifications you want to view.
3. Set the **Date** field with the timeframe for the notifications you want to view.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.aisera.com/product-release-notes/2025/bi-weekly-product-release-notes-feb-12-2025.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
