AI should hand customer service over to a person when the customer asks, when information needed to answer is missing, or when the decision requires authorization it does not have. For an online store, this includes a delivery with conflicting data and a request for commercial terms outside approved rules.
The handoff needs to bring the history to the team and stop automatic replies that would compete in the same conversation. If the customer hears "I'll get someone" and remains stuck answering bot questions, the handoff failed.
In ChatFunnel, the team can take over with the contact's history. To configure this use, start with reasons requiring a person and who will receive them. A vague instruction such as "transfer when necessary" leaves the decision without a criterion you can check.
Define triggers by the customer's situation
Choose signals visible in the conversation or consulted data. "Difficult customer" is a subjective assessment. "Customer said the previous solution did not work and requested an agent" describes a testable situation.
The matrix below is a starting proposal to adapt to your store's rules. The examples are hypothetical.
| Observed signal | Store example | Expected behavior |
|---|---|---|
| Explicit request for a person | "I want to speak to an agent" | Trigger the transfer without making the customer repeat the problem |
| Missing or conflicting information | The order appears delivered, but the customer says it was not received | Send to after-sales with both records, without concluding delivery occurred |
| Data lookup failure | The order system does not respond | Explain the limit and follow the store's defined contingency path |
| Decision outside AI authorization | Customer requests a discount above the approved range | Forward to someone who can decide, without promising approval |
| Conversation not progressing | AI repeats guidance the customer already said did not resolve the issue | Stop repeating and offer or trigger a handoff according to the rule |
| Dispute requiring investigation | Customer reports an unrecognized charge | Send to the responsible team and preserve the account without asserting a cause |
Documentation for Fin by Intercom separates rules that trigger a transfer from flows that define the destination afterward. This distinction helps review configuration: recognizing that a person needs to step in is one step; placing the conversation in the right queue is another.
Not every short or impatient phrase needs an immediate transfer. "Where's my order?" may have a direct answer when customer service finds the correct order and a valid update. "You say it was delivered, but nobody received it" presents a discrepancy requiring investigation.
Avoid using a universal number of attempts as a rule. You may test one clarification attempt for an ambiguous question. An explicit request for human service should have its own path without that wait.
Write the complete rule, including destination
Each trigger needs to specify what AI should do and what the team should receive. Consider this example rule for a fictional store:
When the customer says they did not receive an order marked delivered, forward the conversation to after-sales. Record the order number, consulted status, and the customer's description. Do not confirm receipt or promise a replacement shipment. If the order is not identified yet, ask for the number once without blocking the handoff if there is no response.
This instruction defines the question and preserves the team's decision. The queue still needs configuring, and you must check whether the tool can execute the handoff.
In ChatFunnel, conversations can be assigned and transferred to human service. Configuration should combine agent instructions with distribution features available on the account. Test who receives the conversation and what data they see before expanding use.
If the recurring failure is in the consulted source, sending every case to the team may hide the problem. First review how to correct AI answers about price and inventory. The same logic applies to order status: a connection that does not respond needs its own handling.
Preserve context so service can continue
Before responding, the human agent needs to understand what remains pending. Depending on AI agent configuration, the handoff may include a customer message and an internal case summary.
That record should answer objectively:
- What is the current request and why did AI forward the case?
- Which order or product is involved?
- What was checked and what was returned?
- What has AI already told the customer?
- What decision or action remains pending?
Separate what the customer reports from what the store confirmed. "The customer says they paid" and "the store confirmed payment" require different handling. If a lookup fails, record the failure rather than filling the gap with a conclusion.
In a hypothetical example: "Order 1048. Customer says it was not received. Lookup at 2:20 p.m. returned status 'delivered.' AI explained that the case needs checking and did not promise reshipment. After-sales should investigate the discrepancy."
The ChatFunnel customer record brings messages, fields, and opportunities together in one history. This helps the agent resume without requesting information already available. Before defining the flow, confirm what data the store connection supplies.
Check what happens while the person waits
Teams often test the phrase "I'll transfer you" and forget the queue. Follow the complete path: did the conversation leave AI, reach the expected destination, and become available for someone to take over?
During the wait, define which automated messages can still go out. A notice of service hours may help. Another AI attempt to resolve the same problem may confuse the customer, especially if a team member replies at the same time.
Do not promise "service in five minutes" without a timeframe the store can meet. Outside hours, say when the team returns and how the request will be recorded. If assignment fails, the flow must keep the pending case visible to the queue owner.
AI's return also needs a rule. The team may close the case or enable a new automated step. A customer message such as "thank you" should not accidentally restart the sequence that was just interrupted. Include this behavior in testing.
Test the handoff through the first human reply
Create test conversations with fictional orders and identify them so the team does not confuse them with customers. Each scenario should have an expected response before execution. The table is a starting guide without requiring a specific tool.
| Test scenario | What to check |
|---|---|
| Customer asks for a person in the first message | Transfer happens without a mandatory question sequence |
| Customer asks for a person after providing the order | The number and question accompany the conversation |
| Order lookup fails | AI does not invent a status and the issue reaches its intended destination |
| Customer disputes the previous answer | AI uses context and stops repeating |
| No agent is available | The notice matches team hours and the conversation remains visible |
| Agent takes over and customer sends another message | AI does not respond in parallel without an explicit rule |
| Team closes the case | The conversation does not accidentally return to the previous flow |
Ask the agent to open each case and respond using only what was received. If they need to ask again for everything the customer already provided, review the context sent. If they received the data but lack access to the necessary action, review the destination.
Record the failure reason and repeat the scenario after adjustment. A correct transfer phrase passes only part of the test. The case is ready when the right person can continue service without competing with AI.
Review reasons, not just total transfers
A decrease in transfers may indicate better answers or customers giving up before asking for help. Review a sample of conversations alongside the numbers.
Separate cases by reason and check the time between request and first human reply. Also look for transfers to the wrong queue, repeated questions, and issues still open after handoff.
If many conversations reach the team because the same information is missing, update the knowledge base. In ChatFunnel, daily learning presents suggestions extracted from closed conversations for review. A person decides what to approve before AI uses it. This lets the store correct a gap without treating every agent response as store policy.
Start with triggers your team already recognizes in conversations and test the entire path. ChatFunnel brings together AI agents, customer history, and human service to configure this handoff and monitor cases needing a person.
