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 6 others
‱ 19 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 ClaudIA Panel 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 Aug 26, 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 ClaudIA Panel 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 Aug 26, 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 ClaudIA Panel, under settings. Find "Unanswered ticket escalator" 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 Aug 29, 2026

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 panel, 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 'Transfer message' field on the ClaudIA Panel 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 ClaudIA Panel 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 ClaudIA Panel. To activate it, you need to request a Clouder to set the option ignoreConfidenceCountOnFirstMessage to true.

Last updated on Aug 30, 2026

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 ClaudIA, 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 26, 2026

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 ClaudIA Panel 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 ClaudIA Panel 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 Aug 29, 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 ClaudIA Panel, 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 ClaudIA Panel Whenever this feature is enabled, the reason for the transfer will be recorded with “Reason: Frustration detected”. This appears in both the ClaudIA Panel and the Helpdesk.

Last updated on Aug 29, 2026

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 panel — 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 Aug 26, 2026

What Is Rate Limit in Helpdesks and Why It Affects ClaudIA

When to use it - You are seeing undelivered messages or unresolved tickets and suspect Rate Limit - You need to understand what is and is not within ClaudIA's control - You want to know what to do to avoid hitting the limit Prerequisites - Access to the Helpdesk dashboard to check API usage - (For troubleshooting) Access to the ClaudIA Panel to check tickets with Resolved in N2 About this article Rate Limit is a restriction imposed by the helpdesks (Zendesk, Hubspot, Intercom, Freshdesk, etc.) that limits how many requests can be made within a period of time. It is exclusive to the helpdesk platform and is outside ClaudIA's control. Why this affects ClaudIA ClaudIA's integrations are optimized to consume as few requests as possible. Our architecture prioritizes only the essential actions: - Sending messages to end users - Closing/Resolving tickets automatically - Assigning tickets to humans (handover) Each of these actions consumes API calls. Why I can hit the Rate Limit Even with an optimized integration, there are factors outside our control: Helpdesk limitations - Each helpdesk sets its own limits in RPM (X requests/min) - The limits vary by contracted plan - Some helpdesks apply a global limit per account — all integrations share the same ceiling Customer settings and usage - Features that multiply requests (e.g.: split messages) - High ticket volume in short windows (thousands within a few hours) - Other systems/people using the API in parallel, consuming the same limit - Fluxos Controlados (Controlled Flows) that make additional requests to the helpdesk What happens when you hit the Rate Limit :::warning - Messages may be delayed or not delivered - Tickets may not be resolved or reassigned within the expected time - The helpdesk starts to reject calls until the limit is released ::: What to do to avoid it :::success Since control over the limit always belongs to the helpdesk and depends on the customer's settings and usage: 1. Track your API usage on the helpdesk platform 2. Map which systems besides ClaudIA consume the API 3. Review settings and avoid features that generate extra requests 4. Distribute the ticket volume better over time 5. Ask the helpdesk for a limit increase or a plan upgrade 6. Consider alternatives without API restrictions — such as Cloud Chat ::: What does "Resolved in N2" mean in the messages? When ClaudIA runs into a Rate Limit block, the N2 resolution message may appear with specific flagging. Notes - To understand automatic overflow by timeout: Como funciona o handover por timeout (Unanswered ticket escalator) - For Zendesk-specific Rate Limit: [Zendesk] Rate Limit e usos de RPM pela ClaudIA

Last updated on Aug 27, 2026

How to define the ideal closing time for N1 conversations

When to use - You want to understand the relationship between closing time and CSAT - You are seeing a lower CSAT than expected and want to assess the impact of closing time - You need to adjust the Minutes until ticket is resolved based on data Prerequisites - Administrator access to the project's ClaudIA Panel - (Recommended) The project's CSAT metrics available in the Dashboard About this article This is a data-based analysis of the impact of closing time on customer satisfaction (CSAT), with a practical recommendation for adjustment. What was analyzed We cross-referenced the average closing time + problem resolved checker of tickets with CSAT across different projects. Only interactions with a relevant volume (min. 20 CSAT responses) and times between 0 and 120 min (typical of N1) were considered. :::info Above 120 minutes, the drop in response rate does not offset the increase in CSAT. ::: What the analysis showed The results indicate a moderate positive correlation (r ≈ 0.40) between closing time and CSAT. - Tickets closed very quickly (up to ~30 min) → lower CSAT (automatic closures or incomplete interactions) - Tickets with a closing time close to 120 min → consistently higher and more stable CSAT This behavior holds even after excluding cases with very low CSAT (<40%) — closing too quickly hurts the perception of the service. What this means in practice - Short closures do not necessarily reflect efficiency — in many cases, they indicate a lack of engagement or automatic resolutions before actual confirmation - Allowing a longer period of inactivity before closing helps to capture late messages, improves the natural flow of the conversation and increases the chance of a positive CSAT Ideal recommendation :::success We suggest that the automatic closing time be adjusted to around 120 minutes, especially for N1 tickets. This interval balances: - ⏳ Enough time for the customer to resume the conversation without reopening the ticket - 😊 Higher satisfaction measured by CSAT - 📈 Fewer false closures with negative ratings ::: Next steps 1. Review the time configured in "Fechamento automático por inatividade" (Automatic closing due to inactivity) in the automations panel 2. If it is below 60 minutes, increase it gradually up to 120 min while monitoring the impact on the CSAT reports Notes - To set up automatic closing: How to set up automatic ticket closing in N1 - To validate the resolution before closing: How to validate that the problem was resolved before closing - To improve CSAT: How to improve ClaudIA's quality (CSAT)

Last updated on Aug 26, 2026

Conversation transferred outside business hours: why it shows up as resolved

When to use this - A conversation that should have gone to the human queue showed up as resolved - This happened with conversations that came in outside business hours - You want to understand who closed it: ClaudIA or a person What happens outside business hours When ClaudIA needs to transfer a conversation and nobody is within business hours, there are two possible behaviors — and which one applies depends on a setting in your project. | Setting | What happens | | --- | --- | | Resolve in N1 outside business hours — off | The conversation is transferred normally and stays in the queue, waiting for the team at the next business hour | | Resolve in N1 outside business hours — on | Instead of transferring, ClaudIA closes the conversation in N1, with the out-of-hours message | :::info If your conversations outside business hours are showing up as resolved instead of waiting in the queue, this setting is almost certainly on in the project. It is not a transfer failure: it is the configured behavior. ::: Where to check In the project's ConfiguraçÔes da ClaudIA (ClaudIA Settings), look for the option to resolve in N1 outside business hours (in the transfer/business hours area). That is where the behavior is chosen. The human business hours are also defined in the project — they are what determines what counts as "outside business hours". How to tell who closed it Open the conversation and look at the timeline: - If you see Resolvido em N1 (Resolved in N1) with a reason related to being outside business hours, it was ClaudIA that closed it, through the behavior described above. - If you see a person's name, the conversation was closed manually. The resolution reason is recorded in the conversation and can also be filtered in search, through the ClaudIA filter group. Which of the two to choose - Leave it off if you want the customer to be served by a person at the next business hour — the conversation waits in the queue. - Leave it on if you prefer to close and tell the customer to come back during business hours, avoiding an overnight backlog in the queue.

Last updated on Aug 31, 2026

When a conversation is closed automatically (native and mirrored)

When to use this - You want to know when a conversation closes on its own with ClaudIA - You work through Cloud Chat (a native conversation) and want to know whether the rules change - ClaudIA marked a case as resolved and it did not close right away Short answer ClaudIA's closing rules work exactly the same in native conversations and in mirrored conversations. There is no closing rule that gets turned off just because the conversation is native to Cloud Chat. What changes between the two cases is something else: Cloud Chat's automatic resolution by inactivity, which only acts on native conversations. Native and mirrored: what's the difference - Native — the conversation is born and lives in Cloud Chat (website chat, WhatsApp, email, etc.) - Mirrored — the conversation happens in another helpdesk and is mirrored into Cloud Chat so ClaudIA can handle it; the copy in Cloud Chat is read-only The three ways a conversation can close on its own 1. The customer confirms it was solved (immediate closing) With the "Verificador de problema resolvido" (Problem Solved Checker) in real-time mode, a clear confirmation from the customer ("that was it, thank you") closes the case right away, without waiting for a timer. This applies equally to native and mirrored conversations. 2. The customer stops replying (ClaudIA's automatic closing) If the customer disappears, ClaudIA waits for the time set in "Minutos sem resposta" (Minutes without a reply), counted from the last message she sent, and closes the ticket at N1 with the closing message. This applies equally to native and mirrored conversations. Where to configure it: "ConfiguraçÔes da ClaudIA" (ClaudIA Settings) > "Ciclo de vida" (Lifecycle) > "Resolução AutomĂĄtica" (Automatic Resolution) > "Encerramento automĂĄtico" (Automatic Closing). :::warning This closing only happens if "Encerramento automĂĄtico ativo" (Automatic closing active) is turned on in the project. With it turned off, ClaudIA does not close the ticket — even after having solved the question. ::: 3. General inactivity (Cloud Chat's automatic resolution) Independently of ClaudIA, Cloud Chat resolves idle conversations on its own after the last reply from the support side, based on the time set in "ConfiguraçÔes da Conta" (Account Settings). :::info This is the only rule that tells native and mirrored apart — and it applies only to native conversations. Mirrored conversations are read-only in Cloud Chat and are left out. ::: :::warning There is no default 48-hour deadline. That time is whatever your account has configured, in hours. If the field is blank, Cloud Chat does not close anything by inactivity — and closing then depends on ClaudIA alone. ::: Why a "resolved" conversation may not have closed right away - "Encerramento automĂĄtico" (Automatic Closing) is turned off in the project - The real-time "Verificador de problema resolvido" (Problem Solved Checker) is turned off, so only the timer acts — and the time has not run out yet - The customer gave a neutral reply ("ok", "thanks"), which does not count as a confirmation that it was solved - The closing routines run in cycles of a few minutes, so there may be a small delay compared to the configured time

Last updated on Aug 31, 2026

How a conversation is classified as N1 or N2

When to use - You want to understand why a ticket showed up as "Resolvido em N1" (Resolved at N1) even though a human worked on it - You need to filter or count conversations by N1 and N2 - Someone told you that N1/N2 comes from an automation and you want the correct information About this article N1 and N2 are a native Cloud Chat field, filled in by ClaudIA itself at the moment it closes or transfers the conversation. It is not an automation, it is not a label and it does not come from an external system — there is nothing for you to configure for the classification to happen. :::info The rule is simple: N1 = ClaudIA solved it on its own. N2 = the conversation went to a human. ::: How the classification is defined Every conversation gets a "Resolução" (Resolution) and a "Motivo da resolução" (Resolution reason): | Resolution | What it means | | --- | --- | | N1 | ClaudIA completed the conversation without handing it to a human | | N2 | ClaudIA transferred it, or the ticket was taken over by a human | | Em aberto (Open) | The conversation has not been resolved yet | The "Motivo da resolução" (Resolution reason) explains why. Examples that fall under N1: Resposta completa fornecida (Complete answer provided), Resolvido em N1 (Resolved at N1), Fora do expediente (Outside business hours). Examples that fall under N2: Frustração detectada (Frustration detected), Confiança baixa (Low confidence), Limite de mensagens excedido (Message limit exceeded), Seção N2 utilizada (N2 section used), TransferĂȘncia N2 forçada (Forced N2 transfer), TransferĂȘncia por timeout (Transfer by timeout). Where to see it - In the ticket — the timeline shows the resolution and the reason in Portuguese, such as "Resolvido em N1" - In conversation search — under advanced filters, in the "Filtros ClaudIA" (ClaudIA Filters) group, use "Resolução" (Resolution) (N1, N2 or open) and "Motivo da resolução" (Resolution reason) - In the "Construtor de RelatĂłrios" (Report Builder) — the resolution columns let you count N1 and N2 by period Why a ticket with human handling can show up as N1 The classification is recorded at the moment ClaudIA closes the conversation. If the conversation was closed as N1 and only after that an agent reopened, replied to or closed the ticket manually, the recorded resolution is still the one from ClaudIA's closing — there is no automatic reassessment when a human closes it. :::warning If you need to count "every ticket that had human intervention", and not just "every ticket that ClaudIA transferred", combine the "Resolução" (Resolution) filter with agent or team filters. Resolution alone does not answer that question. :::

Last updated on Aug 31, 2026

ClaudIA Settings — Lifecycle

When to use - Configure greetings (first interaction and default). - Define how ClaudIA closes conversations automatically (resolution). - Enable and adjust Controlled Flows (Eddie) at the start of the conversation. How it works Lifecycle section of ClaudIA Settings The Lifecycle section covers the start, the closing, and the guided flows of the conversation. There are three blocks. Greetings - Initial greeting — instruction used in the first interaction, replacing the {GREETING} placeholder. - N2 greeting — message sent when an unanswered ticket is escalated. - Static greeting — when enabled, sends a fixed greeting text. Automatic Resolution - Problem resolved checker — has two independent modes (enable one, the other, or both): - Scheduled — after a period without a reply, ClaudIA asks whether the user still needs help. Define the verification question and the minutes until the question. - On message (proactive) — ClaudIA tries to detect in real time whether the problem was resolved and closes when appropriate. - Automatic closing — closes resolved tickets automatically. Define the minutes without a reply and the closing messages with feedback and without feedback. Controlled Flows - Start with Controlled Flow — starts conversations through a guided flow. Define the flow ID and whether to add the intent to the N2 tag when escalating. - Controlled Flow settings — maximum number of repetitions per flow before transferring and the flow's error message. Notes :::info The two modes of the Problem resolved checker (Scheduled and On message) are independent and work in parallel — you can turn both on at the same time. They are not mutually exclusive. ::: - Creating and editing the flows themselves is done in the Controlled Flows area (ClaudIA's side menu); here you only choose which flow starts the conversation.

Last updated on Sep 02, 2026

ClaudIA Settings — Handover

When to use - Define when ClaudIA hands the conversation over to a human (N2). - Configure frustration detection and human availability (business hours). - Adjust the escalation of unanswered tickets and the summary sent on handover. How it works Handover section of ClaudIA Settings The TransferĂȘncia (Handover) section defines the decision to pass to a human and the context sent along with it. These are the blocks below. N2 handover — Main settings - Repeated section limit — how many times the same section can appear in a ticket before escalating to a human. - Handover message — message triggered when any handover logic is activated (count limit, forwarding to a human, repeated section limit, or clarifying question limit). Frustration detection - Enabled — turns frustration detection on/off. - Frustration limit — maximum frustration points allowed before handing over. - Handover message — text sent before handing over due to frustration. Human availability - Humans available — indicates whether there are agents at the moment. It can be changed manually, but the configured business hours are the default reference. - Default business hours — schedule rules (e.g., Monday to Friday, from 08:00 to 18:00), with an "all day" option and the option to add more rules. - Special dates and holidays — one-off exceptions to the default schedule. - Out-of-hours message — sent when the team is off-hours and the feature is active. - Resolve as N1 out of hours — outside business hours, closes as N1 instead of handing over to N2. Automatic handover — Unanswered ticket escalator - Escalation message — text sent when escalating the ticket. - Tag — tag applied on escalation. Conversation summary - Summary prompt — instruction to generate the internal note sent when handing over to N2, when escalating, or when automatically closing as N1. Notes - The handover message (main block) covers several handover logics at the same time — review it carefully. - Human availability combines the manual toggle with the schedule rules: the toggle reflects the present moment; the schedule, the recurring default.

Last updated on Sep 02, 2026