Build your agent

Persona, theme & prompts

Three things shape how an agent feels: persona (how it answers), theme (how it looks), and starter prompts (what visitors see first). The Customize page brings them together with a live preview.

Persona & tone

The persona object has two fields:

• name — the assistant's first-person identifier (e.g. “Aria”). It appears in the chat panel header. Leave it blank to fall back to a localized default.
• tone — short descriptive phrases appended verbatim to the system prompt (e.g. “warm but professional, never pushy”).

System prompt

The built-in system prompt handles safety, RAG grounding, citation behavior, and prompt-injection defense. Your system_prompt field is appended to it — use it for:

• Brand vocabulary (always say “subscription”, never “plan”).
• Conversion behaviors (offer a demo after pricing questions).
• Domain-specific hints (industry jargon, product naming).

Custom prompts cannot disable the built-in injection defense — that's regression-tested on every release.

Guardrails

The guardrails object lets you tighten the agent's behavior:

• avoid — a list of topics the agent refuses to discuss.
• max_chars — a soft cap on reply length, e.g. 800.

Starter prompts

Up to six suggestion chips render on first open and disappear after the visitor's first message. Keep them under 80 characters and conversion-oriented — “How much does Pro cost?” beats “Tell me about your product.”

Theme

The Customize page renders a live preview on the right pane so you can see changes without republishing.

Pre-chat lead capture

A toggle gates the chat behind a Name + Email form before the conversation starts. The upside is higher capture rates; the downside is friction — appropriate for sales-led sites, less so for documentation. Once a visitor submits, the gate doesn't reappear on subsequent visits.

Custom lead form fields

You can replace the default Name + Email fields with your own. Supported types: text, email, tel, textarea, select, checkbox.

Reserved keys (email, name, phone) map directly to columns on the Lead record. Everything else lands in the fields JSON column. The legacy Name + Email format remains backward compatible.

Limit: 12 fields maximum per agent.

Language

language_default pins the agent's reply language using a BCP-47 / ISO 639 code. Glozr ships 132 locales auto-discovered from lang/*.json — fully translated for the core surfaces, with UI chrome translated everywhere else. When empty, the agent follows the visitor's Accept-Language header. RTL locales (Arabic, Hebrew) automatically mirror the widget layout.

Confidence threshold

A value in [0, 1] that controls when the agent says “I don't know”. Lower values suit Cloudflare bge embeddings; higher values are tuned for OpenAI text-embedding-3-small. See Confidence threshold for the per-provider defaults.