Chat Interface

The chat interface is a full page, hosted by QAnswer, where people hold a conversation with your assistant. You share it as a single link — there is nothing to install and no website of your own required.

Open the assistant, go to the Expose tab and select the Chat interface card. The page that opens is a five-step guide.

Note
If the assistant's organization does not have the Expose add-on, this guide opens read-only: an "Expose add-on required" notice appears at the top and every step is greyed out. See The Expose add-on.
Note
The chat interface is a page of its own. If you want the assistant to appear on a site you already run, use the website chatbot instead — it embeds the same conversation as a small widget.
The chat interface guide, showing the UI integration settings and Language steps

Step 1 — UI integration settings

Two checkboxes control how the hosted page is framed:

  • Disable navbar on mobile — hides the top navigation bar for visitors on phones, leaving more room for the conversation.
  • Disable branding — removes the QAnswer logo and footer, so the page carries nothing but your assistant.

Step 2 — Language

Choose the language the interface itself is displayed in — the labels, buttons and placeholder text. Visitors can still write in any language your assistant understands. This is the language of the shared page only, unrelated to the language of your own QAnswer account.

Step 3 — Configuration (optional)

This step holds two sub-sections that shape the first thing a visitor sees.

Description

A short explanation of what the assistant is for and what it can answer, shown to visitors on the public page. The rich-text editor lets you add links and formatting.

The Configuration step, with the Description editor and its assistant-level notice
Warning
The description belongs to the assistant, not to this one interface. Editing it here also changes what the search interface, the website chatbot and every other integration show.

Initial message

The greeting the assistant opens the conversation with, before the visitor has typed anything. A good initial message says what the assistant knows about and invites a first question.

The Initial message field with the Rich text switch enabled
  • Rich text — switches the field between a plain text box and a full editor with formatting and links. Leave it on if you want a formatted greeting.
  • The expand icon — opens the editor in a larger dialog, which is easier for a longer message.
Warning
Press Save at the bottom of the Configuration step to keep the description and initial message. Unlike the assistant editor, this step does not autosave.

Step 4 — Choose your access

Nobody can open the link until you decide who is allowed in:

The Choose your access step for the chat interface, with the Public, Logged-in users and Only with an API key options
  • Public — anyone with the link can chat, without logging in or an API key. This is the usual choice for a public link.
  • Logged-in users — the link works, but only after the visitor signs in to QAnswer. Useful for sharing inside a company.
  • Only with an API key — the assistant stays private and the link carries an API key that lets visitors in. Select it to take a public link offline again: a link without a key stops working.

With Only with an API key selected, the key controls appear right under the option:

  • Use an existing API key lists the assistant's keys that can be used here; expired keys and Read and write keys are left out. It only appears if you have write access to the assistant and such a key exists.
  • To make a new key, type a name in API key name and press Generate key.
  • The chosen key is then shown masked, with a copy button, and Use another key brings the picker back. QAnswer remembers the key in your browser and selects it again the next time you open the guide.
  • Keep the API key out of the exported code (advanced) removes the key from the link. The link then only works in this browser, where the key is kept in local storage.

Switching to Public or Logged-in users sets the key aside, since none is needed then; it comes back if you return to Only with an API key.

Note
Below the options, a status message says whether the integration is ready, for example "Ready: anyone can use this integration, no API key needed.", or what is still missing, such as "Not ready yet: select or create an API key above."
Warning
Choosing Public shows the warning "Tool access is restricted for users who aren’t signed in." Anonymous visitors can chat, but the assistant's MCP tools will not run for them. If your assistant depends on tools, prefer Logged-in users.
Warning
Access is an assistant-level setting. Changing it here also changes it for the assistant's search interface, website chatbot, REST API and every third-party integration.
Note
This step only controls anonymous, public access. To share with named users, teams or organisations, use the Share dialog in the assistant's top bar.

Step 5 — Share

Once access is set, the link appears. Use the copy icon beside it, or the arrow to open it in a new tab.

The Share step showing the generated public chat link

The link carries your choices from the earlier steps as parameters — the language, and whether the navbar and branding are hidden. Changing a step regenerates it, so copy the link again after you adjust anything.

What visitors see

Opening the link gives a chat page named after your assistant, opening with the initial message you configured:

The public chat page for an assistant
Note
Conversations held here are recorded like any other, so you can review them under Analytics on the assistant's page.