@lightworkai.official/debug-capture 0.19.3 → 0.19.5

package/README.md

@@ -484,7 +484,14 @@ beside it — แชทกับทีมงาน until the person first opens
 the call's card are drawn in your page's own font (read from `<body>`). The
 panel's head has เปิดในระบบแจ้งปัญหา (0.19.3): the same hand-off as
 `openSupportPortal` — its countdown, signed in, a new tab — to the page the
-panel was on (the chat, the person's tickets, or the one open). Your
+panel was on (the chat, the person's tickets, or the one open). The team can
+call from the chat too, and the person can ask for a call back there (0.19.4):
+the ring card says จากแชทกับทีมงาน instead of a ticket's key, and its fallback
+opens their chat. The bubble's look is the support desk's to set (0.19.5, its
+ปุ่มแชท settings page): its face, colour and words, read with the first answer;
+your own `label` in code still wins. A desk can turn the bubble off for every
+host at once. `chat: { show: () => boolean }` decides per person or per page
+(asked before every read; call `refreshSupportChat()` after a sign-in). Your
 own button instead of ours: `openSupportChat()` /
 `closeSupportChat()`; on a page with no bundler, `data-chat` and
 `data-identity-url` on the script tag, and `window.lwOpenSupportChat()`.

package/dist/config.d.ts

@@ -223,6 +223,12 @@ export interface ChatOptions {
      * of "แชทกับทีมงาน", or `false` for the button alone.
      */
     label?: string | false;
+    /**
+     * Whether the bubble is for whoever is signed in now (0.19.5) — asked before every read; false: no bubble. For a
+     * host whose own staff should not chat with its support desk, or not on every page. Ask again after a sign-in with
+     * `refreshSupportChat()`.
+     */
+    show?: () => boolean;
 }
 /** The bubble's place, from `chat`: null when it is off. */
 export declare function chatPlace(chat: DebugCaptureConfig["chat"]): {