Web Widget

The Wistfare web widget is the planned drop-in option for teams that want an embedded customer-facing surface instead of building their own UI on top of the server SDKs.

What the Web Widget Is Meant to Do

• Add a floating support or checkout entry point to any website.
• Start chat or guided support sessions without exposing your API key in the browser.
• Use a short-lived widget session issued by your backend or a Wistfare widget bootstrap endpoint.
• Keep branding, launcher placement, and welcome copy configurable per business.

Recommended Production Pattern Today

Until the hosted widget is published, the safest web integration looks like this:

1. Your frontend opens your own support, checkout, or help UI.
2. Your backend talks to Wistfare through a server SDK.
3. Your backend returns only the data your web app needs.
4. Wistfare API keys stay on trusted infrastructure instead of the browser.

Planned Embed Model

When the widget ships publicly, the intended web flow is:

1. Load a lightweight hosted script.
2. Initialize it with a business identifier and a short-lived session.
3. Let the widget manage real-time transport, UI state, and feature flags.
4. Receive lifecycle callbacks in the host page for analytics or navigation updates.

What to Document in Your App

If you are designing for a future widget rollout, prepare these integration decisions now:

• Which pages should expose the widget launcher.
• Whether the widget should appear as support, sales, or checkout assistance.
• Which user context fields your backend can safely attach to a widget session.
• Which analytics events you want to mirror into your product telemetry.

Best Next Step

Use Backend SDK installation and usage for the real integration path available today, then keep this page as your reference for the future hosted web surface.