Jasser Knows

Authenticated customer support that keeps every conversation verified.

Enforce authenticated customer identifiers so every Jasser Knows conversation stays tied to a known account while maintaining a consistent support interface across your portals.

When to use it

  • Customer dashboards that need contextual answers without leaving the page.
  • Support portals where SLAs depend on the signed-in account tier.
  • Billing and licensing journeys that require an auditable chat transcript.

Payload expectations

  • CHAT_APP_VARIANT=customer when starting the Jasser Knows service.
  • user_id must be present, numeric, and match your CRM record.
  • require_user_id stays true to block anonymous sessions.
  • Use direction to respect Arabic or RTL layouts when needed.

Launch the live widget

Provide a real or sample account identifier. The launcher keeps the iframe hidden until a valid value is supplied to prevent anonymous traffic from reaching the customer persona.

Capture the numeric user id from your authentication session (positive integer).

Embed telemetry

Watch the configuration payloads and acknowledgements to confirm the Jasser Knows iframe and host page remain in sync.

Continue exploring

Production deployment checklist → Switch to public persona → Test the employee flow →