WHITE LABEL
The external widget supports multiple themes, title overrides, display modes, and custom theme builds for branded deployments.
The strongest white-label story in PrintSpeak today is around the standalone widget’s visual presentation and deployment options.
Feature family placeholder
Reserved for a dedicated interface preview, workflow diagram, or annotated screenshot.
MATRIX
Preset themes
Includes
Default, solid-color, gradient, neon-glow, and glass-morphism theme variants.
Why it matters
The codebase ships multiple ready-made branded looks instead of a single hard-coded chat skin.
Header title override
Includes
Widget title text is configurable through `data-title`.
Why it matters
This is a simple but real white-label control exposed directly in the embed code.
Auto-open mode
Includes
The widget can open immediately on load rather than starting as a minimized launcher.
Why it matters
This supports different branded launch experiences depending on the host site.
Hidden-toggle mode
Includes
The floating bubble can be removed entirely so the widget opens only from your own buttons or links.
Why it matters
This allows the host application to own the visible entry point into the experience.
Responsive widget states
Includes
Floating, open, expanded, and mobile-fullscreen widget behaviors.
Why it matters
The widget has multiple presentation states that affect how branded embeds feel across devices.
Custom theme build pipeline
Includes
Teams can add a new SCSS theme and rebuild themed CSS assets into `public/agent_standalone`.
Why it matters
This is the factual extension point for deeper visual customization.
Optional bundled styles
Includes
The external docs expose `data-include-styles` as a configurable option.
Why it matters
That gives integrators some control over how much styling the widget injects by default.
External widget preview
Includes
When external use is enabled, the builder exposes an External Widget tab with theme/title settings.
Why it matters
The white-label experience is not only documented; it is configurable inside the enterprise UI.
| Capability | Includes | Why it matters |
|---|---|---|
Preset themes | Default, solid-color, gradient, neon-glow, and glass-morphism theme variants. | The codebase ships multiple ready-made branded looks instead of a single hard-coded chat skin. |
Header title override | Widget title text is configurable through `data-title`. | This is a simple but real white-label control exposed directly in the embed code. |
Auto-open mode | The widget can open immediately on load rather than starting as a minimized launcher. | This supports different branded launch experiences depending on the host site. |
Hidden-toggle mode | The floating bubble can be removed entirely so the widget opens only from your own buttons or links. | This allows the host application to own the visible entry point into the experience. |
Responsive widget states | Floating, open, expanded, and mobile-fullscreen widget behaviors. | The widget has multiple presentation states that affect how branded embeds feel across devices. |
Custom theme build pipeline | Teams can add a new SCSS theme and rebuild themed CSS assets into `public/agent_standalone`. | This is the factual extension point for deeper visual customization. |
Optional bundled styles | The external docs expose `data-include-styles` as a configurable option. | That gives integrators some control over how much styling the widget injects by default. |
External widget preview | When external use is enabled, the builder exposes an External Widget tab with theme/title settings. | The white-label experience is not only documented; it is configurable inside the enterprise UI. |
RELATED FAMILIES
ENTERPRISE FEATURES
The real admin surface centers on agent creation, versioning, import/export, scope controls, and operational configuration inside the enterprise UI.
AUTHENTICATION
The implemented access model centers on agent API keys, signed or encrypted tokens, origin controls, and agent/context resolution.
SDK
The implemented surfaces are a standalone widget script, a JS API, trigger elements, and internal Rails/Stimulus helpers.