The Agent page
The seven settings that decide how Aura writes, what is deliberately not on this page, and how saving works.
The Agent page, under Aura AI, is where you decide how the agent sounds, what job it thinks it is doing, and what it knows about you. It holds exactly seven settings.
It is worth saying plainly what it does not hold, because that is the question people arrive with. The agent's name, greeting, languages, colours, logo, avatar and support contacts are not here. They belong to the widget and are set under Channels, Web chat. There is one editor for those, not two.
There is also no model or LLM setting on this page at all. The model is not something a workspace chooses.
Editing needs admin or owner. Everybody else sees the same three sections as a read-only list, with "Not set" where a value is empty.
How it answers
This card is about register, not appearance.
| Setting | What it is |
|---|---|
| Reply tone | One of Conversational, Professional, Friendly, Formal, Empathetic or Playful. |
| Persona | Free text. The character the agent plays — its manner, not its job. |
| Brand voice | Free text, up to 1000 characters. Phrasing dos and don'ts. |
If the agent was set up elsewhere with a tone outside the list, Auralis keeps it rather than quietly coercing it into one of the six.
Persona and brand voice sound similar and pull in different directions in practice. Persona is who is speaking — "warm, unhurried, never cute". Brand voice is the house style they speak in — "never say unfortunately", "we call them members, not users", "no exclamation marks". If you fill in only one, fill in brand voice: it produces the more consistent change.
What it is for
| Setting | What it is |
|---|---|
| Agent role | A job title, up to five words — for example, "customer support specialist". A counter enforces the limit as you type. |
| Agent goals | Up to 250 characters describing what a good answer achieves. |
Goals are not a list of tasks. They are a definition of done.
What it knows about you
| Setting | What it is |
|---|---|
| Company info | What your company does, in the agent's own words. |
| Keyword glossary | A list, built one entry at a time with Add. |
Company info is the background the agent answers over and above its training data, so it is the place for facts too small or too general to be worth an article.
The keyword glossary holds product names and terms the agent must spell exactly one way. It is what stops the agent writing "Auralis AI" when the product is "Aura AI", and it earns its keep faster than anything else on the page.
Two of these reach the workflow
Brand voice and Keyword glossary are also input variables a workflow node can take. A node that does not take them will not follow your house style, however carefully you wrote it here. See Workflows.
Saving
The form saves as a whole. The button stays inactive until something has actually changed, and stays inactive while any field is over its ceiling — Auralis will not send a partial save behind your back. If you are over a limit, the page names the field.
A successful save says "Saved. These are the agent's live values now." A failed one keeps everything you typed. Nothing is cleared, so you adjust the named field and save again rather than retyping the form.
Only the fields you changed are sent. That matters if two admins are editing at once: the last write wins per field rather than per form, so you do not silently overwrite a colleague's untouched field with a stale copy of it. The page records the time it read the values, near the save bar, so you can tell how old what you are looking at is.
When the page will not open
If Auralis cannot be reached, the page shows a card saying so rather than an empty form. That is deliberate: a form rendered without live values would happily save blanks over the agent's real configuration. A page that cannot read must not write.