Build. Serve. Verify.
Build an Ailo in Harness, serve customers in Desk, and see how each conclusion was measured in Research.
Recall engine: evaluating knowledge and SOP prefetch before the first model call
Serve
01 · Desk · Conversations, assist tickets and the Desk API
Desk overview
Desk is the support product itself, where Ailo and your teammates serve customers from one workspace.
Serving and assist tickets
Who talks to the customer, when that changes, and what the customer sees while a teammate helps.
My queue and all conversations
What to handle first, how new conversations reach you, and how to find a conversation.
Connect your personal Telegram
After connecting your own Telegram account, you can ask Orbit to search and read your chats, summarize messages, or look at images and files. Orbit is read only: it never sends messages or marks chat…
Serving a conversation
Start serving, replies and notes, transfers, recalling a message, ending a conversation, and conversation states.
Working on assist tickets
Claim, work on and resolve assist tickets, and what the customer sees in the widget.
Orbit
Members' AI assistant, which reads conversations, drafts replies and acts for you when you ask.
Status, notifications and preferences
Online, Focus on tickets and Away, when Desk alerts you, and your personal preferences.
Installing the web widget
Put the chat widget on your website, set its look and conversation behavior, and tell it which player is signed in.
Members, assignment and timing
Add members and roles, decide how new conversations are assigned, and set conversation timing and business hours.
Stats
Resolution rate, how teammates joined, waiting and reply times, satisfaction, and how each number is counted.
Keys, bans and the activity log
Personal and site keys, banning visitors, the activity log, and sign-in security.
Authentication and conventions
Authentication, addresses, rate limits and errors for calling Desk's open API with a personal access key.
Conversations
List conversations, read one, subscribe to its events, and write internal notes.
Tickets, stats and team
Read assist tickets, team stats, the team right now, members and sites.
Build
02 · Harness · Persona, tools, SOPs and knowledge, published as fixed versions
What Harness is
Harness is where you build an Ailo. Who it is, which procedures it follows, what it can look up and which tools it can call are all written in Harness and saved as immutable versions; testing, going …
Build your first Ailo
This page starts from an empty Harness organization and ends with Ailo serving customers on a Desk channel. Most steps happen in the Harness console; the SOP and system prompt editors are not open to…
The Harness console
The Harness console is the web app for building Ailos. The sidebar has four entries: Orbit, Stats, Content and Workspace, with the organization home under Orbit; settings open from the avatar menu. E…
Code packages and main
Every turn ends up running one code package's entry point, main(context, handle). The Runtime calls it once per turn: context is the turn's business input, and handle is the private handle through wh…
Ailo SDK
@ailodesk/ailo-sdk is the library for writing main(context, handle): a ready-made model loop, tool definitions, ways to ask Desk for actions, and all of main's types. It is optional; you can call han…
The Runtime and run records
The Runtime is the part of Harness that actually runs a turn: it receives the turn Desk opened, pins the package version, calls main, calls the model on its behalf, enforces the call, budget and time…
Versions, publishing and going live
Every change to an Ailo is saved as an immutable package version. Customers always meet the live version; saving and publishing never change it, only going live and rolling back do.
Knowledge and SOP API
Knowledge (FAQ), SOPs and the persona live in the Harness content table: one identity row per entry plus immutable versions. The Console pages, Orbit, the CLI and scripts all use the same named comma…
Verify
03 · Research · The experiments behind each default
Knowledge retrieval for a support agent: semantic search, full-context reading and variants compared
We study how the support agent Ailo obtains evidence from a knowledge base before it answers. On a fictional support knowledge base for an online game platform (572 articles; questions in English, Th…
Interim replies while the agent looks things up: evaluating opening lines and wait notices
When a customer's question requires an account lookup or knowledge retrieval, the support agent Ailo produces nothing until its tool calls finish, and the customer may see no reply for a long time. W…
Choosing the right SOP as the catalog grows
With a handful of SOPs, putting the catalog in the prompt and letting the main model choose is enough. A site may have hundreds. We wanted to know three things: how much worse a main model gets as SO…
Recall engine: evaluating knowledge and SOP prefetch before the first model call
The recall engine retrieves relevant knowledge passages (and, where applicable, SOP candidates) on the server before the support agent Ailo makes its first model call, and appends them after the cust…