Handling Different Logic When AI Customer Service Goes Offline in Special Scenarios | Best Practices

In real-world AI customer service scenarios, situations such as customer complaints or payment requests may require a timely handover to a human agent. Although the standard “Handover Conditions” can take the AI offline, they often only send a generic script and make it difficult to trace the specific reason for the handover.

This article introduces two implementation methods, focusing on how to achieve scenario-based replies, automatic handovers, and reason logging by using the “Special Case Handling” AI Skill + the “Handover” MCP Tool.

I. Standard Method: Configuring “Handover Conditions”

The most direct approach is to configure special conditions that trigger a handover within the AI’s “Guidelines”.

When a customer triggers these conditions, the AI goes offline and sends the “Handover Script” pre-set in the “Basic Configuration”.

This method is simple to configure, but has two obvious limitations:

  1. Fixed response content. After the AI goes offline, it no longer generates new scripts for the current situation and only sends the uniform handover message from the basic configuration. For example, using the same handover script for a customer complaint and a customer preparing to make a payment may not yield optimal communication results.
  2. Unclear handover reasons. Relying solely on this method makes it difficult to determine which specific “Handover Condition” was triggered, and it is inconvenient for post-event statistics and troubleshooting.

II. Recommended Method: AI Skill + MCP Handover Tool

A more flexible approach is to delegate the identification and handling of special scenarios to a separate AI skill, which then calls the handover tool.

When a customer triggers a special scenario, the system can invoke the “Special Case Handling” AI skill to generate an appropriate reply based on the current scenario, and then call the “Handover” tool to execute the offline operation.

Using this approach, you can generate different scripts for different situations, and record the handover reasons via tool calls, allowing you to view specific trigger details in the logs.

**Note: **After executing the handover using this method, the system may still send the handover script from the “Basic Configuration”. You need to adjust this fixed script based on actual results to avoid duplication with replies generated by the AI skill.

III. Specific Configuration Steps

Step 1: Create and Configure the “Handover” MCP Tool

Refer to the corresponding handover API documentation to create an MCP tool for executing handover operations.

Add a collection parameter in the tool:

Configuration Item Content
Parameter Name reason
Parameter Description Reason for handover

At the same time, add the reason field in the API request body so that the specific handover reason can be submitted when the tool is called. Only this field is shown below; other request parameters should follow the actual API documentation:

{
  "reason": "Customer complaint"
}

After configuration is complete, save and publish the MCP tool.

Step 2: Create the “Special Case Handling” AI Skill

Create a separate AI skill and set the scenarios previously configured in “Handover Conditions” as the trigger conditions for this skill.

In the skill, set up corresponding processing logic for different scenarios, for example:

  • **Customer complaint: **Generate a targeted soothing and bridging reply based on the content of the customer’s complaint, then call the “Handover” tool, filling in the reason with the actual complaint reason.
  • **Customer preparing to make a payment: **Generate a bridging reply based on the customer’s current transaction needs, then call the “Handover” tool, filling in the reason with the actual payment or transaction request.
  • **Other situations requiring human intervention: **Generate a reply according to the corresponding scenario, and fill in a clear handover reason when calling the tool.

The key is to have the skill identify specific scenarios, compose corresponding replies, and explicitly call the “Handover” tool, rather than just instructing the AI to say “I am transferring you to a human agent” in the script.

Step 3: Disable Existing “Handover Conditions”

After completing the configuration of the MCP tool and AI skill, go back to the original “Handover Conditions” configuration and disable these conditions.

This prevents the original rules from triggering prematurely, causing the AI to go offline directly without executing the personalized replies and handover tool calls within the “Special Case Handling” skill.

Step 4: Verify Actual Results

It is recommended to test with typical scenarios such as complaints and payments, focusing on confirming the following points:

  1. The “Special Case Handling” AI skill is triggered, rather than the original fixed handover conditions.
  2. The AI can generate corresponding replies based on the customer’s actual situation.
  3. The skill indeed calls the “Handover” tool and passes a clear reason.
  4. The AI successfully goes offline, and the corresponding handover reason can be viewed in the logs.
  5. The fixed handover script in the basic configuration does not cause duplication or conflict with replies generated by the skill.

IV. Which Method to Choose?

Comparison Item Directly Configuring “Handover Conditions” “AI Skill + MCP Tool”
Configuration Difficulty Lower Slightly higher
Can Trigger AI Offline Yes Yes
Can Generate Scenario-Based Replies No, uses fixed scripts Yes
Facilitates Clear Recording of Handover Reasons Not convenient Can be recorded via reason
Suitable Scenarios Sufficient if uniform scripts meet needs Scenarios requiring differentiated replies and reason tracing

**Summary: **If you simply want to take the AI offline, the built-in “Handover Conditions” are sufficient. If you wish to provide more appropriate responses to customers in different scenarios such as complaints and payments, while also recording specific handover reasons or having different processing logic, it is recommended to use the “Special Case Handling” AI Skill + “Handover” MCP Tool.