All guides
User

Inbox Live Chat Widget

Screen guide

Before you start

Use the account and workspace that own the relevant records. The feature also needs to be enabled for this installation and plan.

Open this feature
  1. Open /portal/inbox/live-chat-widget on your site.

Steps

Use Create widget

  1. Open /portal/inbox/live-chat-widget on your application domain, using the workspace account for this task.
  2. Select the intended record or item first and review its displayed values. There is no separate input form described for this control.
  3. Select Create widget. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.

Use Save changes

  1. Open /portal/inbox/live-chat-widget on your application domain, using the workspace account for this task.
  2. Find the form containing Launcher label, Position, Accent color. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Save changes. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
Launcher labelRequired. Enter the launcher label for this task, using the help or example shown by the form. Maximum 50 characters.
PositionRequired. Choose Bottom right, Bottom left.
Accent colorRequired. Enter the accent color for this task, using the help or example shown by the form.
Panel titleRequired. Enter the panel title for this task, using the help or example shown by the form. Maximum 80 characters.
Open animationRequired. Enter the open animation for this task, using the help or example shown by the form.
Widget fontRequired. Enter the widget font for this task, using the help or example shown by the form.
Welcome messageRequired. Enter the welcome message for this task, using the help or example shown by the form. Maximum 280 characters.
Composer placeholderRequired. Enter the composer placeholder for this task, using the help or example shown by the form. Maximum 120 characters.
Require visitor nameEnter the require visitor name for this task, using the help or example shown by the form.
Require visitor emailEnter the require visitor email for this task, using the help or example shown by the form.
Assistant nameRequired. Enter the assistant name for this task, using the help or example shown by the form. Maximum 80 characters.
Minimum confidenceRequired. Choose High - stricter threshold, Medium - more answers.
Reply toneRequired. Enter the reply tone for this task, using the help or example shown by the form. Maximum 40 characters.
Reply languageRequired. Enter the reply language for this task, using the help or example shown by the form. Maximum 40 characters.
AI reply limit per conversationRequired. Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 1. Maximum 20.
Only answer from approved Knowledge BaseEnter the only answer from approved knowledge base for this task, using the help or example shown by the form.
Handoff messageRequired. Enter the handoff message for this task, using the help or example shown by the form. Maximum 500 characters.
Human handoff keywordsOptional unless the current form requests it. Enter the human handoff keywords for this task, using the help or example shown by the form. Comma-separated. These always transfer the conversation to your team. Maximum 1000 characters.
Routing modeRequired. Enter the routing mode for this task, using the help or example shown by the form.
Picker titleRequired. Enter the picker title for this task, using the help or example shown by the form. Maximum 120 characters.
RequiredEnter the required for this task, using the help or example shown by the form.
Widget nameRequired. Enter the widget name for this task, using the help or example shown by the form. Maximum 255 characters.
Website URLOptional unless the current form requests it. Enter the complete address required by this field. For a callback or webhook, copy the URL shown by the running application instead of guessing its path. Maximum 500 characters.

Fields and choices

Field descriptions appear beside each task above so that separate forms are not mixed together.

Check the result

  1. Stay in the same account/workspace and reopen the intended record or result screen.
  2. For saved settings, compare the displayed values with the choices you made. For filters and previews, check the current result scope.
  3. For queued or external work, inspect its status/history and provider result where applicable. A successful save does not by itself prove message delivery, publication, payment completion or provider approval.

Common problems

ProblemWhat to check
The screen or action is missingCheck the correct workspace account, role, enabled app and plan. A hidden action is not fixed by typing an internal endpoint.
A field is rejectedRead its validation message, choose from the offered options and check the relevant format or limit. Do not substitute a database ID for a displayed choice.
A list is emptyCheck the selected workspace, search text, date range and status filters. Clear one filter at a time before concluding that records are missing.
A request is still pendingCheck its status/history before repeating it. For messages, publishing, imports and payments, a submitted request can finish later or fail separately.

Technical reference

Role-scoped source references

Pinned commit: 68a5655db1bbe17c74fb211f0fe0ee4e63c8be88

Source-only route information
MethodSource-default route
GET/portal/inbox/live-chat-widget
GET/portal/inbox/live-chat-widget/{widgetId}/test
GET/portal/inbox/live-chat-widget/{widgetId}
GET/integrations/live-chat/widget/{token}.js
GET/integrations/live-chat/widget/{token}/bootstrap
GET/integrations/live-chat/widget/{token}/messages
POST/integrations/live-chat/widget/{token}/messages
POST/integrations/live-chat/widget/{token}/typing
Unmapped fields — not user instructions

These fields belong to this role’s source handler, but their screen labels were not confirmed.

Source keyHandler
launcherIconmodules/Inbox/InboxLiveChatWidget/Livewire/LiveChatWidgetWorkspace.php
launcherStylemodules/Inbox/InboxLiveChatWidget/Livewire/LiveChatWidgetWorkspace.php
launcherImageUrlmodules/Inbox/InboxLiveChatWidget/Livewire/LiveChatWidgetWorkspace.php
headerPatternmodules/Inbox/InboxLiveChatWidget/Livewire/LiveChatWidgetWorkspace.php
accentColormodules/Inbox/InboxLiveChatWidget/Livewire/LiveChatWidgetWorkspace.php
allowedDomainsTextmodules/Inbox/InboxLiveChatWidget/Livewire/LiveChatWidgetWorkspace.php
conversationModemodules/Inbox/InboxLiveChatWidget/Livewire/LiveChatWidgetWorkspace.php
session_idmodules/Inbox/InboxLiveChatWidget/Http/Controllers/LiveChatWidgetPublicController.php
namemodules/Inbox/InboxLiveChatWidget/Http/Controllers/LiveChatWidgetPublicController.php
emailmodules/Inbox/InboxLiveChatWidget/Http/Controllers/LiveChatWidgetPublicController.php
routingmodules/Inbox/InboxLiveChatWidget/Http/Controllers/LiveChatWidgetPublicController.php
after_idmodules/Inbox/InboxLiveChatWidget/Http/Controllers/LiveChatWidgetPublicController.php
bodymodules/Inbox/InboxLiveChatWidget/Http/Controllers/LiveChatWidgetPublicController.php
page_urlmodules/Inbox/InboxLiveChatWidget/Http/Controllers/LiveChatWidgetPublicController.php
preferred_user_idmodules/Inbox/InboxLiveChatWidget/Http/Controllers/LiveChatWidgetPublicController.php
attachmentmodules/Inbox/InboxLiveChatWidget/Http/Controllers/LiveChatWidgetPublicController.php
activemodules/Inbox/InboxLiveChatWidget/Http/Controllers/LiveChatWidgetPublicController.php