Agent name, avatar and greeting

The agent's name

Karas is the product; the assistant on your site is whatever you call it. Customers talk to a named assistant more readily than to a nameless one.

A name that is plainly not a person is the honest choice, and it prevents the awkward moment where a customer realises mid-conversation. Give it your brand's name, a mascot, or something short and neutral.

The avatar

Either an image URL or up to two initials, which are rendered on your brand colour. Initials are the reliable choice: they need no hosting, load instantly, and cannot break if an image URL later moves.

The greeting

The first thing a visitor reads when they open the widget, up to 280 characters. The default is "Hi! How can I help you today?", which is fine and forgettable.

A better greeting sets expectations about what the assistant can actually do:

Hi — I can answer questions about orders, delivery and returns from our help centre. If you need a person, just ask.

That does three useful things: it says what topics are covered, it implies the answers come from your documentation, and it tells the visitor the exit exists before they need it.

The composer placeholder

The grey text in the input box. "Ask a question…" is the default. Something more specific nudges better questions — "Ask about delivery, returns or sizing…" tells a visitor what this assistant is for.

A short line under the composer, up to 200 characters. Two good uses:

Disclosure. Telling visitors the answers are AI-generated and cite your help centre. Some jurisdictions expect this, and it is good practice regardless. See Acceptable use and AI disclosure.

A fallback contact. An email address or phone number, which is also shown to a visitor if a handoff request fails.

Requesting changes

Email support@usekaras.com. These settings live on your account, so changes reach your site without you editing anything.