Documentation Index

Fetch the complete documentation index at: https://knowledge.lightico.com/llms.txt

Use this file to discover all available pages before exploring further.

Sandbox releases

Prev Next

This article lists features, improvements, and bug fixes that are available in sandbox environments only.

Once the features are released to production environments, they are deleted from this article and will appear only in the standard release notes.


Collaboration Room

📂 Agent control over Document Request requirements

Admins can now give agents greater flexibility over how document collection is enforced within a Document Request step. Two new controls are available when enabled by the admin:

  • Minimum required: Agents can set the minimum number of documents a customer must upload before the step is considered complete — defaulting to all selected documents, but adjustable down to zero.

  • Step exclusion: Agents can exclude the Document Request step entirely when document collection isn't needed for a particular customer interaction. When excluded, the customer doesn't see the step and the Workflow continues automatically to the next step.

🪪 More flexible photo ID verification

Photo ID verification Workflow steps now give you more control over how document types are handled — both during verification and in the Workflow logic that follows.

🔬 Control photo ID type matching

Photo ID verification steps now include a Classification validation toggle, so you can set per step how strict verification should be:

  • Toggle on (default) — the document must match the requested type. Existing Workflows behave as before.

  • Toggle off — any authentic supported document continues down the step's pass path, as long as it clears quality and authentication checks.

↗️ Route customers by the identified document type

The document type identified during verification — such as a driver's license, passport, or residence permit — is now available as a system value when building Workflow conditions. Use the IDV Document Classification value to guide customers down the appropriate path based on the document they actually uploaded, even when it differs from the type originally requested.

📎 Optional External Document steps in Workflows

Admins can now configure any External Document step in a Workflow as optional. When a step is marked optional, agents can choose to skip it during the session — and any skipped step is automatically excluded from the customer's view.

⚙️ Control auto-cropping behavior from System Settings

Admins can now enable or disable auto-cropping directly from System Settings, without needing to contact Customer Support. This makes it easy to adjust the setting if auto-cropping isn't producing the expected results.

📐 Set table widths as relative or fixed in Dynamic Documents

You can now set a table's width in a Dynamic Document as a percentage of the screen, in addition to the existing fixed pixel option. A relative width lets short, summary-style tables resize cleanly across mobile and desktop, avoiding horizontal scrolling in mobile-heavy journeys. Fixed pixel widths remain the default and are still the better choice for tables with longer text, which can become cramped at relative widths. Existing tables are unaffected unless you switch them.


Case Manager

👁️ Hide tasks from the agent view based on conditions

A new Hidden behavior option is now available in the case type builder, alongside Read Only and Disabled. When the configured condition is met, the task is removed from the agent's task navigation entirely — not visible, not selectable. When the condition is no longer met, the task reappears automatically.f

🔄 Hit the ground running with a ready-made case lifecycle

Case Manager now initializes new case types with a three-state default lifecycle — In Progress, Completed, and Cancelled — rather than a single bare step. Business configurators have a ready-made starting point for every new case type they create and can build on or adjust the lifecycle from there.

🛠️ Fix customer contact details without restarting the session

The re-engage feature is now available in customer engagement task. Re-engage enables agents to correct a customer's contact details and resend the collaboration session invitation without losing any existing session content.

📬 Case assignment email notifications

Agents in Case Manager can now receive an email notification when a case is assigned or reassigned to them. When enabled, each notification includes:

  • The case title and a direct link to the case

  • A configurable subject line supporting static text and dynamic case values

  • A customizable email body via HTML upload, with a system default available


Document Analyzer

🛠️ Resolve extraction gaps directly in Document Analyzer

Agents can now edit extracted Attribute values directly in Document Analyzer — including entering a value for an Attribute where no extraction point was found, or marking an extracted value as "missing" when the document does not actually contain that data.

Previously, incomplete or inaccurate extractions could cause rules to fail with no way for agents to correct them in context. With this update, agents can resolve these gaps in real time, reducing rule failures caused by missing or incorrect extraction data and avoiding the need for manual workarounds outside the system.

🗂️ Edit and manage your data schema

Business Configurators can now update an existing data schema without deleting and re-uploading it. Changes are made directly in the custom integration hub Data Schema tab, with Attribute mappings preserved throughout. New capabilities include:

  • In-place editing — add, edit, or delete objects and key-value pairs directly in the schema

  • Export schema with mapping — save the schema and its current Attribute bindings as a portable file

  • Import schema with mapping — restore a previously exported schema, including its bindings

  • JSON view toggle — see which Attribute is bound to which key at a glance

🔍 Confirm STP analysis results without making changes

Agents can now submit an STP document analysis package without making changes, formally confirming the automated results were reviewed and accepted. Previously, Submit was only active when a manual override was performed.