# Serving a conversation

When you open a conversation, the header always says who is serving it. This page covers what you do while serving. For when who serves changes, see [Serving and assist tickets](serving.md).

## Start serving

- When a customer is waiting for you, just write in the reply box. The button reads **Start serving & send**, and sending starts serving.
- Otherwise, hold **Start serving** or **Transfer to me** in the header; letting go early does nothing.
- The moment you start serving, any reply Ailo has not sent is cancelled.

## Replies and notes

Above the reply box you choose **Reply** or **Note**, and **Orbit** when Orbit is available.

- **Reply** goes to the customer. Only whoever is serving can reply to the customer.
- **Note** is an internal note. Only the team sees it; the customer never does. You can write notes even when you are not serving.
- **Orbit** sends what you write to Orbit, the members' AI assistant, not to the customer; see [Orbit](orbit.md).

## Transfers

Whoever is serving can transfer from **⋯** (More actions) in the header:

- **Transfer to a teammate…** lists online teammates and how many conversations each has, and you can add a note that only the team sees. Until they start serving, you are still serving and can **Cancel transfer**.
- **Transfer to Ailo** hands the conversation back to Ailo; the customer sees "{name} transferred you to Ailo".

When no other teammate is online, Transfer to a teammate… is unavailable.

## Recalling a message

Hold **Recall** on a message to take back one you sent in the web widget, within 5 minutes. The message disappears from the customer's widget; Desk still shows it as Recalled, so the team can see what was taken back.

## Ending a conversation and its outcome

**⋯** in the header also has **End conversation**, with two choices:

- **End · customer can continue**: if the customer writes again, this conversation reopens.
- **End · next visit starts new**: the customer's next visit starts a new conversation.

You cannot end a conversation while it has an assist ticket that is not done, or a transfer waiting for a teammate to start serving; the message names each of them. With a transfer, it also offers what you can do now: **Start serving** (Ailo's unsent drafts are discarded and the transfer ends), or **End · next visit starts new** (the transfer is withdrawn). If only an "Ailo asks you" is left pending, you are asked whether to discard it and end.

Every ended conversation has an outcome: **Done**, **Answered**, **Unresolved** or **No action needed**. The outcome is worked out from what happened in the conversation. When it is wrong, use **Correct outcome** and pick a reason: Wrong guess, Customer came back, Spam or test, or Other. Conversations corrected to Spam or test no longer invite the customer to rate.

## The side panel

The panel on the right has three tabs:

- **Orbit**: members' AI assistant, which reads this conversation and drafts replies.
- **Progress**: this conversation's assist tickets and transfers, with waiting times and a timeline.
- **Customer**: the customer profile, with channel, language, identity, rating and the last few past conversations. It shows only what the system actually has.

## First-reply reminders

If you start serving and do not reply to the customer:

- after 3 minutes you get a reminder: "You started serving {contact} {minutes} min ago and haven't replied yet."
- after 5 minutes, online teammates get one.

A reminder never takes the conversation away from you. Time counts from when you start serving; an admin can change both times, or turn the reminder off, under **First-reply reminder** in **Settings › Business hours**.

## Conversation states

| State | When |
| --- | --- |
| Ongoing | The conversation is active |
| Inactive | No new message for a while, 10 minutes by default |
| Resolved | A while after becoming inactive, 30 minutes by default; if the customer comes back within the reopen window (72 hours by default), the conversation reopens |
| Closed | Past the reopen window; the customer's next visit starts a new conversation |

A conversation with an assist ticket that is not done is never resolved automatically. An admin can change all three times in **Settings › Conversation timing**.

## Related

- [My queue and all conversations](queue.md)
- [Working on assist tickets](tickets.md)
