Close support case

Overview

The Customer Service Completion Component is a terminal control-state node. Its main function is to formally close an active service ticket in the system and, at the same time, interrupt the execution of the automation flow for the contact in question. It acts as the end of the customer journey, archiving the conversation or interaction and changing the ticket status to resolved or closed.

Configuration Parameters

The component's configuration is used to categorize ticket closure for auditing and management reporting purposes:

• Reason: Dropdown menu used to classify the reason why the service is being closed (e.g., "No response", "Question answered", "Sale completed"). The list of reasons displayed is inherited directly from the closing statuses registered globally in the platform's workspace.

Visual Builder

The interface of this component is designed to be simple and straightforward, graphically marking the end of a logical branch:

• Null Output Node (Terminal): In the visual flow editor, this component acts as an endpoint. It has no connectors or output ports to continue the current flow, since all automation execution for that user is frozen and considered complete after passing through this block.

• Closure Tag Search: The dropdown selector offers an internal text search field to quickly find the correct justification in workspaces that have extensive catalogs of closure reasons.

Special Operators

The logical properties of this component deal with data auditing, session cache cleanup, and performance metric generation (KPIs):

• Channel Cleanup and Release: When processing the closure, the system engine clears the temporary variables from the current session and releases the customer's conversation window. This ensures that, if the user sends a new message in the future, the system treats them as a new contact and restarts the automation tree from scratch (instead of trapping them in old histories).

• Report Metadata Injection (Analytics): The reason selected in this node is injected directly into the platform's Business Intelligence (BI) database. This makes it possible to measure crucial operational metrics, such as the automatic resolution rate (First Contact Resolution - FCR) and the main customer exit bottlenecks.

5. Practical Examples

The table below demonstrates classic application scenarios for this component to close service cycles in an organized way:

Selected Reason	Node Location in the Flow	Automation Context	Practical Use Case
No response	Connected after a wait or inactivity node.	The customer stopped responding to the chatbot for more than 6 hours.	Close the ticket due to inactivity so as not to pollute the company's service time metrics.
Question Answered	Connected in the "Successful Self-Service" branch.	The customer consulted the Knowledge Base and selected "Yes, I solved my problem."	End the flow and the ticket, ensuring the request was resolved via artificial intelligence or FAQ.
Disqualified Lead	Connected after the profile filtering block.	The lead provided information that does not align with the company's sales policy.	End the triage flow immediately, archiving the contact without sending it to the human team.