SilentChat

Configuration

After installation, configuration decides how the widget behaves. All settings live per widget in the dashboard under Settings → Widgets.

Branding

So the widget blends into your site:

  • Accent color for header, buttons, and bot avatar.
  • Logo (SVG or PNG, max 64×64 px) shown in the chat header.
  • Position bottom-left or bottom-right, with adjustable viewport offset.

Business hours

Enter your office hours so the widget shows an offline notice instead of an online ping outside those windows. Time zone, weekdays, and holidays are managed separately.

Greeting messages

Online and offline greetings are separate fields and are picked automatically based on current business hours:

{
  "online": "Hi 👋 — wir sind hier. Wie können wir helfen?",
  "offline": "Wir sind gerade offline, antworten aber meist binnen einer Stunde."
}

Consent mode

By default, the widget runs in anonymous visitor mode without personal data — no cookie banner needed. If you need named profiles with email, switch to consent mode and optionally integrate an external consent tool via window.SilentChat.setConsent.

Origin whitelist

List every domain the widget is allowed to run on. Requests from other origins are rejected by the backend — keeps your widget key from being abused on third-party sites.

UX & Engagement

The widget editor's UX & Engagement tab gathers a set of toggles that control launcher behavior, conversion helpers, and comfort features. Defaults are privacy-first — anything with a privacy impact is off by default.

Launcher

  • show_response_time_indicator — Shows an estimated response time (7-day average) as a small pill above the chat bubble. Aggregate value, no PII. Default off.
  • show_agent_identity_in_launcher — Shows the first name and avatar of online agents in the launcher. Each agent must additionally enable public_display in their own profile. Default off (employee PII).

Engagement / conversion

  • exit_intent (Trigger condition) — Fires when the mouse cursor leaves the browser window across the top edge. Use it from the trigger editor to set a context-aware greeting instead of auto-opening the chat.
  • quick_actions — Up to 6 cards on the home screen with the actions chat, kb, external_link, booking_link (allowlist: Calendly, cal.com, SavvyCal, TidyCal, Acuity), email (mailto), or prefilled_chat (pre-filled composer text).
  • enable_persistent_resume — Persistent chat resume across 30 days using a signed token (HMAC-SHA256) plus an email hash. GDPR-relevant — default off. See the GDPR doc for details.

Comfort

  • enable_drag_and_drop_upload — Drag and drop a file onto the chat window to trigger the same upload path as the paperclip button. Default on.
  • enable_sound_toggle_in_footer — Bell icon in the chat header to mute notification sounds per session. Persisted in localStorage. Default on.
  • enable_open_hotkey — Opens the widget with / or Ctrl+K. Suppressed inside inputs/textareas/contenteditable. Default off because / collides with site-search shortcuts on some sites.
  • enable_mobile_swipe_close — On mobile (≤480px), visitors can swipe the widget away: floating downward, side_panel-right to the right, side_panel-left to the left. Default on.

Agent tools

In the agent composer, the calendar button opens a dialog where you paste a Calendly/cal.com/SavvyCal/TidyCal/Acuity link. The visitor sees a booking card with a click-through CTA instead of a bare link. The backend enforces an allowlist of hosts and HTTPS.

GDPR note: enable_persistent_resume and show_agent_identity_in_launcher are the only switches with a substantive privacy impact. Enable them only alongside an updated privacy policy and an appropriate consent-banner mention.

Configuration | SilentChat