Skip to content

Chatting with an assistant

People talk to a published assistant in one of two places: signed in to the console, where the conversation is kept as theirs, or on the assistant’s public link, with no account at all. Both are answered by the same agent, grounded in the same knowledge and held to the same guardrails. This page describes both, for the builders who publish assistants and for the people who use them.

Where Who How they get there
In the console Admin, Builder, Reviewer, End user The overview’s Assistants you can use, or a conversation in My conversations
On the public link Anyone with the full link A share link an Admin created. See Publish and share an assistant

An Auditor reads conversations but does not chat. Only Active assistants answer; a draft or disabled one is not there for a person who only chats.

An end user’s overview shows two panels:

  • Assistants you can use: every live assistant in the tenant, with its welcome message. With none, it reads No assistant is live in this tenant yet.
  • Your recent conversations: the conversations you left off, with the assistant and when you last spoke. All your conversations opens My conversations.

Opening an assistant shows its chat page:

  1. The header: the assistant’s name, a breadcrumb back to My conversations, and the line “Ask a question. The conversation is kept in My conversations, where you can reopen it.” A reopened conversation reads “A conversation you started. Ask on, and it continues where it stopped.” and has New conversation.
  2. Conversation: the welcome message, or Ask this assistant a question., then the turns.
  3. The message field, Ask a question…, and Send.
  1. Type your question in Ask a question….
  2. Press Enter or choose Send.

The answer streams in and is formatted: lists, tables, code. When the agent is grounded in knowledge, the answer ends with Sources: and the numbered documents it drew from.

  • To continue, open the conversation from Your recent conversations or My conversations. Its turns are read back, and the next question continues it.
  • To start fresh, choose New conversation. The earlier conversation stays where it is.
You see What it means
Waiting for an approval before this can be answered… The agent wants to use a tool that needs a person’s approval. The page updates when a reviewer answers. See Human approval
The approval window closed without an answer. Nobody answered the approval in time. Ask again
The answer did not arrive. and a reason The model or the agent failed, or the tenant’s budget is spent. Ask again, or tell your tenant admin
This assistant is not available It was taken down, never published, or belongs to another tenant
This conversation could not be read back. The conversation could not be opened. Start a new one

The public page is the assistant and nothing else: no console, no sign-in, and the browser tab carries the assistant’s name.

  1. The logo, in a thin bar at the top, when the assistant has one.
  2. The chat header: the assistant’s name and Start a new conversation.
  3. The start screen: the welcome message (or How can I help?) and the assistant’s starter prompts as buttons.
  4. The conversation: each answer is labelled as written by an AI model. AI explained opens a note: “This assistant answers with an AI model, from the documents and tools it was given. Check anything important before you rely on it.” Answers that draw on knowledge carry their Sources.
  5. The message field, Type a message…, with Send message; while an answer streams, Stop the answer.
  6. The reference line at the bottom: “Your conversation reference: v-… — quote it to have this conversation deleted.” It is not shown when the site that linked here passed its own handle for the visitor.

The page’s own words follow the visitor’s browser language where Olympusx AI offers it: English, French or Arabic.

  1. Choose a starter prompt, or type in Type a message….
  2. Press Enter or choose Send message.

To stop a long answer, choose Stop the answer. To start over, choose Start a new conversation.

The conversation survives a reload of the page, in the same browser tab. Closing the tab, or opening the link in a new one, starts a new conversation, so the next person at a shared computer does not see the last one’s questions. Nothing is stored in the browser that can read a conversation without the link’s key.

A visitor quotes their reference (v-…) to whoever published the assistant. A tenant admin finds and erases the conversation in Erasure.

The page says What it means
This assistant is not available The link is mistyped, or the assistant was switched off. Ask whoever shared it for a new link
This assistant link is missing its access key. The link was cut short. Ask for the full link
This assistant could not be reached The service did not answer. Try again in a moment
Waiting for an approval before this can be answered. This page will update when it is. A tool call is held for a person’s approval
The approval window closed without an answer. Ask again. Nobody approved in time
The message is too long The message is over the limit; shorten it
The answer did not arrive. Try again in a moment. The answer failed
  • Every turn is answered by the assistant’s current agent, with the conversation so far as context.
  • Every turn passes through the tenant’s guardrails when they are on. A message the guardrails block is answered with the reason instead of an answer.
  • Every turn is metered to the tenant: a signed-in person’s turns to the tenant, a public link’s turns to the project its key belongs to.
  • The tenant’s Admins, Builders, Reviewers and Auditors can read every conversation in Conversations and on the assistant’s Conversations tab. A person who only chats reads their own.
  • Conversations are kept for the period your platform administrator sets for assistant conversations. See Data retention.
What Limit
One message 4,000 characters
Wait for an answer on the public link 150 seconds before the chat reports a failure
Wait for an approval Up to ten minutes, then the chat stops waiting
Conversation title The first question, cut at 60 characters
Public link requests 60 a minute per tenant by default, across all its public links