Chat Interface

​

Starting a Conversation

There are several ways to begin a new chat:

• Home Page — Type a message in the input box or click an assistant card.
• Sidebar — Click the New Chat button.
• Agents Page — Browse all assistants and click one to start a conversation.
• Existing Conversation — Continue any previous conversation from the sidebar or chats page.

When you select an assistant, you’ll see its welcome page explaining what that assistant can help with. What else appears depends on how you got there:

• Starting a new chat (from the home page or the New Chat button) shows just the assistant’s introduction and the message input — a clean slate.
• Opening the assistant from the Agents page also lists your previous conversations with that assistant, so you can resume one instead of starting over.

​

Required Context

Some assistants are configured to require specific context before they will answer — for example, your company size, industry, or strategic focus. When this is the case, an amber banner on the welcome page lists what you need to provide. Send your first message including that information. If anything is missing, the assistant replies with a short clarification asking for the missing pieces; once you provide them, the conversation continues normally and the requirement is not re-checked for the rest of that conversation. To review or update the context you provided, click the clipboard icon next to the message input. The panel shows your original context along with any updates you’ve added, and lets you submit a new amendment from the same place.

​

Sending Messages

Type your message in the input area at the bottom of the chat and press Enter to send (or Shift+Enter for a new line).

​

Attaching Files

Click the paperclip icon to attach files to your message:

• Maximum file size: 25 MB per file
• You can attach multiple files to a single message
• Remove files before sending by clicking the X on each attachment
• Supported formats include PDFs, Word documents, text files, and more

Each attachment appears inside the message box, above where you type, showing its file-type icon, name and size — so you can see exactly what you’re about to send. After you send, the attachment stays on your message — click it to read the original in the panel on the right, and download it from there if you need a copy. Files attached before this was introduced still show on the message, but can’t be re-opened: only their extracted text was kept at the time. The assistant works from the text extracted from an attachment, and only the first 10,000 characters of that text are stored. On a long document that means the assistant is reading the opening section, not the whole file — the remainder is not kept. When an attachment is cut short this way the assistant is told the document is partial and asked to say so rather than summarizing it as though it were complete. Your original file is unaffected: it stays on the message in full and you can still open and download it.

​

Selecting a Model

If multiple AI models are available, use the model selector next to the input area to choose which model processes your message. Your selection persists for the current assistant session.

​

Generating Documents

If document templates are configured, a Generate button (wand icon) appears next to the model selector. Click it to browse templates organized by category and generate presentations, formatted messages, and more. See Document Templates for full details.

​

Reading Responses

AI responses stream in real-time — you’ll see the text appear as it’s generated. When you ask a follow-up in a long conversation, your question moves to the top of the view and stays there while the assistant works, so you can keep reading it alongside the progress steps. The view follows the answer once it starts arriving.

​

Task Progress

For complex queries, the AI may perform multiple steps (searching documents, analyzing data, synthesizing information). A task progress indicator shows:

• The current step being performed
• Completed steps with checkmarks
• Sub-steps and tool calls being made

The indicator updates as the assistant moves through the run, so a long answer shows where it has actually got to rather than a single unchanging label. A typical question moves through Analyzing Question, Routing Query (deciding how to handle it), Planning, Scope Analysis (finding the data that answers it), then Report Generation as the answer is written. Steps vary by question — a query that is answered from what it already found will skip the retrieval step entirely.

​

Citations and Sources

When the AI references your organization’s documents, you’ll see numbered citations in the response. Click any citation to open the Source Details Panel on the right, which shows:

• File title and type
• Data source name (Box, Google Drive, SharePoint)
• File path and last modified date
• A content preview of the referenced section
• A direct link to the original file

Citations are filtered to your own access, like the answers themselves — you will only see a citation for a record you are allowed to read. On very broad questions a correct answer can arrive with no citations at all; see Sources and citations. For graph entities cited in provenance, use View lineage on the entity card or open the graph explorer to see how properties were extracted, imported, or enriched. See Graph Lineage.

​

Artifacts

When the AI generates long-form content (reports, analysis, structured outputs), it opens automatically in the Artifact Panel on the right side. You can:

• Maximize the panel for full-width reading
• Minimize it back to a side panel
• Close it to return to the chat view
• Export the content as PDF, DOCX, or Markdown — click the download icon in the panel header.
• Generate document from the content — click the wand icon in the panel header and pick a template to have the agent produce a formatted file (DOCX, PPTX, or PDF). See Document Templates.
• Edit the content inline with the built-in editor

You can also export from the message action toolbar on the chat response itself (see Export & Sharing). Generated files (DOCX, PPTX, PDF, CSV, and similar) use a Download button in the file panel to save the original file.

​

Questions from the Assistant

Sometimes the assistant needs something from you before it can answer — which part of the business you’re asking about, whether you want a summary or a full report, which of several close matches you actually meant. Rather than writing the question into its reply and leaving you to guess the format of an answer, it asks with a question card underneath the response. A card carries a handful of questions — five at most by default, and an administrator can set a different limit per assistant — each with a few suggested answers shown as selectable chips:

• Pick one or several. Most questions accept more than one answer. A question whose options are mutually exclusive — summary versus detailed report, say — accepts only one, and picking a second replaces the first. The hint under each question tells you which it is.
• Add your own. Type in the Add your own… box and press Enter (or click +) to add an answer that isn’t offered. Your additions appear as chips you can remove with their X. If what you type matches one of the options, that option is ticked instead of adding a duplicate.
• Send answers submits the whole card in one go. It stays disabled until every question has at least one answer.

What you send is posted as a normal message in the conversation — one line per question, in Question: answer form — so the exchange stays readable when you scroll back. The assistant then resumes from wherever the question came from: usually it goes back and retrieves data using what you told it, and occasionally — when the question was only about how to present an answer it already has — it simply rewrites the answer. You don’t have to use the card. The message box stays open, so you can type your answer instead and send it like any other message; the assistant reads it as the reply to what it asked. Either way, the card clears as soon as you send. If you reload the page or come back to the conversation later, a question you haven’t answered yet is still waiting — the card is restored with the conversation. It disappears if you stop or delete that turn. The assistant won’t keep asking indefinitely. After a couple of rounds of questions — two by default, configurable per assistant — it answers with what it has and explains in plain language what it could not pin down.

​

Recommendations

After each response, the AI may suggest follow-up questions based on the conversation context. Click any suggestion to send it as your next message. Suggestions are held back while a question card is waiting for you — nothing appears under an open question but the card itself. They return once the assistant delivers its final answer.

​

What the AI can see

Answers are limited to what you are allowed to see. When your organization has access control enabled for the knowledge graph, every question the assistant asks of the graph is filtered to your own access before any answer is written — so two people asking the same question can correctly get different answers. You do not configure this and there is nothing to switch on. If an answer seems to be missing something you expected, it usually means that record is not linked to you, and an administrator can check with Preview as user on the Access Control screen.

​

Agent Flows

Some requests are handled by an agent flow — a multi-step pipeline the assistant runs for you (for example, drafting a response to an RFP). There are two ways to start one:

• Just ask. When your request matches a flow, the assistant confirms first (“I can run RFP Response Pipeline — proceed?”). Once you approve, it launches the flow in the background, so you can keep chatting while it works.
• Pick it from the composer. Click the Launch a flow button (workflow icon) next to the message input to see the flows available for this conversation, each with a short description. Choosing one launches it right away — the pick is your go-ahead, so there’s no separate confirmation. The composer prefills a short prompt you can extend with any details the flow needs before sending. The flow you picked shows as a pill on the top edge of the message box, so it’s clear the next message will launch it; clear it with the pill’s X.

Files you’ve attached to the conversation are routed into the flow automatically — including the file you attach to the message that starts it, so “here’s the RFP, draft a response” works in one go. Only files you uploaded are picked up this way; a document an earlier run produced is never swept in as the next run’s input unless you ask for it by name. If the flow still needs a file you haven’t shared, it doesn’t start, and a message in the conversation names what to attach — by the input’s readable name (for example RFP document), not an internal field name — and tells you to attach it and send your message again. Asking the assistant to continue a run that already stopped doesn’t do what it sounds like, and it now says so. No run can be picked up where it left off once it has ended — that includes one that finished successfully, not just one that failed or was cancelled. Running the flow again starts a new run from the first step, with no partial output carried over, no reading or revising of the earlier run’s document, and every approval asked again. Before it launches anything, the assistant looks up what actually happened to your last run in this conversation, and tells you plainly that this is a fresh start rather than describing it as a continuation. If that earlier run is still going, it reports where the run has got to instead of starting a second one.

​

Watching a flow run

When a flow launches, a flow-run view opens automatically in the panel on the right and follows the run live. It is deliberately spare — it exists to tell you the flow is working and to let you act when it needs you:

• A status badge showing where the run is — Pending just after you start it, Running while it works, and Awaiting review whenever there’s a question or an approval waiting for you. It can read Paused for a moment while a pause is still making its way to the panel
• One line naming what it is working on right now, by the step’s name: Working on Draft the response
• The approval or question card when the run pauses for you, so you can answer it without leaving the conversation (see Approval Steps). Documents and files a card shows you open right there in the panel
• A Stop button to cancel a run that’s still going

When the run finishes, the panel closes — unless you’re reading a file the run produced, in which case it waits until you close that document rather than taking it away mid-read. Nothing is lost either way: the result and any files the flow produced arrive as a message in the conversation, and so do the questions you answered and the decisions you made — the conversation is the record. You can close the panel at any time — the flow keeps running, and a View progress control appears above the message box to reopen the live view. While a flow is active, its conversation pulses in the sidebar, so you can tell at a glance that work is still in progress; the pulse clears once the run finishes. If a run is waiting on you (see Approval Steps), the reopen control turns amber — “Review needed — open to approve or reject” — and the conversation’s sidebar row shows an amber review badge instead of the pulse, so you can spot which conversation needs action from anywhere. These sidebar signals keep up live, with no page refresh: the pulse appears as soon as a flow starts, gives way to the amber badge when a run pauses for you, returns to the pulse once you’ve answered and the flow carries on, and clears when the run finishes or you Stop it. This works both for the conversation you’re reading and for conversations working in the background. You can also ask the assistant for the status or results of a flow it launched at any time. When the flow finishes, a brief notification appears and its full result — along with any files it produced — is added as a message in the conversation on its own, without a manual refresh. Files stay with the answer that produced them: each one is listed inside its own message, so running a flow twice in the same conversation gives you two answers with their own files rather than everything piling onto the newest one. Re-running a flow doesn’t replace the earlier document either — when a run would write a file that another run already produced here, it keeps its own copy under a slightly different name. Filenames mentioned in the answer text are clickable too, and open the same reader. A run can also stop because the service running it did — a deployment or a restart. A run stranded that way used to keep its Running status indefinitely, leaving the conversation looking permanently busy over work nothing was doing. Those runs are now reconciled when the service starts up: a run with nothing left to finish it is marked as failed, the sidebar pulse clears, and the conversation is free again. A run parked at a review gate is never touched — a question waiting on you survives a restart, along with the amber badge that tells you it’s there. Passing trouble no longer sinks a whole run either, though the cover has edges worth knowing. A momentary network problem in a step is retried once — never in the steps where an AI agent is doing the work itself, since re-running one of those could repeat something it had already done, and otherwise only while the run is working on its own. Once it has stopped to ask you something and picked up again from your answer, nothing in that stretch is retried, because re-running a step there could put a question you have already answered back in front of you. So in a flow that asks for your sign-off early, the work that comes after your sign-off is not covered by that retry. A step that failed and was then genuinely redone no longer forces the whole run to be reported as failed either — as long as it really was redone: the same step, over the same piece of work, on a later pass. A different step covering similar ground later on doesn’t clear it, and neither does anything else; a failure that nothing redid still fails the run.

​

Asking about a document a flow produced

You can carry straight on in the same conversation — “summarise the response you just wrote”, “what did it say about pricing?” — without re-attaching anything. The content of documents the flow produced is read into the conversation alongside the messages, so the assistant can answer from them directly. What it gets read in that way is a bounded excerpt, not the full document. There are limits on how much of any single document, and how much across the conversation as a whole, is carried this way; the most recently produced document is served first, so the one you just asked about is the one that fits. Where a document was cut short, or an older one didn’t fit at all, the assistant is told — so it can say the answer is based on part of the document rather than answering confidently from a fragment. That excerpt is no longer all it has to go on. The assistant can also list the documents flows have produced in this conversation, search inside one, and read a section of it at a time — so a question about something deep in a long report is answerable even though only the opening was read in. Searching looks for an exact word or phrase and ignores capitalization; it is not a semantic search, so name a term you expect to actually appear in the text. Each document is checked against your own access before it is read, and only documents produced by flow runs in this conversation can be reached this way. You can still open any of them in the panel and read them yourself.

​

Approval Steps

Some flows pause partway through for a person to sign off — for example, before a draft is finalized. These pauses don’t interrupt your chat, and you don’t have to go anywhere else to clear them: the question comes to the conversation. When a run pauses, a notification appears and the flow-run panel shows an Awaiting review card where you can approve or reject it right there, with a comment (optional when approving, required when rejecting). The question lands in the conversation too, as its own message — one per gate, naming the gate it belongs to and carrying a short excerpt of what’s up for review; for a mid-run question, the question itself and any options it offers. A run that pauses on three gates at once posts three messages, so you can tell them apart. Long documents scroll inside the card, so the approve and reject buttons stay in reach. A flow can also ask you a question mid-run — type your answer into the card and send it to continue. Acting on the card resumes the flow and the card clears. You can change what you were shown before approving it. Where the card presents a document or a block of text, an Edit button turns it into an editable field — reword a section, or edit a document’s title and each of its sections — and then Approve and continue. The version you edited is the one that carries on to the rest of the flow, not the one you were originally shown. An edited card is marked edited while you work, and Revert puts the original back. If a run pauses on more than one question at once, you don’t have to wait between them. Answer them in whatever order you like: an answer you give while the flow is still busy with a previous one is held and submitted automatically as soon as the run is free, so you don’t have to sit and retry. An answer can still be refused: if that question is no longer waiting for one — someone has already answered it in the Agent Inbox, or the run has moved on — a short message tells you so rather than leaving you wondering. On the rare occasion the run stays busy long enough that the automatic retries give up, the card comes back so you can answer it again. Answered cards clear as you go and don’t come back — though a flow that revises its work can put the same gate up for review again with the new version, which arrives as a fresh card and a fresh message rather than the answered one returning; the ones you haven’t answered stay on screen and stay usable. Each card is signed off on its own, carrying whatever you edited on it — there is no bulk sign-off, since an approval and a rejection each need their own note. Until the last question is answered, the conversation keeps its amber review badge in the sidebar. Once you’ve acted, your decision is recorded in the conversation — which gate it was, whether you approved or rejected it, and any note you left. It is folded into the question’s own message, under Your response, instead of arriving as a second message further down: scrolling back, you read the question and the answer it got as one entry, and the question drops its “answer it in the run panel” instruction, which your answer has already satisfied. If you edited before approving, the record says so and includes what you approved, so reading back through the conversation later shows the version that actually went through rather than the draft you were offered. A rejection with no reason given is recorded as such. Answers to a mid-run question are merged the same way, under the question they answered. A long response — an edited draft you approved, say — is shown as a preview with a View full response button that opens the whole thing in the panel on the right. There is one deliberate exception. If you sent a chat message of your own in between — asking something else while the run was parked — your answer stays as a separate message below it rather than folding back up into the question. Nothing you answered later ever appears above something you said earlier. The same pending review is also available to admins in the Agent Inbox, but you don’t need it — either path resumes the flow, which then posts its outcome back into the conversation.

​

Message Actions

Hover over any message to access its action toolbar.

​

AI response toolbar

Open More (⋯) on an AI response for additional actions:

​

User message toolbar

​

Stopping a Response

If the AI is generating a response you no longer need, click the Stop button that appears during streaming. The response will stop at wherever it has reached.

​

Editing Messages

Click the edit icon on your last message to modify it. The AI will regenerate its response based on your updated message. This is useful when you want to refine your question without starting a new conversation.

​

Conversation Management

​

Renaming

Click the conversation title in the header to edit it. The new name saves automatically when you click away or press Enter. Press Escape to cancel.

​

Forking

To copy the whole conversation, open the three-dot menu in the header (or on the row in the sidebar, chats list, or a folder) and select Fork. To branch from a specific AI reply, use Fork from here on that message. See Forking Conversations.

​

Sharing

Click the Share button in the conversation header to share with other users:

1. Search for users by name or email
2. Assign a role: Viewer (read-only) or Editor (can contribute)
3. Manage existing shares — change roles or remove access

​

Deleting

Use the conversation menu (three dots) to delete a conversation. A confirmation dialog will appear before deletion.

​

Filters

Some assistants support response filters that let you narrow results by category or type. When available, filter options appear above the message input. Click a filter to apply it to your next message. Like follow-up suggestions, filters are hidden while the assistant is waiting on a question card.