# Inno, the AI assistant (/en/businesses/inno)

Inno is the AI assistant in the Thril dashboard. Ask it how last month went, why a customer's payment failed or which hours stand empty, and it looks the answer up in your venue's data. Tell it what to create, such as a promo code or a tournament, and it drafts it on a card for you to check and confirm.

Inno runs on a large language model. It writes fluent answers fast, and it can still get things wrong. Nothing it drafts changes your venue until someone on your staff confirms it.

---

## Opening Inno [#opening-inno]

- Click **Inno** in the dashboard header, or press **⌘I** on a Mac or **Ctrl+I** on Windows.
- Open **Inno** in the side menu for the full page, with your chat list and the starter tabs **Suggested**, **Create** and **Analyse**.
- In the chat header, **Dock to sidebar** keeps Inno beside the page you work on. **Open as page** gives it the whole screen.

Other people at the venue don't see your chats in their chat list. A venue admin or a company admin or manager can read a chat that has an entry in the [audit log](/businesses/inno/memory-and-audit-log#audit-log), from that entry.

To replay the short tour of Inno, open your user menu and choose **Restart Inno tutorial**.

If the dashboard shows no **Inno** button, Inno is not on for your company. Contact [Thril support](mailto:support@thril.fi).

---

## What Inno reads [#what-inno-reads]

Inno answers from your venue's data:

- **Customers and support cases.** Reservations, payments, refunds, memberships, session cards, credits, gift cards, promo codes and the emails and notifications a customer got.
- **Numbers.** Sales, utilisation, bookings, events, memberships, marketing results, customer segments, payouts and the till.
- **Your setup.** What is missing or set up in a way that costs bookings, such as a venue page without photos.
- **The page you have open.** Open Inno on the calendar, a reservation or a customer and it knows which one you mean. On the reservations list, select rows and choose **Ask Inno about … reservations** from the selection menu.
- **Files you attach.** Screenshots, spreadsheets, PDFs and Word documents.
- **This knowledgebase.** Inno searches these pages when you ask how something works in Thril.

---

## What Inno can create and change [#what-inno-can-create-and-change]

Ask Inno to create something and it drafts it on a card in the chat. The card shows every field. Edit them there or ask Inno to change the draft, then click the card's button to save it. Inno never saves anything itself.

Inno can draft:

- Promo codes, gift cards, credit products and session cards
- Memberships
- Events, courses, leagues and tournaments. An event can repeat weekly until a date you give, and one card creates every event of the series.
- Reservations
- Resources and resource prices
- Customer lists and marketing emails. A marketing email is saved as a draft and is never sent from the chat.
- Workflows
- CrossFit programs, at venues with CrossFit

Inno can also change what you already have, except memberships, gift cards, reservations and workflows. Name the promo code, event or course, say what to change, and the card shows the change before you click **Save changes**.

Three things happen without a card:

- When you ask Inno to forget something it remembered, it deletes that entry from [memory](/businesses/inno/memory-and-audit-log#memory).
- In the workflow editor, Inno can change the workflow you have open. Nothing is saved until you save the workflow.
- The [daily brief](/businesses/inno/playbook#daily-brief) and the [Playbook](/businesses/inno/playbook) ideas only produce text.

Every card Inno drafts goes into the [audit log](/businesses/inno/memory-and-audit-log#audit-log) with the chat it came from. Everything someone confirms goes there with the person who confirmed it.

---

## Drafting replies to customers [#drafting-replies-to-customers]

In a customer chat, choose **Ask Inno to look into this case and draft a reply**. Inno reads the customer's bookings and payments and puts a reply in the message box, marked **Drafted by Inno**. Edit it and send it yourself. Inno doesn't send it.

---

## When Inno answers customers [#when-inno-answers-customers]

Inno can answer your customers' chat messages. Turn it on in Inno's settings, on the **Customer chat** tab. When Inno can't settle a matter itself, it passes the chat to your staff. The chat then shows **Inno passed this chat to you** and the reason, such as **Booking change** or **Refund or payment**.

### Cancel, refund and move requests [#cancel-refund-and-move-requests]

Inno never cancels, refunds or moves a booking by itself. When a customer asks for one of these, Inno prepares the change and passes it to your staff:

- **Cancel booking**, for an upcoming booking the customer owns
- **Refund booking**, for what the customer paid for a booking
- **Move booking**, to the time and resource the customer asked for, when it is free

Other requests, such as pausing a membership, are passed on without a prepared change. Answer those in the chat.

### Notifications [#notifications]

The bell in the dashboard header opens **Notifications** and shows how many requests wait for a decision. The notice in the customer chat links there too. Venue admins and clerks can decide.

Under **Needs your decision**, each card shows the customer, the booking and what the customer wrote:

- **Approve** makes the change, the same way as cancelling, refunding or moving the booking yourself.
- **Edit** picks the refund method before you approve. On a cancellation you can also choose **Do not refund**, and tick **Tell the customer the booking was cancelled**.
- **Open chat** opens the customer's chat.
- **Decline** leaves the booking as it is. The customer still waits for your answer in the chat.

A cancellation can't be approved once the booking has started. Refund it from the booking instead.

### Activity and the reply to the customer [#activity-and-the-reply-to-the-customer]

**Activity** lists the decisions of the last 30 days and who made them. After an approval, **Reply to customer** opens the chat with a reply in the message box that says what was done. Edit it and send it yourself.

---

## Checking Inno's work [#checking-innos-work]

The chat footer says it: **Inno can make mistakes. Check what matters.**

- **Read the card before you confirm.** Check dates, prices, VAT and who a code or email reaches. The card is what gets saved, not what Inno wrote above it.
- **Check a figure before you act on it.** Ask Inno where the number came from, or open the same report in [Statistics](/businesses/statistics).
- **Ask again when an answer looks off.** Give it the date range or resource you mean. A vague question gets a guess.
- **Don't take legal, tax or accounting advice from Inno.** It knows your Thril data and this knowledgebase, not the law.

Inno can't see what isn't in Thril. It has no access to your email, your bookkeeping software or a customer's phone call. It also doesn't know a policy you never wrote down. Add those to [memory](/businesses/inno/memory-and-audit-log#memory) as notes.

---

## Your data and the AI model [#your-data-and-the-ai-model]

To answer, Thril sends the AI model your question, what Inno looked up for it, files you attached and the venue's memory. That can include customers' names, contact details and payments.

Your chats stay in Thril, and you can come back to them. Deleting a chat removes it from your chat list. A chat behind an audit log entry stays readable there.