Make it yours, then stop tweaking.

What you can change

• Primary color — launcher, header, visitor bubbles, and focus states. Pick anything readable; HAL derives tints from it.
• Position — bottom-right or bottom-left, with independent edge offsets for horizontal and vertical placement.
• Button shape and size — circle, rounded, or square; normal or small.
• Theme — light, dark, or follow the visitor's system, plus an optional in-widget theme switcher so visitors choose.
• Teaser bubble — a short message next to the launcher before the first open. Great for "Questions? We reply in minutes."
• Agent names — show or hide agent names on messages.
• Conversation list — returning visitors see their previous conversations instead of a blank slate.

Greetings that actually fire

The greeting isn't a static string — it's your first automation. Create a first message automation to greet visitors, or a page visit automation to open specific URLs with context ("Working on pricing? Ask us about volume discounts."). Automations support locale-aware copy and frequency caps.

Accessibility defaults

The widget ships with keyboard navigation, focus states, and readable contrast out of the box. If your primary color fails contrast on white, HAL darkens text overlays automatically — but pick a color with at least 4.5:1 contrast on white for best results.

Recommendations

• Match your brand, not your exact hex — if your brand color is dark or muddy, use its brightest accessible variant.
• Keep the launcher clear of cookie banners — offset it above common consent-tool positions.
• Write teasers in the visitor's language — automations pick the locale automatically; static teasers are single-language.
• Enable the theme switcher if your audience is developers — they will use it.

White-label

On Pro and above the "Powered by HAL" badge is removed; Business adds a custom domain for the widget assets and hosted help center, so everything loads from your domain. See pricing for what's included per plan.