Home Conversation Closure: Handover (N2) and Retain (N1)
🔚

Conversation Closure: Handover (N2) and Retain (N1)

Descriptions of our handover functionality and ticket closure
FabrĂ­cio Rissetto
By Daniel Conde Feitosa and 5 others
• 12 articles

How to configure the out-of-hours message and human team unavailability (N2)

When to use - You need to set up the default human support hours (weekdays, Saturday, etc.) - You want to register special dates and holidays with different rules - You want to understand the 3 ways ClaudIA can behave outside business hours Prerequisites - Administrator access to the project's Hub About this article The system uses schedule rules to automatically switch human support availability. The configuration lives in ClaudIA → "Configurações" → "Transferência" → "Disponibilidade humana" (Settings → Transfer → Human availability), with two blocks: "Horário de atendimento padrão" (Default support hours) and "Datas especiais e feriados" (Special dates and holidays). :::info Times follow the time zone configured in the project (default: Brasília time). ::: Details Default Support Hours ("Horário de Atendimento Padrão") Define recurring rules per day of the week. When adding a rule: - Aplicar em (Apply to) — Monday to Friday · Saturday · Every day · Custom (select the days individually) - Disponibilidade (Availability) — Atendimento Ativo (Active Support) or Sem Atendimento Humano (No Human Support) - Horário (Hours) — set a start and end time, or check Dia todo (All day) :::info You can add multiple rules. E.g.: one for Monday to Friday from 9 AM to 6 PM, another for Saturday from 9 AM to 12 PM. ::: Human availability block — Default support hours Special Dates and Holidays ("Datas Especiais e Feriados") Register exceptions to the default hours (holidays, events, atypical days). For each date: - Nome (Name) (optional) — identifies the date (e.g.: "Carnival 2026") - Data (Date) — the specific day - Disponibilidade (Availability) — Atendimento Ativo (Active Support) or Sem Atendimento Humano (No Human Support) - Horário (Hours) — a specific period or Dia todo (All day) :::warning Special dates always take priority over the default hours. ::: Example — Carnival 2026 | Date | Availability | Hours | | --- | --- | --- | | 02/16/2026 | No Human Support | All day | | 02/17/2026 | No Human Support | All day | | 02/18/2026 | No Human Support | from 9 AM to 2 PM | Special dates and holidays in ClaudIA Settings How availability impacts support The configuration influences 3 distinct behaviors of ClaudIA: 1. Within business hours: normal transfer With humans available, the transfer to N2 happens normally, without any out-of-hours notice to the customer. 2. Outside business hours: out-of-hours message + handover With no humans available, ClaudIA sends the out-of-hours message configured in the project and hands the ticket over, and it waits in the queue until the team is back. :::info The out-of-hours message is a fixed text, written by you — ClaudIA does not calculate or automatically inform the next available time. If you want the customer to know when they will be served, include the hours in the text itself (e.g.: "Our team is available Monday to Friday, from 9 AM to 6 PM. As soon as we're back, we'll reply right here!"). ::: 3. Outside business hours: message + resolve in N1 Avoids unnecessary queues: instead of handing the ticket over, ClaudIA sends the out-of-hours message and closes the ticket in N1. In this case, the closure appears in the reports with the out-of-hours reason. Notes - To set up holidays and special dates: How to configure holidays and special dates in ClaudIA - To understand automatic ticket closing in N1: How to configure automatic ticket closing in N1

Last updated on Jul 05, 2026

How to set up automatic ticket closure in N1 (Ticket Resolver)

When to use - You want to define how much inactivity time passes before a ticket is closed by ClaudIA - You need to customize the closing message (with or without a feedback/CSAT request) - You want to avoid tickets staying open unnecessarily Prerequisites - Administrator access to the project's Hub About this article Automatic closure defines the closing rules for tickets after ClaudIA's response, followed by a period of user inactivity. It ensures that unresolved tickets do not remain open unnecessarily and that the customer receives closing feedback. Adjusting the settings In ClaudIA → Configurações → Ciclo da Conversa → Resolução (Settings → Conversation Cycle → Resolution), in the Encerramento automático (Automatic closure) block: "Encerramento automático ativo" (Automatic closure enabled) Turns automatic closure of resolved tickets on/off. "Minutos sem resposta" (Minutes without reply) How many minutes ClaudIA waits, counting from the last message she sent to the customer, before closing the ticket when the user no longer replies. :::info If the Problem Resolved Checker (scheduled mode) is enabled, the counting changes: ClaudIA sends the verification question and the ticket is closed after the time configured in the Checker, counted from that question. ::: Closing messages There are two types of configurable messages: 1. Message without feedback — sent when the ticket is closed due to inactivity, without the customer having given any response. 2. Message with feedback — sent when the customer gave a response before the closure: they confirmed the problem was resolved (via the Problem Resolved Checker) or answered the satisfaction survey (CSAT). :::warning The choice between the two is made conversation by conversation. Even with the Checker or CSAT enabled in the project, a ticket closed due to pure inactivity receives the message without feedback — so write both messages with both scenarios in mind. Fill in both messages. If either of them is left blank, ClaudIA closes tickets without sending any closing message. ::: :::info In many cases the two messages can have the same content. But you can customize them independently for specific situations. ::: Automatic closure block in ClaudIA Settings Changes in the Resolução (Resolution) subsection are saved together via the subsection's own Salvar (Save) button. Notes - To understand the ideal closing time (correlation with CSAT): How to define the ideal closing time for conversations - To validate the resolution before closing: How to validate that the problem was resolved before closing (Problem Resolved Checker)

Last updated on Jul 05, 2026

N2 | Escalate Tickets Without Response (Handover by timeout)

When does the overflow occur due to timeout? This behavior occurs when there is some instability or connection error in the integration that prevents a response to the customer within the scheduled time. In these cases, the functionality automatically transfers the ticket to ensure continuous customer service. Some reasons that may cause Claudia to use this functionality include: - Error reaching the Helpdesk API Rate Limit - System errors in Claudia Since this is an automatic action and part of the feature's design, this type of transfer is not available for auditing. How to identify? In the ticket, you will see that it uses the tag: n2_unansweredbyclaudia. Another detail is that you'll notice the customer remains unresponsive for a period (+10 minutes), after which a standard message is sent and the transfer occurs. Suggested response: Hello! How are you? This ticket was automatically transferred due to timeout. This behavior occurs when there is some instability that prevents a response to the customer within the expected timeframe. In these cases, the functionality transfers the ticket to ensure the customer receives assistance. Since this is an automatic and expected action of the feature, it is not available for auditing. Adjusting the transfer message Some customers complain about the default message that is sent. We can help modify it within the hub, under settings. Find "Escalar Tickets Sem Resposta" Message Attention: We will only change the message and no other fields, as the settings are standard for the feature to work correctly. Click save

Last updated on Oct 11, 2025

N2 | Transfer due to lack of content (Low Confidence & Count Limit)

One of the controls we have to identify that ClaudIA is not able to find enough content to respond to the user is the 'low confidence counter'. In the Hub, when ClaudIA does not find content above the stipulated confidence (more on that later), a 'Count limit' indicator appears in yellow below ClaudIA's response, as shown below: After reaching the configured limit, the service is automatically transferred to a human using the message configured in the 'Forward To Human Message' field on the Hub settings screen. The configuration of the limit counters can also be adjusted on the same screen: - 'Limit' is the field that defines the maximum number of low-confidence searches. PS: we recommend at least 3, as not every low-confidence content search necessarily generates a bad response. Sometimes ClaudIA clarifies and that resolves it; sometimes the user's message does not require content to be answered (example: "Good morning!") - 'Low Confidence Threshold' is the minimum expected distance to be considered relevant content (high confidence). Every content search in the Hub presents a score that you can track directly whenever you see the sessions returned by ClaudIA's search, as in the Conversations audit screen: Additional functionality It is possible to configure ClaudIA to ignore the low confidence count on the first response of a ticket, considering that often the user's first interaction is just a greeting. This prevents the counter from being incremented unnecessarily. However, if the first message already contains a question and ClaudIA provides a low-confidence answer, that interaction will not be counted. The other interactions in the ticket follow the normal confidence counting flow. Currently, this configuration is not available in the Hub. To activate it, you need to request a Clouder to set the option ignoreConfidenceCountOnFirstMessage to true.

Last updated on Aug 12, 2025

N1 | Validate problem resolution before closing (Problem Solved Verifier)

How It Works 1. Final question triggered by the timer (default flow) - ClaudIA sends a follow-up message (e.g., "Can I assist you with anything else?"). - The system interprets the user's response: - Resolved: ticket is automatically closed after a few minutes (asynchronous routine). - Dissatisfaction: ticket is moved to N2. - Other response: the conversation remains open. 🔸 Important: the service runs asynchronously every 5 minutes, so there may be a slight delay in triggering. 2. Verification after each new message (optional) - ClaudIA proactively evaluates each new message sent by the customer. - Examples: - "That's all, thank you" → immediate closure (without waiting for the timer). - "It's not resolved" → conversation remains open, possibly moving to N2. - Neutral response ("Ok", "Thanks") → ClaudIA responds and sends the closing follow-up. :::info The two modes are independent — you can enable one, the other, or both at the same time. ::: How to configure In ClaudIA → Settings → Lifecycle → Automatic Resolution, in the Problem resolved checker block: Scheduled — enable Scheduled mode, set the verification Question and the Minutes until the question. Scheduled mode in the Problem resolved checker On message (proactive) — enable Real-time mode so ClaudIA detects, on each message, whether the issue is resolved. On-message (real-time) mode in the Problem resolved checker Each block saves independently. The scheduled trigger runs asynchronously (up to a ~5-minute delay). The configured Question is also used by the real-time check. ⚠️ Interaction with Controlled Flows Here are new features (with feature flag): 1. Send follow-up but keep user in the Controlled Flow - When a customer responds to a follow-up during a Controlled Flow, the conversation does not return to ClaudIA. - Control remains with the Controlled Flow until the flow ends. The user's response after FUP is sent to the Controlled Flow. 2. Do not send follow-up in the Controlled Flow - If the conversation is ongoing within a Controlled Flow, ClaudIA does not send the follow-up question. - This allows the Controlled Flow to continue the conversation without interruptions. However, note that the ticket might be closed by the default closing time without sending an FUP. These two behaviors are disabled by default but can be activated on demand — contact support to enable via feature flag.

Last updated on Jun 30, 2026

N2 | Ticket Taking Functionality in the Hub, Removing It from Service (Forced Handover)

https://www.loom.com/share/d68947c57c0c4675b4ff6474b58830c9?sid=955f0f63-8092-4b3d-b0d2-5f5b410b484b The action of taking a ticket allows your team to interrupt the automated service provided by ClaudIA and take manual control of the conversation with the end customer. When should I use this functionality? You can use this functionality to take over a ticket that is being handled by ClaudIA. This is useful in situations such as: - The automated service is not progressing as expected. - You want to make a more precise manual intervention. - Your team wants to escalate the conversation to a more human or specialized handling. The Take All button is disabled. Why? This button is only enabled when there are open conversations in the current filter, i.e., conversations that have Status: Open, still in progress with ClaudIA. If the button is disabled, it is because: - The current filter shows only resolved or closed conversations. - No eligible conversations were found in the selected period. How to view open conversations? 1. Click on Filter. 2. In Resolution, select the Open or All option. 3. Click on Apply filters. What happens when I click Take? When you click Take (individually or in bulk), the following steps are performed: 1. We attempt to automatically transfer the conversation to Level 2 (N2) of service. 2. Even if the transfer is unsuccessful, ClaudIA interrupts the service of that ticket. 3. From that moment on, your team can take over the service manually, redirect, or end the conversation as preferred. Important: In cases where automatic transfer does not occur, you or someone from your team needs to pull it manually for you. This is done in your own Helpdesk. These cases happen when there is some communication failure, so we prioritize ensuring that ClaudIA leaves the service completely, rather than having the chance to transfer to someone and it responds in the middle of the conversation—which we know brings a very bad experience for the end customer. Button to take tickets in bulk: Button to take a ticket individually:

Last updated on Aug 12, 2025

How to set up transfer detection (Detect Transfer)

When to use - You want ClaudIA to automatically transfer the conversation whenever she says she is going to transfer it - You are modeling N2 sections and need to make sure the handover actually happens - You are seeing tickets in the dashboard with the reason "ClaudIA falou que ia transferir" (ClaudIA said she would transfer) and want to understand where they come from Prerequisites - Access to the Hub with permission to edit content and settings - (For auditing) Access to the "Dashboard de Métricas de Retenção" (Retention Metrics Dashboard) About this article Detect Transfer makes ClaudIA notice when her own reply indicates a transfer and, in that case, automatically trigger the handover to a human agent (N2). Detection works by interpreting the message, not by matching exact phrases: any reply in which ClaudIA commits to transferring the conversation can trigger the handover, even if the wording is not identical to the examples in this article. How to enable it Detect Transfer has its own switch and comes disabled by default. To enable it, go to ClaudIA → "Configurações" → "Transferência" (Settings → Transfer) and turn on the "Detectar pedido de transferência" (Detect transfer request) option. :::error With the option disabled, nothing happens: even if ClaudIA's reply promises to transfer the conversation, the automatic transfer is not performed — and the customer may be left waiting for an agent who will never arrive. Before relying on transfer phrases in your sections, make sure the option is enabled in your project. ::: How to use it in N2 sections In the response of the N2 sections that should escalate, write a clear transfer phrase, such as: - "I'm going to transfer your conversation to a specialist" - "I'm going to forward your request to an agent" - "I'm going to transfer your case to our team" Transfer phrase N2 section with phrase Since detection works by interpretation, you don't need to use these exact phrases — but the more direct and unambiguous the transfer promise is, the more reliable the detection. :::warning Be careful with transfer phrases in N1 sections. If an N1 response contains a transfer promise, ClaudIA may transfer a conversation that should have stayed with her. In INTERACTIVE sections ("Fluxo Controlado" / Controlled Flow), on the other hand, detection is not applied: messages sent inside flows do not trigger Detect Transfer. To transfer inside a flow, use the Controlled Flow's own transfer. ::: How to track it in the dashboard The % of tickets escalated by Detect Transfer is shown in the Hub Dashboard, on the "Métricas de Retenção" (Retention Metrics) tab, in the "Proporção de razões de transferência em tickets N2" (Share of transfer reasons in N2 tickets) chart, under the name "Claudia detectou ação de transferência" (Claudia detected a transfer action). Transfer reasons dashboard The tickets appear in the "Quantidade de tickets / Razão de Transferência" (Ticket count / Transfer Reason) table as "Claudia falou que ia transferir o atendimento" (Claudia said she would transfer the conversation). Tickets table Notes - To understand the transfer reasons: How ClaudIA and the audit process work - To transfer without notifying the customer: How to remove the Handover message - For other escalation options: How to set up handover by message limit · Transfer on frustration

Last updated on Jul 05, 2026

N2 | Trying to Convince the User to Talk to AI Before Transferring (Forward to Human Check)

This feature allows ClaudIA to try to convince the user to be served by her instead of being directly transferred to a human when requested. This is especially useful in cases where, before ClaudIA, there was a TREE BOT or any automation alternative that provided a poor experience to users, and they have already developed the habit of requesting human assistance. In many cases, we are able to convert this user to stay with ClaudIA. If the user insists, we respect the request and transfer the ticket to the N2 team. Example of a user insisting to talk to a human To increase the retention rate, we can configure the message to be more persuasive, something like "The team is experiencing high demand and it may take a few minutes to respond..." Example of a user who accepted to be served by the AI Interaction with Controlled Flows It is worth noting that, although this feature was created with the goal of increasing retention, it does not "lock" the user. All of ClaudIA's guardrails are designed with a focus on quality — even when optimizing for retention. In other words: if the user insists, they will be directed to a human, as part of our product's design choice. A direct impact of this decision is that, even within a structured Controlled Flow, if the customer asks to speak to a human, they will be taken out of that flow and redirected to human assistance.

Last updated on Jun 24, 2026

N2 | Frustration Detection Transfer

What is it? ClaudIA can detect when a customer becomes frustrated during a conversation. When this happens, she can automatically transfer the support to a human agent, ensuring the issue is handled more carefully. How it works Every message from the customer is analyzed and assigned a frustration score. This score accumulates until it reaches the configured limit. - 1 point — Mild irritation The customer shows impatience or makes repeated complaints, but without aggression. - 3 points — Frustrated Stronger complaints about the service/product, tense tone, risk of cancellation, mention of billing/refund, or occasional use of mild swear words. - 5 points — Highly frustrated The customer threatens to cancel, writes IN ALL CAPS, asks to speak with a supervisor, uses strong swear words frequently, or threatens legal action. When the total reaches 5 points (or the configured value), ClaudIA transfers the support. She sends a standard message to the customer and logs an internal note explaining the reason for the transfer. How to configure In the Hub, under the Settings tab, you can: - Enable or disable the feature. - Set the maximum allowed score (default is 5 points). - Edit the message sent to the customer when frustration is detected. How to identify in the Hub Whenever this feature is enabled, the reason for the transfer will be recorded with “Reason: Frustration detected”. This appears in both the Hub and the Helpdesk.

Last updated on Sep 03, 2025

How to Set Up Holidays and Special Dates in ClaudIA

Overview On holidays and atypical dates, the behavior of human support (N2) needs to be adjusted. In ClaudIA, this is done directly in the Hub — without manual intervention on the holiday day. Where is the setting In ClaudIA → Settings → Transfer → Human availability. The block has two parts: - Standard support hours — recurring rules by day of the week - Special dates and holidays — exceptions to the standard schedule Human availability — Standard support hours block in ClaudIA Settings Configuring holidays in Special Dates 1. Scroll to the Special dates and holidays block and click Add special date 2. Fill in the fields: | Field | How to fill | | --- | --- | | Name (optional) | Identifies the date, e.g.: Carnival 2026 | | Date | The specific day of the holiday | | Availability | No Human Support for full holiday, or Active Support for reduced hours | | Schedule | Enable All day for full holiday, or set start and end times for reduced hours | 3. Repeat for each day of the holiday (extended holidays = one entry per day) 4. Save the configurations ⚠️ Special dates always take priority over the standard schedule. Even if the weekly rule says "Monday to Friday from 9 AM to 6 PM," if that day is registered as a holiday, the special date prevails. Special dates and holidays in ClaudIA Settings Example — Carnival 2026 | Date | Availability | Schedule | | --- | --- | --- | | 02/16/2026 | No Human Support | All day | | 02/17/2026 | No Human Support | All day | | 02/18/2026 | No Human Support | All day | How ClaudIA behaves outside business hours Beyond the schedule, you can configure what ClaudIA should do when human support is unavailable. These settings are just below in the same Human availability block: Out-of-hours message and Resolve as N1 outside hours. There are two possible behaviors: | Behavior | What happens | When to use | | --- | --- | --- | | Overflow (Resolve as N1 outside hours disabled) | Sends the out-of-hours message and forwards the ticket to the human queue (N2) | When the customer needs to be attended by a human as soon as the team returns | | N1 Closure (Resolve as N1 outside hours enabled) | Sends the message and closes the ticket without creating a queue | When you want to avoid accumulated queues during the holiday | 💡 Best practices: Always mention the return date in the out-of-hours message. Example: "We are on break today. Our support resumes Monday at 9 AM." This reduces reopenings and customer frustrations awaiting replies. Frequently Asked Questions Does ClaudIA stop responding on holidays? No. The configuration affects only human support (N2). ClaudIA continues to operate normally in N1 during holidays unless you manually turn it off in Settings → General. Can I register multiple holidays at once? Yes. Add as many dates as you want. Each day requires a separate entry — giving you individual control over each day's schedule. Can I edit or delete a special date after saving? Yes. Revisit the Special dates and holidays block, edit or delete the entry. The changes take effect immediately for new conversations. What if the holiday has already passed and the date is still registered? No problem — past dates are automatically ignored by the system.

Last updated on Jun 30, 2026