Building

Agents

An agent is one assistant, with its own name, appearance, keys and assigned material. Most accounts need only one. Several become necessary when different audiences must not share the same answers.

Creating an agent

Creation asks for very little, because behaviour comes from your material rather than from configuration.

FieldRequiredLimitNotes
NameYes1 to 100 charactersShown in the widget header, so write it for visitors rather than for your own records
DescriptionNoUp to 500 charactersInternal only. Visitors never see it
AppearanceNoLight or darkLight or Dark surface, plus a curated Widget Color palette
Welcome MessageNoUp to 200 charactersGreeting shown at the start of a new widget conversation
PersonalizationNoUp to 4,000 charactersOptional instructions for how the agent communicates. Default keeps the adaptive policy; Custom shapes tone, structure, and response language within the platform rules

An agent starts with no keys, so nothing is issued automatically. Create a secret key for server calls, or create a widget installation to get a publishable key and its embed snippet, both on the API Keys(sign in required) page. Create your first agent on the Agents(sign in required) page.

Note

How many agents you may have at once depends on your plan. See Plans and Usage.

Communication style and greeting

By default agents use one adaptive communication policy: professional, friendly, natural, and responsive to the visitor's context, answering in the visitor's own language. Owners can optionally write Custom Personalization instructions (up to 4,000 characters) that shape persona, tone, structure, and response language. An explicit response-language instruction, such as one asking the agent to always answer in English, takes precedence over the visitor's language; a softer preference does not. Custom instructions never change what the agent may claim: grounding, citations, security, and the platform identity still outrank them, and answers still come only from the agent's knowledge base.

Welcome Message is an optional greeting shown when visitors start a new widget conversation. You can customize it when creating or editing an agent. It defaults to “Hi! How can I help you today?” and accepts up to 200 characters. Leaving it blank uses the default.

Agent limits

PlanMaximum agents
Starter1
Lite2
Pro5
Business20
EnterpriseBy contract

These are account limits. More agents can separate audiences or knowledge scope, but they share the account's request quota and per-minute throughput.

Appearance

Advanced Settings groups the widget's appearance controls. Choose Light or Dark, then a Widget Color palette for the header, messages and composer. The Widget Avatar offers searchable Classic icons, four Animated characters (Educational, Customer Support, General and Assistant), or a Custom image. Classic icons and Animated characters can use an optional avatar color. The hosted widget reads these settings on page load; the Playground uses a fixed dark interface for testing answers and behavior.

Custom avatar images accept PNG, JPEG or WebP up to 5 MB. The server resizes them to fit within 512 by 512 pixels and converts them to WebP when you save. You can replace or remove an uploaded image in the agent editor. The Custom option requires the chatbot avatar storage service to be configured; an upload error does not mean the agent's other settings were saved.

Personalization & Language contains Widget Language, Welcome Message and Personalization. Widget Language changes the widget interface between English and Indonesian; it does not translate a custom Welcome Message or set the AI's answer language. By default answers follow the visitor's language. An explicit response language instruction in Custom Personalization can override that default.

ValueDefault
SurfaceDark
Widget ColorNeutral
Widget AvatarClassic Bot
Widget languageEnglish
Launcher positionBottom right
Corner styleRounded
Welcome messageHi! How can I help you today?
Input placeholderType your message...

If you are building your own interface, read these values rather than copying them into your code, so an agent stays consistent with what its owner configured. See Official SDK or REST API.

Status

An agent is either active or inactive, and the switch takes effect everywhere at once.

  • Active. It answers on the widget, the SDK and the API.
  • Inactive. It refuses every request on every surface, including the Playground, while keeping its material, its keys and its installations intact.

Deactivating is the right move for taking an assistant down temporarily, during a content rewrite for example. Deleting is not reversible.

Editing and deleting

Renaming an agent or changing its appearance takes effect on the next page load for embedded widgets, and immediately for your own interface. Neither affects its keys.

Heads up

Deleting an agent is permanent. Its keys stop working straight away, so any site still embedding them will show a refused request rather than a chat bubble. Deactivate first if you are not certain.

Getting it in front of visitors

Each installation on the API Keys(sign in required) page provides the embed snippet, prefilled with its publishable key. For a website that snippet is all you need, once the site's origin is on the installation's allowed origins.

GoalRead next
Drop a chat bubble on a websiteEmbed widget
Build a custom chat interfaceOfficial SDK
Call it from a backend or an automationREST API
Decide which sites may use the keyAllowed origins
Note

An agent with no material will answer, but it will decline almost everything, because it has no material to answer from. Attach a knowledge base before you launch. Questions it cannot answer from the available material are listed on the Knowledge Gaps(sign in required) page.

Keys are created, rotated and revoked on the API Keys(sign in required) page, one at a time. Rotating a key issues a replacement of the same class and leaves the other class alone, and the previous value stops working immediately, so update wherever that one key is deployed. The prefixes are wcx_pk_ for a publishable key and wcx_sk_ for a secret key.

Tip

Give an agent the name a visitor should see, not the name your team uses internally. It appears in the widget header, and "Support" is clearer to a customer than "prod-bot-v2".

Disclaimer

The Playground uses a fixed dark interface to test agent behavior. Check the hosted widget to review your saved appearance with a real visitor-facing conversation.