@helpai/elements 0.63.3 → 0.63.5

package/index.d.ts

@@ -427,7 +427,7 @@ interface FeedbackOptions {
  * event(s) and shown as a gate that replaces the composer (locking the chat
  * until submit/skip). Its answers are recorded via one shared submit endpoint.
  * Generic across verticals — there is NO industry logic; a clinic intake, an
- * insurance claim form, a CSAT survey, and a sales lead capture are all just
+ * insurance claim form, a CSAT survey, and a sales signal capture are all just
  * different config.
  *
  * The same {@link FormField} shape powers the AI-driven ask-questions tool.
@@ -987,7 +987,7 @@ interface Endpoints {
   transcribe?: string;
   /**
    * Form submission endpoint. Default: `'/submit-form'`. When any form
-   * (a pre-chat lead capture, a CSAT survey, etc.) is completed, the widget POSTs
+   * (a pre-chat signal capture, a CSAT survey, etc.) is completed, the widget POSTs
    * the captured values here (fire-and-forget), keyed by the same `visitorId` +
    * `conversationId` the conversation uses; the payload carries `formId` + `trigger`
    * so the backend can route. Optional: a backend that doesn't implement it just
@@ -1128,7 +1128,7 @@ interface ChatWidgetOptions {
   footer?: FooterOptions;
   /** Capability flags (file upload, voice mode, tools). Server-pushable. */
   features?: FeatureFlags;
-  /** Event-driven forms (lead capture, CSAT, intake, consent…). Server-pushable. */
+  /** Event-driven forms (signal capture, CSAT, intake, consent…). Server-pushable. */
   forms?: FormsOptions;
   /** Messenger modules (Chat / Home / Messages / Help / News tabs). Server-pushable. */
   modules?: ModulesOptions;