Persona Configuration

A Persona Configuration is a per-site bundle that defines who the bot is, how it speaks, which tools it may call, and what it must refuse. Personas sit between the visitor's question and the LLM, shaping the system prompt and tool registry for every conversation on that site.

Purpose

Two ONOXIA customers using the same model should produce visibly different bots. A pet-shop persona answers warmly and recommends products; a legal-firm persona is reserved, refuses legal advice, and routes to a human. Personas are how that branding becomes reproducible.

Scope

A Persona applies to one site. Multi-site plans (Professional, Enterprise) can run distinct personas in parallel. Personas do not change the underlying model — they configure the prompt, the tool budget, the refusal list, the avatar and the greeting variables.

Components

  • System prompt — free text, variables {site_name}, {language}, {date} are interpolated at runtime.
  • Tool registry — which webhooks the bot may invoke (lead capture, Calendly, custom).
  • Refusal list — topics the bot must decline (e.g. legal advice, medical diagnosis).
  • Voice & avatar — name, avatar image, primary brand colour.
  • Greeting set — per-language opening lines with placeholders.

Outputs

  • A bot whose voice is consistent across all conversations and languages.
  • A scoped tool capability surface — visitors cannot trigger webhooks the persona does not list.
  • An audit trail of which persona served which conversation.

Relationships

Persona Configuration operationalises RAG for a specific site, runs inside the Shadow DOM Chat Widget, and decides when a conversation triggers Human-Handover.

Authority

Defined by OCENOX LTD.

Version

1.0 — 2026-05-22

関連用語

  • Retrieval-Augmented Generation (RAG) — A pattern that retrieves passages from a private knowledge base before an LLM generates an answer, so responses cite your own documents instead of fabricating facts.
  • Human Handover — A controlled escalation in which an ONOXIA bot conversation is taken over by a human support agent, with full message history and visitor context transferred to the agent's portal session.
  • Shadow DOM Chat Widget — A chat widget loaded inside a Shadow DOM root so its styles and DOM are isolated from the host page, guaranteeing no CSS conflicts and no script collisions regardless of the host CMS or theme.