Agents
Branding the chat widget, launcher placement, colors, typography, accessibility defaults, and hosted help URLs when you cannot embed yet.
Customer-facing chat should feel native to your site: colors, corners, and copy that match your design system. FlexyAgents exposes appearance settings per agent so marketing iterations do not require redeploying your app.
Hosted help URLs let you pilot assistants on campaigns or microsites before engineering schedules a full embed.
Choose launcher position and iconography consistent with mobile and desktop breakpoints. Verify the widget does not cover critical CTAs or cookie banners.
Set default open/closed behavior per audience: marketing pages may auto-open cautiously; logged-in apps may prefer click-to-open.
Map widget colors to accessible contrast ratios; rely on theme tokens where possible so dark mode and high-contrast user settings remain legible.
Custom fonts should load on the host page before the widget paints to avoid FOUT that looks like broken styling.
Hosted pages inherit agent branding and are useful when CMS access blocks script tags. Track them in analytics as first-class entry points.
When graduating to embeds, keep hosted URLs live for old campaigns that still link to them.
Continue exploring
Platform features · HTTP API & webhooks · Quickstart · Contact
Build on your stack
Start a trial or talk to us about rollout, governance, and enterprise requirements.