Look and answersBeta
Name, colour, icon, greeting and starter prompts, plus the model, language and system prompt that shape every answer
This feature is in beta. It is usable, but details can still change.
Two sections decide what visitors meet: Identity is what the widget looks like and how it greets people, Brain is how it answers. All of it is part of the draft and reaches visitors with the next publish.
Name, colour and icon
- Widget name: shown in the chat header.
- Primary color: used for the chat button and accents.
- Launcher icon: the glyph on the floating chat button, chosen from the built-in set.
- Custom logo: replaces the icon on the button and appears in the chat header. PNG, JPEG or WEBP, at most 2 MB. While a logo is uploaded, it is shown instead of the icon.
- Position: the corner of your website the button sits in, bottom right or bottom left. The test widget in the builder ignores it.
Greeting and starter prompts
- Welcome message: the first message in the chat when a visitor opens it.
- Welcome note: a speech bubble next to the closed button that invites visitors in, after a delay you choose (0 to 60 seconds). Leave it empty to show none.
- Starter prompts: suggested questions shown when the chat opens. Write them the way a visitor would ask, "When is the recycling centre open?", not as feature names.
Model
Automatic is the recommended choice: DeutschlandGPT picks a suitable model and keeps it current. Pick a fixed model when you need a specific one. Which models exist and where they are hosted changes over time, so the list in Brain is the source of truth.
If a fixed model is later withdrawn, the widget cannot be published until you choose another. See Publish and versions.
Language
The language sets the widget interface and speech-to-text. Automatic follows the website the widget is embedded in, which suits bilingual sites. Choose German or English to fix it.
System prompt
The system prompt is the hidden instruction behind every answer: the bot's role, its tone, and what it should and should not do. Visitors never see it.
A good system prompt is short and concrete:
- who the bot speaks for ("the citizen service of the city of Bocholt"),
- whom it addresses and how (formal "Sie", plain language),
- what it does when it does not know (point to the contact page instead of guessing),
- what it must not do (legal advice, promises about processing times).
Write it in the language of your website. The setup assistant drafts one from what it read on your site; treat that draft as a starting point.