Branding

Friday is a product, not a chrome plate. But she should feel like part of your site. Branding controls cover the things visitors actually see — the name in the chat header, the accent color, the first message, and whether the "Made with Friday" line shows.

Set everything in Dashboard → Website → Appearance.

What you can change

• Chatbot name. Default is "Friday." You can rename her to "Ada", "your concierge", or whatever fits your brand. The name shows in the chat header and in the system prompt — she'll refer to herself by it.
• Accent color. Any hex. Used for the launcher, send button, and confirm bubbles. Friday auto-derives a hover and disabled tint from your accent — pick a color that has enough contrast against white and slate-900.
• Welcome message. The first thing a visitor sees when they open the launcher. Keep it specific to what your site does — "Hi! Ask me anything about our pricing or how to get started." beats "Hello! How can I help?"
• Show branding toggle. Whether the "Made with Friday" line appears under the chat. On by default; off is available on paid plans.

What you can't (yet) change

• The launcher icon — fixed for now.
• The chat font — inherits from the host site where possible; falls back to system-ui.
• The exact phrasing Friday uses in her replies. (That's shaped by your sources, vocabulary, and the prompt template — but not directly typeable.)

Per-host vs workspace

Branding lives at the workspace level. If you run Friday on three sites under one workspace, they all get the same accent and welcome. If each site needs its own look, create one workspace per site (free tier covers it; the 500-message cap is per workspace).

Theme detection

If the script tag has data-theme="auto", the widget follows the visitor's prefers-color-scheme. The accent stays the same in both modes; the chrome around it (panel background, text) inverts. You can force light or dark via the script attribute.