@getnexorai/sdk 0.1.2 → 0.1.4

package/dist/{config-khGNZDHI.d.cts → config-C39P5Aax.d.cts}

@@ -77,6 +77,8 @@ interface WorkflowRunStub {
 interface CreateLeadResponse {
     success: true;
     lead: Lead;
+    /** True when an existing lead was matched/merged (vs. a brand-new insert). */
+    existed?: boolean;
     workflow_run?: WorkflowRunStub;
     force_first_message?: {
         sent: boolean;
@@ -336,6 +338,20 @@ declare class NexorClient {
     createMeeting(input: CreateMeetingInput, options?: RequestOptions): Promise<unknown>;
     /** Push a note-taker transcript / summary / action items to a meeting. */
     createMeetingNotes(input: MeetingNotesInput, options?: RequestOptions): Promise<unknown>;
+    /**
+     * Fetch the dashboard-authored web-chat config for a workflow. Backed by
+     * GET /api/public/chat/config. The widget calls this once on init to learn
+     * whether web chat is enabled and to get the static opening message
+     * (`initial_message`, a RAW template that may contain {{variables}} — the
+     * widget substitutes them client-side before painting the greeting).
+     *
+     * Most users will not call this directly — `initChat()` handles it.
+     */
+    getChatConfig(workflowId: UUID, options?: RequestOptions): Promise<{
+        success: true;
+        enabled: boolean;
+        initial_message: string | null;
+    }>;
     /**
      * Send a turn in a browser-embedded chat session. Backed by
      * POST /api/public/chat on the Nexor API.
@@ -348,6 +364,16 @@ declare class NexorClient {
         message: string;
         system_prompt?: string;
         client_prompt?: string;
+        /** The opening message the widget actually displayed (keeps the agent's
+         *  <webchat_opening> in sync with a per-page override). */
+        opening_shown?: string;
+        /** Start over as a brand-new lead: the API skips email/phone/session
+         *  matching and mints a fresh lead with no prior conversation context. */
+        new_lead?: boolean;
+        /** Keep the same lead but start a fresh conversation episode: the API
+         *  deactivates the prior run + thread and clears this workflow's collected
+         *  variables, so the agent sees no prior context. */
+        reset_episode?: boolean;
         lead?: {
             first_name?: string;
             last_name?: string;
@@ -362,6 +388,53 @@ declare class NexorClient {
         session_id: string;
         lead_id?: UUID;
         workflow_run_id?: UUID;
+        /** True when the API recognised an existing lead (returning visitor). */
+        matched_existing?: boolean;
+    }>;
+    /**
+     * Create (or upsert) a lead from the web chat widget and force its FIRST
+     * contact to go out on a chosen channel — used when a visitor clicks
+     * "call me" / "email me" instead of opening the chat. Backed by
+     * POST /api/public/leads with `force_first_channel`.
+     *
+     * Unlike a literal `force_first_message`, `force_first_channel` pins the
+     * channel and lets the workflow's own agent compose the first outreach. The
+     * `metadata` you pass (page URL, requested channel, a note that the visitor
+     * asked to be contacted from the website) is stored on the lead so the agent
+     * has that context.
+     *
+     * Most users will not call this directly — `initChat()`'s contact-request
+     * form handles it.
+     */
+    requestContact(input: {
+        workflow_id: UUID;
+        first_name?: string;
+        last_name?: string;
+        email?: string;
+        phone?: string;
+        /** Force the first contact onto this channel (agent composes the message). */
+        force_first_channel: "call" | "email" | "whatsapp";
+        /** Context stored on the lead (page URL, requested channel, free-form note). */
+        metadata?: Record<string, unknown>;
+        /** Lead source label. Defaults to "web-chat" server-side handling. */
+        source?: string;
+    }, options?: RequestOptions): Promise<{
+        success: true;
+        lead: {
+            id: UUID;
+            first_name?: string;
+            email?: string;
+            phone?: string;
+        };
+        existed?: boolean;
+        workflow_run?: {
+            id: UUID;
+        };
+        force_first_channel?: {
+            channel: string;
+            applied: boolean;
+        };
+        warning?: string;
     }>;
 }
 
@@ -378,19 +451,111 @@ interface ChatLeadCapture {
     fields?: Array<"first_name" | "last_name" | "email" | "phone">;
     /** "before" gates chat behind the form; "skip" never asks. Default "before". */
     mode?: "before" | "skip";
-    /** Label rendered above the form. */
+    /** Create the lead in Nexor the INSTANT the form is submitted (via POST
+     *  /leads), instead of waiting for the visitor's first chat message. Captures
+     *  visitors who fill the form but never send a message. Default false. */
+    createLeadOnSubmit?: boolean;
+    /** Heading rendered above the form (its own view). */
     label?: string;
     /** Submit button label. */
     submitLabel?: string;
+    /** Per-field placeholder overrides (for localization). */
+    placeholders?: Partial<Record<"first_name" | "last_name" | "email" | "phone", string>>;
+    /** Default country for the phone field — a dial code ("+56") or ISO ("CL").
+     *  Sets the initial flag, prefix and max length. */
+    phoneCountryCode?: string;
+    /** Restrict the phone country selector to these ISO codes (e.g. ["CL","AR"]),
+     *  in this order. Omit to offer the full built-in list. */
+    phoneCountries?: string[];
+    /** Validation error copy (for localization). */
+    errorMessages?: {
+        required?: string;
+        email?: string;
+        phone?: string;
+    };
+}
+/** The actions that can appear in the hover/speed-dial fan above the launcher. */
+type ChatChannelKey = "whatsapp" | "call" | "email" | "instagram" | "chat";
+/** Channels that can open the in-widget contact-request form. */
+type ContactRequestChannel = "call" | "email" | "whatsapp";
+/**
+ * Turns the `call` / `email` (optionally `whatsapp`) fan buttons into an
+ * in-widget contact-request FORM instead of a tel:/mailto: link. The visitor
+ * fills name + email + phone, and on submit the widget creates a lead in Nexor
+ * and forces the FIRST contact to go out on that channel (the workflow's agent
+ * composes the message), with context that they requested it from the website.
+ *
+ * All copy is per-channel so it can be localized; sensible English defaults
+ * apply when omitted.
+ */
+interface ChatRequestContact {
+    /** Fan channels that open the form instead of navigating. Default ["call","email"]. */
+    channels?: ContactRequestChannel[];
+    /** Heading above the form, per channel. */
+    title?: Partial<Record<ContactRequestChannel, string>>;
+    /** Explainer line (e.g. "we need this info to contact you"), per channel. */
+    subtitle?: Partial<Record<ContactRequestChannel, string>>;
+    /** Submit button label, per channel. */
+    submitLabel?: Partial<Record<ContactRequestChannel, string>>;
+    /** Confirmation shown after a successful request, per channel. */
+    successText?: Partial<Record<ContactRequestChannel, string>>;
+    /** Label for the button that dismisses the success screen. Default "Done". */
+    doneLabel?: string;
+    /** Error shown when the request fails. */
+    errorText?: string;
+}
+/**
+ * Optional "speed-dial" channels shown when the visitor hovers (desktop) or taps
+ * (touch) the launcher bubble. Instead of opening the chat immediately, the
+ * launcher fans out a column of round buttons — WhatsApp, call, email, Instagram,
+ * and an "open chat" button — letting the visitor pick a channel.
+ *
+ * If only `chat` would be enabled (no other channel supplied), the fan is skipped
+ * and the launcher keeps its default behaviour (click opens the chat).
+ */
+interface ChatChannels {
+    /** WhatsApp number in international format (e.g. "+56912345678"). Opens wa.me. */
+    whatsapp?: string;
+    /** Pre-filled WhatsApp message text. */
+    whatsappText?: string;
+    /** Phone number for the call button (e.g. "+56912345678"). Opens tel:. */
+    call?: string;
+    /** Email address. Opens mailto:. */
+    email?: string;
+    /** Instagram handle ("nexor.ai") or full profile URL. */
+    instagram?: string;
+    /** Include a button that opens the chat panel. Defaults to true. */
+    chat?: boolean;
+    /** Top-to-bottom order of the fan buttons. Defaults to the order below. */
+    order?: ChatChannelKey[];
+    /** Accessible labels / hover tooltips per channel. */
+    labels?: Partial<Record<ChatChannelKey, string>>;
+    /** Turn `call`/`email` (and optionally `whatsapp`) into an in-widget
+     *  contact-request form that creates a lead and forces first contact on that
+     *  channel, instead of opening a tel:/mailto: link. Omit to keep magic links. */
+    requestContact?: ChatRequestContact;
 }
 interface ChatInitOptions {
     /** Workflow that handles this chat conversation. Required. */
     workflowId: UUID;
     title?: string;
     subtitle?: string;
+    /**
+     * Force the opening message for this widget instance. Highest priority —
+     * WINS over the dashboard `initial_message` and over `greeting`. Use it for
+     * per-page openings (e.g. an ecommerce-specific greeting on /ecommerce).
+     * Supports the same {{first_name}} / {{last_name}} / {{full_name}} / {{email}}
+     * / {{phone}} tokens, substituted from the captured/known lead.
+     */
+    openingMessage?: string;
+    /** Fallback opening, used only when neither `openingMessage` nor the
+     *  dashboard `initial_message` is set. */
     greeting?: string;
     /** Shown when a turn fails or the server returns no reply. */
     errorText?: string;
+    /** Shown when web chat is disabled for the workflow (channel turned off in
+     *  the dashboard, or the API reports it unavailable). */
+    disabledText?: string;
     /** BCP-47 locale for timestamps (e.g. "es", "en-US"). Defaults to the browser. */
     locale?: string;
     /** Hex colour for bubble + accents. Defaults to #111827. */
@@ -399,12 +564,32 @@ interface ChatInitOptions {
     accentTextColor?: string;
     /** Show the "Powered by Nexor" footer. Defaults to true. */
     showBranding?: boolean;
+    /** Composer placeholder once chat is active. Default "Type a message…". */
+    inputPlaceholder?: string;
+    /** Show a header "start over" control that wipes the conversation and starts a
+     *  BRAND-NEW lead (the backend won't re-match the old one). Default true. */
+    showRestart?: boolean;
+    /** aria-label / tooltip for the header restart control. Default "Start over". */
+    restartLabel?: string;
     position?: "bottom-right" | "bottom-left";
     /** Auto-open the panel on first load. Defaults to false. */
     openOnLoad?: boolean;
+    /**
+     * Turn the launcher into a hover/tap "speed-dial" that fans out channel
+     * buttons (WhatsApp, call, email, Instagram, chat) instead of opening the
+     * chat right away. Omit for the classic click-to-open launcher.
+     */
+    channels?: ChatChannels;
     /** Coalesce rapid-fire messages: wait this many ms of quiet, then send the
      *  buffered messages as one combined turn. Defaults to 700. 0 = per message. */
     debounceMs?: number;
+    /** Split a bot reply into separate bubbles on blank lines (paragraph breaks),
+     *  WhatsApp-style. Defaults to true. Set false to keep one bubble per reply. */
+    splitReplies?: boolean;
+    /** Fixed typing pause (ms) shown between split bubbles. Omit for a natural
+     *  3000–5000ms pause scaled by the length of the next message (longer text
+     *  reads as more time spent typing). */
+    splitDelayMs?: number;
     /** Per-turn request timeout (ms). Agent turns can legitimately take 10-20s,
      *  so this is generous (default 60000). Chat turns never retry — a timeout
      *  surfaces the error once rather than re-sending the message. */
@@ -422,8 +607,18 @@ interface ChatInitOptions {
         metadata?: Record<string, unknown>;
     };
     capture?: ChatLeadCapture;
-    /** Arbitrary metadata passed with each turn (page URL, UTM, …). */
-    metadata?: Record<string, unknown>;
+    /** Arbitrary metadata passed with each turn (page URL, UTM, …). Pass a
+     *  FUNCTION to have it resolved fresh on every turn — useful for SPA values
+     *  that change without re-mounting the widget (e.g. the current route). */
+    metadata?: Record<string, unknown> | (() => Record<string, unknown> | undefined);
+    /** Banner text when a prior conversation is restored but we have no name.
+     *  Default "Continuing your conversation". */
+    resumeText?: string;
+    /** Banner text when we know the visitor. `{name}` is replaced with their
+     *  first name (or email / phone as a fallback). Default "Continuing as {name}". */
+    resumeWithNameText?: string;
+    /** Label for the reset action in the resume banner. Default "Start over". */
+    startOverText?: string;
     onOpen?: () => void;
     onClose?: () => void;
     onMessage?: (msg: {
@@ -445,4 +640,4 @@ interface ChatHandle {
     getSessionId(): string;
 }
 
-export { type AutomationInput as A, type BulkResultEntry as B, type Campaign as C, type ForceFirstMessage as F, type GetLeadHistoryParams as G, type ISODateString as I, type Lead as L, type MeetingNotesInput as M, NexorClient as N, type RequestOptions as R, type SendMessageInput as S, type UUID as U, type WhatsAppTemplate as W, type ChatHandle as a, type ChatInitOptions as b, type ChatLeadCapture as c, type ClientOptions as d, type CreateLeadBulkResponse as e, type CreateLeadInput as f, type CreateLeadResponse as g, type CreateMeetingInput as h, type GetLeadHistoryResponse as i, type GetLeadResponse as j, type IsPausedResponse as k, type LeadHistoryItem as l, type ListTemplatesParams as m, type ResumeAutomationInput as n, type SyncTagsInput as o, type SyncTagsResponse as p, type Workflow as q, type WorkflowRunStub as r };
+export { type AutomationInput as A, type BulkResultEntry as B, type Campaign as C, type ForceFirstMessage as F, type GetLeadHistoryParams as G, type ISODateString as I, type Lead as L, type MeetingNotesInput as M, NexorClient as N, type RequestOptions as R, type SendMessageInput as S, type UUID as U, type WhatsAppTemplate as W, type ChatChannelKey as a, type ChatChannels as b, type ChatHandle as c, type ChatInitOptions as d, type ChatLeadCapture as e, type ClientOptions as f, type CreateLeadBulkResponse as g, type CreateLeadInput as h, type CreateLeadResponse as i, type CreateMeetingInput as j, type GetLeadHistoryResponse as k, type GetLeadResponse as l, type IsPausedResponse as m, type LeadHistoryItem as n, type ListTemplatesParams as o, type ResumeAutomationInput as p, type SyncTagsInput as q, type SyncTagsResponse as r, type Workflow as s, type WorkflowRunStub as t };

package/dist/{config-khGNZDHI.d.ts → config-C39P5Aax.d.ts}

@@ -77,6 +77,8 @@ interface WorkflowRunStub {
 interface CreateLeadResponse {
     success: true;
     lead: Lead;
+    /** True when an existing lead was matched/merged (vs. a brand-new insert). */
+    existed?: boolean;
     workflow_run?: WorkflowRunStub;
     force_first_message?: {
         sent: boolean;
@@ -336,6 +338,20 @@ declare class NexorClient {
     createMeeting(input: CreateMeetingInput, options?: RequestOptions): Promise<unknown>;
     /** Push a note-taker transcript / summary / action items to a meeting. */
     createMeetingNotes(input: MeetingNotesInput, options?: RequestOptions): Promise<unknown>;
+    /**
+     * Fetch the dashboard-authored web-chat config for a workflow. Backed by
+     * GET /api/public/chat/config. The widget calls this once on init to learn
+     * whether web chat is enabled and to get the static opening message
+     * (`initial_message`, a RAW template that may contain {{variables}} — the
+     * widget substitutes them client-side before painting the greeting).
+     *
+     * Most users will not call this directly — `initChat()` handles it.
+     */
+    getChatConfig(workflowId: UUID, options?: RequestOptions): Promise<{
+        success: true;
+        enabled: boolean;
+        initial_message: string | null;
+    }>;
     /**
      * Send a turn in a browser-embedded chat session. Backed by
      * POST /api/public/chat on the Nexor API.
@@ -348,6 +364,16 @@ declare class NexorClient {
         message: string;
         system_prompt?: string;
         client_prompt?: string;
+        /** The opening message the widget actually displayed (keeps the agent's
+         *  <webchat_opening> in sync with a per-page override). */
+        opening_shown?: string;
+        /** Start over as a brand-new lead: the API skips email/phone/session
+         *  matching and mints a fresh lead with no prior conversation context. */
+        new_lead?: boolean;
+        /** Keep the same lead but start a fresh conversation episode: the API
+         *  deactivates the prior run + thread and clears this workflow's collected
+         *  variables, so the agent sees no prior context. */
+        reset_episode?: boolean;
         lead?: {
             first_name?: string;
             last_name?: string;
@@ -362,6 +388,53 @@ declare class NexorClient {
         session_id: string;
         lead_id?: UUID;
         workflow_run_id?: UUID;
+        /** True when the API recognised an existing lead (returning visitor). */
+        matched_existing?: boolean;
+    }>;
+    /**
+     * Create (or upsert) a lead from the web chat widget and force its FIRST
+     * contact to go out on a chosen channel — used when a visitor clicks
+     * "call me" / "email me" instead of opening the chat. Backed by
+     * POST /api/public/leads with `force_first_channel`.
+     *
+     * Unlike a literal `force_first_message`, `force_first_channel` pins the
+     * channel and lets the workflow's own agent compose the first outreach. The
+     * `metadata` you pass (page URL, requested channel, a note that the visitor
+     * asked to be contacted from the website) is stored on the lead so the agent
+     * has that context.
+     *
+     * Most users will not call this directly — `initChat()`'s contact-request
+     * form handles it.
+     */
+    requestContact(input: {
+        workflow_id: UUID;
+        first_name?: string;
+        last_name?: string;
+        email?: string;
+        phone?: string;
+        /** Force the first contact onto this channel (agent composes the message). */
+        force_first_channel: "call" | "email" | "whatsapp";
+        /** Context stored on the lead (page URL, requested channel, free-form note). */
+        metadata?: Record<string, unknown>;
+        /** Lead source label. Defaults to "web-chat" server-side handling. */
+        source?: string;
+    }, options?: RequestOptions): Promise<{
+        success: true;
+        lead: {
+            id: UUID;
+            first_name?: string;
+            email?: string;
+            phone?: string;
+        };
+        existed?: boolean;
+        workflow_run?: {
+            id: UUID;
+        };
+        force_first_channel?: {
+            channel: string;
+            applied: boolean;
+        };
+        warning?: string;
     }>;
 }
 
@@ -378,19 +451,111 @@ interface ChatLeadCapture {
     fields?: Array<"first_name" | "last_name" | "email" | "phone">;
     /** "before" gates chat behind the form; "skip" never asks. Default "before". */
     mode?: "before" | "skip";
-    /** Label rendered above the form. */
+    /** Create the lead in Nexor the INSTANT the form is submitted (via POST
+     *  /leads), instead of waiting for the visitor's first chat message. Captures
+     *  visitors who fill the form but never send a message. Default false. */
+    createLeadOnSubmit?: boolean;
+    /** Heading rendered above the form (its own view). */
     label?: string;
     /** Submit button label. */
     submitLabel?: string;
+    /** Per-field placeholder overrides (for localization). */
+    placeholders?: Partial<Record<"first_name" | "last_name" | "email" | "phone", string>>;
+    /** Default country for the phone field — a dial code ("+56") or ISO ("CL").
+     *  Sets the initial flag, prefix and max length. */
+    phoneCountryCode?: string;
+    /** Restrict the phone country selector to these ISO codes (e.g. ["CL","AR"]),
+     *  in this order. Omit to offer the full built-in list. */
+    phoneCountries?: string[];
+    /** Validation error copy (for localization). */
+    errorMessages?: {
+        required?: string;
+        email?: string;
+        phone?: string;
+    };
+}
+/** The actions that can appear in the hover/speed-dial fan above the launcher. */
+type ChatChannelKey = "whatsapp" | "call" | "email" | "instagram" | "chat";
+/** Channels that can open the in-widget contact-request form. */
+type ContactRequestChannel = "call" | "email" | "whatsapp";
+/**
+ * Turns the `call` / `email` (optionally `whatsapp`) fan buttons into an
+ * in-widget contact-request FORM instead of a tel:/mailto: link. The visitor
+ * fills name + email + phone, and on submit the widget creates a lead in Nexor
+ * and forces the FIRST contact to go out on that channel (the workflow's agent
+ * composes the message), with context that they requested it from the website.
+ *
+ * All copy is per-channel so it can be localized; sensible English defaults
+ * apply when omitted.
+ */
+interface ChatRequestContact {
+    /** Fan channels that open the form instead of navigating. Default ["call","email"]. */
+    channels?: ContactRequestChannel[];
+    /** Heading above the form, per channel. */
+    title?: Partial<Record<ContactRequestChannel, string>>;
+    /** Explainer line (e.g. "we need this info to contact you"), per channel. */
+    subtitle?: Partial<Record<ContactRequestChannel, string>>;
+    /** Submit button label, per channel. */
+    submitLabel?: Partial<Record<ContactRequestChannel, string>>;
+    /** Confirmation shown after a successful request, per channel. */
+    successText?: Partial<Record<ContactRequestChannel, string>>;
+    /** Label for the button that dismisses the success screen. Default "Done". */
+    doneLabel?: string;
+    /** Error shown when the request fails. */
+    errorText?: string;
+}
+/**
+ * Optional "speed-dial" channels shown when the visitor hovers (desktop) or taps
+ * (touch) the launcher bubble. Instead of opening the chat immediately, the
+ * launcher fans out a column of round buttons — WhatsApp, call, email, Instagram,
+ * and an "open chat" button — letting the visitor pick a channel.
+ *
+ * If only `chat` would be enabled (no other channel supplied), the fan is skipped
+ * and the launcher keeps its default behaviour (click opens the chat).
+ */
+interface ChatChannels {
+    /** WhatsApp number in international format (e.g. "+56912345678"). Opens wa.me. */
+    whatsapp?: string;
+    /** Pre-filled WhatsApp message text. */
+    whatsappText?: string;
+    /** Phone number for the call button (e.g. "+56912345678"). Opens tel:. */
+    call?: string;
+    /** Email address. Opens mailto:. */
+    email?: string;
+    /** Instagram handle ("nexor.ai") or full profile URL. */
+    instagram?: string;
+    /** Include a button that opens the chat panel. Defaults to true. */
+    chat?: boolean;
+    /** Top-to-bottom order of the fan buttons. Defaults to the order below. */
+    order?: ChatChannelKey[];
+    /** Accessible labels / hover tooltips per channel. */
+    labels?: Partial<Record<ChatChannelKey, string>>;
+    /** Turn `call`/`email` (and optionally `whatsapp`) into an in-widget
+     *  contact-request form that creates a lead and forces first contact on that
+     *  channel, instead of opening a tel:/mailto: link. Omit to keep magic links. */
+    requestContact?: ChatRequestContact;
 }
 interface ChatInitOptions {
     /** Workflow that handles this chat conversation. Required. */
     workflowId: UUID;
     title?: string;
     subtitle?: string;
+    /**
+     * Force the opening message for this widget instance. Highest priority —
+     * WINS over the dashboard `initial_message` and over `greeting`. Use it for
+     * per-page openings (e.g. an ecommerce-specific greeting on /ecommerce).
+     * Supports the same {{first_name}} / {{last_name}} / {{full_name}} / {{email}}
+     * / {{phone}} tokens, substituted from the captured/known lead.
+     */
+    openingMessage?: string;
+    /** Fallback opening, used only when neither `openingMessage` nor the
+     *  dashboard `initial_message` is set. */
     greeting?: string;
     /** Shown when a turn fails or the server returns no reply. */
     errorText?: string;
+    /** Shown when web chat is disabled for the workflow (channel turned off in
+     *  the dashboard, or the API reports it unavailable). */
+    disabledText?: string;
     /** BCP-47 locale for timestamps (e.g. "es", "en-US"). Defaults to the browser. */
     locale?: string;
     /** Hex colour for bubble + accents. Defaults to #111827. */
@@ -399,12 +564,32 @@ interface ChatInitOptions {
     accentTextColor?: string;
     /** Show the "Powered by Nexor" footer. Defaults to true. */
     showBranding?: boolean;
+    /** Composer placeholder once chat is active. Default "Type a message…". */
+    inputPlaceholder?: string;
+    /** Show a header "start over" control that wipes the conversation and starts a
+     *  BRAND-NEW lead (the backend won't re-match the old one). Default true. */
+    showRestart?: boolean;
+    /** aria-label / tooltip for the header restart control. Default "Start over". */
+    restartLabel?: string;
     position?: "bottom-right" | "bottom-left";
     /** Auto-open the panel on first load. Defaults to false. */
     openOnLoad?: boolean;
+    /**
+     * Turn the launcher into a hover/tap "speed-dial" that fans out channel
+     * buttons (WhatsApp, call, email, Instagram, chat) instead of opening the
+     * chat right away. Omit for the classic click-to-open launcher.
+     */
+    channels?: ChatChannels;
     /** Coalesce rapid-fire messages: wait this many ms of quiet, then send the
      *  buffered messages as one combined turn. Defaults to 700. 0 = per message. */
     debounceMs?: number;
+    /** Split a bot reply into separate bubbles on blank lines (paragraph breaks),
+     *  WhatsApp-style. Defaults to true. Set false to keep one bubble per reply. */
+    splitReplies?: boolean;
+    /** Fixed typing pause (ms) shown between split bubbles. Omit for a natural
+     *  3000–5000ms pause scaled by the length of the next message (longer text
+     *  reads as more time spent typing). */
+    splitDelayMs?: number;
     /** Per-turn request timeout (ms). Agent turns can legitimately take 10-20s,
      *  so this is generous (default 60000). Chat turns never retry — a timeout
      *  surfaces the error once rather than re-sending the message. */
@@ -422,8 +607,18 @@ interface ChatInitOptions {
         metadata?: Record<string, unknown>;
     };
     capture?: ChatLeadCapture;
-    /** Arbitrary metadata passed with each turn (page URL, UTM, …). */
-    metadata?: Record<string, unknown>;
+    /** Arbitrary metadata passed with each turn (page URL, UTM, …). Pass a
+     *  FUNCTION to have it resolved fresh on every turn — useful for SPA values
+     *  that change without re-mounting the widget (e.g. the current route). */
+    metadata?: Record<string, unknown> | (() => Record<string, unknown> | undefined);
+    /** Banner text when a prior conversation is restored but we have no name.
+     *  Default "Continuing your conversation". */
+    resumeText?: string;
+    /** Banner text when we know the visitor. `{name}` is replaced with their
+     *  first name (or email / phone as a fallback). Default "Continuing as {name}". */
+    resumeWithNameText?: string;
+    /** Label for the reset action in the resume banner. Default "Start over". */
+    startOverText?: string;
     onOpen?: () => void;
     onClose?: () => void;
     onMessage?: (msg: {
@@ -445,4 +640,4 @@ interface ChatHandle {
     getSessionId(): string;
 }
 
-export { type AutomationInput as A, type BulkResultEntry as B, type Campaign as C, type ForceFirstMessage as F, type GetLeadHistoryParams as G, type ISODateString as I, type Lead as L, type MeetingNotesInput as M, NexorClient as N, type RequestOptions as R, type SendMessageInput as S, type UUID as U, type WhatsAppTemplate as W, type ChatHandle as a, type ChatInitOptions as b, type ChatLeadCapture as c, type ClientOptions as d, type CreateLeadBulkResponse as e, type CreateLeadInput as f, type CreateLeadResponse as g, type CreateMeetingInput as h, type GetLeadHistoryResponse as i, type GetLeadResponse as j, type IsPausedResponse as k, type LeadHistoryItem as l, type ListTemplatesParams as m, type ResumeAutomationInput as n, type SyncTagsInput as o, type SyncTagsResponse as p, type Workflow as q, type WorkflowRunStub as r };
+export { type AutomationInput as A, type BulkResultEntry as B, type Campaign as C, type ForceFirstMessage as F, type GetLeadHistoryParams as G, type ISODateString as I, type Lead as L, type MeetingNotesInput as M, NexorClient as N, type RequestOptions as R, type SendMessageInput as S, type UUID as U, type WhatsAppTemplate as W, type ChatChannelKey as a, type ChatChannels as b, type ChatHandle as c, type ChatInitOptions as d, type ChatLeadCapture as e, type ClientOptions as f, type CreateLeadBulkResponse as g, type CreateLeadInput as h, type CreateLeadResponse as i, type CreateMeetingInput as j, type GetLeadHistoryResponse as k, type GetLeadResponse as l, type IsPausedResponse as m, type LeadHistoryItem as n, type ListTemplatesParams as o, type ResumeAutomationInput as p, type SyncTagsInput as q, type SyncTagsResponse as r, type Workflow as s, type WorkflowRunStub as t };