Fields you configure
Agent Name
The name used everywhere the agent appears — the Launch Pad list, Copilot threads, the Live Chat header, and email signatures. Use a role-based name ("Acme Support Assistant") rather than a person's name so the agent can be reassigned without a rebrand.
Description
An internal, one-or-two sentence summary of what this agent is for and who owns it. It is not shown to end users, but it is what teammates see when browsing the agent list, so state the use case and the business owner.
Avatar
The image shown in the chat widget and in Copilot. Upload a square PNG or JPG (512×512 or larger); it is cropped to a circle. Brand marks read better than photos at small sizes.
Conversation States
The canned copy the agent uses outside of a normal answer: the greeting shown when a conversation opens, the fallback used when the agent cannot answer, and the closing/offline message. These are written here, not in the instructions, so they stay consistent across every channel.
Language Settings
The primary language the agent replies in. The underlying model can still answer in the user's language when instructed to; this setting controls the default for greetings, fallbacks, and system copy.
Tips
- Everything on this tab is presentation. Behavior rules belong in Train → Agent Instructions.
- Change the greeting and fallback before launch — the defaults are generic and are the first thing every user reads.