> ## Documentation Index
> Fetch the complete documentation index at: https://docs.relayhub.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Relay

> Relay is your lead bot: it gives each part of a job to the right bot, passes results on, checks work and answers your questions about any bot

Relay is your lead bot. It is optional, and it knows all your other bots. Relay was called the Orchestrator before. You talk to Relay like your chief of staff: tell it a job, and it gives each part to the right bot, passes the results on and gives you one answer. Ask it what any bot is doing, did or needs, or ask it to check a job, and it answers at once.

## Create your Relay

Click **New bot**. When you have not created Relay, the pane shows the section **Create your Relay**: "A high-tier coordinator that can manage your Bots." Click **Create your Relay**. You can have one lead bot. When you archive Relay, you can create it again.

Relay is first in your list of bots, apart from the others. It shows the faces of the bots it leads and a line such as "Leads 6 bots". While it works on a job, the line says which bots take part, for example "Working with Renterra Bot and Email drafter", and those bots have a blue ring.

Relay is yours alone. Other people and their bots cannot send it requests.

## Give it a job

Write the job in its chat, for example "Invoice rental order 1251 and email the invoice to the customer" or "Research the new crane rules, make a branded deck and have it checked".

1. It writes a plan first: each step names the bot that does it, the steps it waits for and what it hands on.
2. It sends each step to its bot. Steps that do not wait for each other run at the same time.
3. It passes results on as real files and values, for example the invoice PDF becomes the attachment of the email.
4. It answers the bots' questions from the job when it can, and asks you only what the job cannot answer.
5. When a check step finds a problem, it sends the work back to the bot that made it, with the reasons.
6. You get one answer at the end: the result of each step, the record numbers and the files.

Its progress line shows the step that runs, for example "Working: step 2, Email drafter. 1 of 2 done." When a step needs your approval, for example to send an email, the card shows in the chat of Relay with the step and the bot, and in that bot's chat. One decision closes it in both.

Relay never does a step itself. When no bot fits a step, it tells you and offers to create one.

## Ask it about your bots

Ask questions such as:

* "What did Renterra Bot last work on?"
* "What needs me right now?"
* "Give me a link to the Email drafter."
* "Did Renterra Bot open work order 1275 correctly?"

It answers from RelayHub's records of your bots in one step, without sending the bot a request: each bot's state, current job, the jobs up next, what waits for you, its recent jobs with their results, costs and files, and the evidence of a job. Every bot and job it names is a link that opens it.

To check a claim, it reads the job's evidence first. When only an outside system can confirm it (for example Renterra), it asks the bot that uses that system for a read-only check, and tells you both.

It reads only your own bots.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.