# Desk overview

Desk is ailodesk's support product. Customers start a conversation from the chat widget on your website, and Ailo and your teammates serve it from the same workspace. Ailo answers what it can. When part of a request needs a human decision, it becomes an assist ticket for a teammate, and the customer sees real progress.

## Organizations, sites and channels

| Level | What it is | Example |
| --- | --- | --- |
| Organization | The company that uses ailodesk; members and roles live here | A company that runs several brands |
| Site | One brand in one market | One brand's Thailand site |
| Channel | A way customers reach you | The web widget |

Data, settings and logs are never visible across organizations.

## Where Ailo comes from

Ailo is built and published on the Harness platform. A newly opened Desk organization gets a Harness organization with the same name, already connected. When a Desk organization is connected to Harness, an admin picks which Ailo serves each channel in **Settings › Channels**:

- Once one is picked, new conversations on that channel are served by that Ailo from the first turn, on whichever version of it is live at the time.
- Until one is picked, or if the connection is removed or either side turns that Ailo off, conversations go to the team. Desk never switches to a different Ailo on its own.
- The handoff switch, business systems, languages and business hours still follow the Desk site's own settings.

A channel with no Ailo picked shows "No Ailo chosen" on its card; with "No Ailo for now" picked, or when Ailo is unavailable, it shows "Answered by the team". Desk has no Ailo of its own: when the connection is removed or another one is made active, the channels that used it have no Ailo chosen and go to the team, never back to a site Ailo; while a connection offers Ailos, their cards show "No Ailo chosen" until you pick again.

## Five ways a conversation is served

Each conversation has one person or agent serving it at a time. By who serves and whether there is an assist ticket, there are five cases:

| Case | What it is |
| --- | --- |
| Ailo-led | Ailo serves from the start |
| Specialist-led | A specialist serves from the start |
| Assist | Ailo opens an assist ticket, a specialist claims and resolves it; Ailo keeps serving |
| To specialist | Ailo transfers the conversation to a specialist |
| To Ailo | A specialist transfers the conversation to Ailo |

Stats count "How Specialists joined" by Assist, To specialist and Specialist-led. The rules are in [Serving and assist tickets](serving.md).

## Roles

| Role | Usually does |
| --- | --- |
| Specialist | Serves customers and works on assist tickets |
| Admin | Also manages members, channels and team rules, and reads the activity log |
| Owner | Also manages the organization itself |

Each action needs the same permission whether it comes from Desk, the CLI, Orbit or the API.

## The workspace

The left rail, top to bottom:

| Item | What it is for |
| --- | --- |
| Orbit | Members' AI assistant: reads conversations, drafts replies, acts for you |
| My queue | Conversations that need you now, and "Ailo asks you" |
| All conversations | Every conversation on the team, with search and filters |
| Assist tickets | The pool and the tickets you have claimed |
| Stats | Numbers for the team and for you |
| Settings | Personal settings, team rules and site settings |

For day-to-day work see [My queue and all conversations](queue.md), [Serving a conversation](conversation.md) and [Working on assist tickets](tickets.md).

## Related

- [Serving and assist tickets](serving.md)
- [My queue and all conversations](queue.md)
- [Authentication and conventions](api-overview.md)
