How to Prevent Ticket Reopenings with Thank-You Detector in BoldDesk
Thank-You Detector is an AI Copilot feature that evaluates customer replies received on resolved or closed tickets. When a reply contains only an acknowledgment, such as “Thanks” or “Thank you,” BoldDesk records the reply as a note and keeps the ticket closed instead of reopening it.
If the reply contains a new question, unresolved issue, request, or other content that requires action, the ticket reopens according to the configured ticket behavior. This intent-based evaluation helps reduce unnecessary ticket reopenings while ensuring that actionable customer messages return to the support queue.
- Thank-You Detector is part of AI Copilot. AI Copilot must be enabled before Thank-You Detector can be configured.
- The Thank-You Detector feature is accessible within both the Momentum (Legacy) and Enterprise plans.
Prerequisites
Before configuring Thank-You Detector, ensure that:
- Agents required to prevent ticket reopenings using the Thank-You Detector possess access to the AI Copilot.
- The applicable brands and ticket sources are configured in BoldDesk.
- Your role has the Manage AI Co-pilot permission under the AI Copilot module.
For general AI Copilot setup information, explore How to Enable and Configure AI Copilot Features in BoldDesk.
How Thank-You Detector Works
Thank-You Detector follows this workflow when a customer replies to a ticket that is already resolved or closed:
- Customer replies: A reply is added to a resolved or closed ticket.
- Brand and source check: BoldDesk confirms that the ticket matches the selected brands and sources.
- Intent detected: The AI evaluates whether the reply is only an acknowledgment.
- Outcome applied:
- If the reply is acknowledgment-only, BoldDesk records it as a note and keeps the ticket closed.
- If the reply contains a new question or issue, the ticket reopens according to the normal reopening behavior.
Thank-You Detector evaluates the intent and context of a reply rather than relying only on keyword matching.
AI Copilot must be enabled before Thank-You Detector can be configured.
When AI Copilot is disabled, the AI Copilot features are unavailable.
How to Enable and Configure Thank-You Detector
AI Copilot must be enabled before Thank-You Detector can be configured. Explore further information on How to Enable or Disable AI Copilot in BoldDesk.
When AI Copilot is disabled, the AI Copilot features are unavailable.
After enabling AI Copilot:
-
Remain in AI Center > AI 2.0.
-
Under AI Copilot, select Thank-You Detector. BoldDesk opens the dedicated Thank-You Detector configuration page.
The Thank-You Detector page contains the feature toggle, Brand and Source fields, a summary of the decision workflow, and example outcomes. -
Turn on Thank-You Detector.
-
In Brand, select the brands where the detector should run. The Brand field determines which brands are eligible for Thank-You Detector.
- Select one or more brands to restrict the detector to those brands.
- Leave the field empty to include all brands.
-
In Source, select the eligible ticket creation or reply sources. The Source field determines which ticket creation or reply channels are eligible for Thank-You Detector. A source is the channel through which a ticket was created or replied to, such as email, the customer portal, or live chat.
- Select one or more sources to restrict the detector to those sources.
- Leave the field empty to include all sources.
-
Review the How it works and See it in action sections.
-
Click Update.
Click Discard to remove unsaved configuration changes.
The Update button is enabled after a configuration change is made.
Understand Thank-You Detector Decisions
The detector keeps a ticket closed only when the reply is identified as an acknowledgment without a new issue or question.
| Reply Type | Example | Result |
|---|---|---|
| Acknowledgment only | “Thank you so much, that solved it! I appreciate the quick help.” | The reply is recorded as a note, the ticket remains closed, SLA timers are not restarted, and the ticket does not return to the agent queue. |
| Acknowledgment with a new issue | “Thanks, but now the export button is grayed out on my end.” | The ticket reopens and returns to the agent queue because the reply requires follow-up. |
| New question | “Can you also help me configure the export schedule?” | The ticket reopens according to the normal reopening behavior. |
| Unresolved issue | “Thank you, but the original problem is still happening.” | The ticket reopens because further action is required. |
| Negative or sarcastic acknowledgment | “Thanks for nothing. The issue is still not fixed.” | The ticket reopens because the reply is not acknowledgment-only. |
The examples are illustrative. The live detector uses AI to evaluate the complete intent and context of each reply.
Understand the Ticket Outcome
Acknowledgment-Only Reply
When the detector identifies an acknowledgment-only reply:
- The ticket remains closed.
- The customer reply is recorded as a note.
- SLA timers are not restarted.
- The ticket does not return to the agent queue.
- The ticket history records the detector outcome, when applicable.
Reply Requiring Follow-Up
When the reply contains a new issue, question, request, or unresolved problem:
- The ticket reopens according to the configured reopening behavior.
- The ticket returns to the applicable agent queue.
- The customer message remains available in the ticket conversation.
- Agents can continue handling the new or unresolved request.
Understand Ticket Status Requirements
Thank-You Detector evaluates replies only when the ticket is already in an applicable resolved or closed state.
The detector does not evaluate customer messages on tickets that are already Open, Pending, or in another active status.
If the ticket is not resolved or closed when the reply is received, the standard ticket update behavior applies.
Understand Reopening Configuration
Thank-You Detector works with the ticket’s configured reopening behavior.
| Reopening Configuration | Behavior |
|---|---|
| Do not perform any action on the ticket state | The ticket status is not changed by the incoming reply. |
| Automatically change ticket status to open | An acknowledgment-only reply can remain closed when detected. A reply containing a new question or issue reopens the ticket. |
| Create a new follow-up ticket | A follow-up ticket is created according to the configured behavior. Thank-You Detector does not suppress the configured follow-up-ticket creation. |
Review the ticket reopening settings together with Thank-You Detector to confirm the expected behavior for resolved and closed tickets.
Understand Requester and CC Behavior
Thank-You Detector can apply in the following scenarios:
- A contact replies through the customer portal or another supported source.
- A CC participant who is a contact replies.
- An agent replies through the Agent Portal while also being the ticket requester.
The detector does not apply in the following scenarios:
- A CC participant who is an agent replies.
- An agent who is not the requester replies through the Agent Portal.
The detector evaluates eligible customer-side acknowledgments. Agent collaboration messages are not treated as customer thank-you replies.
Review Thank-You Detector Activity
When Thank-You Detector identifies an acknowledgment-only reply, review the ticket history or conversation to confirm the recorded outcome.
Depending on the ticket interface, the history can indicate that:
- A thank-you message was detected.
- The ticket remained closed.
- The reply was recorded as a note.
If the detector does not identify an acknowledgment and the ticket reopens, a Thank-You Detector history entry may not be recorded.
Consider the following behavior:
- The detector applies only to eligible replies on resolved or closed tickets.
- The ticket must match the configured Brand and Source scope.
- The detector evaluates reply intent and context, so similar wording can produce different outcomes when the surrounding content differs.
- Replies containing actionable content reopen according to the normal ticket behavior.
- Follow-up-ticket creation is controlled by the applicable reopening configuration.
- The detector does not replace review of complex customer messages that return to the queue.
Troubleshooting
A Ticket Reopened After a Thank-You Reply
Confirm that:
- The ticket was resolved or closed when the reply was received.
- Thank-You Detector was enabled.
- The ticket’s brand matched the configured Brand scope.
- The reply source matched the configured Source scope.
- The message did not contain a new issue, question, request, unresolved problem, or negative statement.
- The ticket reopening configuration supports keeping acknowledgment-only replies closed.
The Update Button Is Unavailable
Change the Thank-You Detector toggle, Brand selection, or Source selection. The Update button becomes available after a configuration change.
The Detector Works for Some Brands but Not Others
Review the Brand field. Only tickets from selected brands are included. Leave the field empty to include all brands.
The Detector Works for Some Sources but Not Others
Review the Source field. Only tickets associated with selected sources are included. Leave the field empty to include all sources.
A Follow-Up Ticket Is Created for a Thank-You Reply
Review the ticket reopening configuration. If the system is configured to create a new follow-up ticket, Thank-You Detector does not suppress that configured action.
Frequently Asked Questions
-
What does Thank-You Detector do?
Thank-You Detector identifies acknowledgment-only customer replies on resolved or closed tickets and keeps the tickets closed. -
Where do I configure Thank-You Detector?
Go to AI Center > AI 2.0, enable AI Copilot, and select Thank-You Detector. -
Does Thank-You Detector use keyword matching only?
No. Thank-You Detector uses AI to evaluate the intent and context of the reply. -
Does Thank-You Detector run on Open or Pending tickets?
No. The detector evaluates replies only when the ticket is already resolved or closed. -
Does Thank-You Detector apply to CC replies?
It can apply when the CC participant is a contact. It does not apply when the CC participant is an agent.