Configuration

Everything in Dashboard → Configure shapes how J.O.S.I.E behaves for your customers.

System prompt

The system prompt is the primary instruction layer. It should include:

Who you are — company name, industry, products
Scope — what questions you answer vs. what to decline
Tone — formal, friendly, concise, etc.
Escalation — when to suggest email, phone, or human support

Example structure:

You are the customer support assistant for Acme Corp, a B2B SaaS company.

Answer only questions about Acme products, pricing, billing, and account setup.
If asked about competitors or unrelated topics, politely decline and offer to help with Acme.

Tone: professional, concise, helpful.
Support email: support@acme.com

Static knowledge vs. system prompt

	System prompt	Static knowledge
Use for	Behavior, tone, rules	Facts (hours, URLs, SKUs)
Size limit	Keep focused	Tier-based char limit (4k Basic, 8k Pro)
Always sent	Yes	Yes, appended to context

Put stable facts in static knowledge so you can update hours/pricing without rewriting the whole prompt.

Allowed origins (required for embed)

The widget only loads on domains you list. This prevents others from using your API key on their sites.

Format: full origin including scheme, e.g. https://www.yourcompany.com

Add every domain and subdomain you use (www and apex if both)
Local dev: http://localhost:3000 for testing
Changes take effect immediately — no redeploy of widget.js needed

Avatar

Upload a square image (PNG/JPG/WebP). It appears in:

Dashboard chat preview
Embedded widget header
Cached per-tenant with private cache headers (no cross-user bleed)

Recommended: 256×256 or larger, simple logo or mascot.

Widget appearance

From Configure you can set:

Placeholder text in the input field
Primary color accents in the widget (where supported)
Dark/light default for the widget chrome (users can toggle in-widget)

Setup Chat (guided onboarding)

The dashboard Setup Chat walks you through questions about your business and drafts configuration. When satisfied:

Review suggested prompt and knowledge
Click Apply to configuration
Save and test in preview

Guardrails (automatic)

Even with a perfect prompt, J.O.S.I.E runs server-side guardrails before the model sees the message. See Guardrails for the full pipeline.

Best practices

Be explicit about refusal — "Do not answer medical, legal, or competitor questions"
Duplicate critical facts in static knowledge and RAG docs for Pro users
Test edge cases — pricing, refunds, account deletion, angry users
Rotate keys after staff changes if keys were shared