To automatically update a ticket when a customer replies, first check whether your help desk already does it. If it does not, create a rule that detects the reply, checks the ticket’s current status and any scope conditions, then sets the intended active status. The exact behavior differs by platform: a reply may reopen the same ticket, leave it resolved, or create a linked follow-up.
In Intercom, a reply to a ticket in Waiting on customer or Resolved automatically changes it to In progress, so no workflow is needed for that case. Freshdesk provides a preconfigured rule for reopening resolved or closed tickets after a customer response. Zendesk reopens solved tickets after a requester adds a comment, but a response to a closed ticket creates a follow-up request instead.
Compare the default behavior before adding a rule
The key distinction is not just which message triggers an update. Check the ticket’s starting state, whether the platform changes that state automatically, and what happens when the ticket is closed.
| Platform | Customer reply and starting state | Result | When to configure a rule |
|---|---|---|---|
| Intercom | Reply to Waiting on customer or Resolved | Automatically changes to In progress. If custom In progress states exist, the first state in that group for the ticket type is selected. | For additional behavior, such as responding to teammate replies or limiting updates to selected ticket types. Intercom, June 23, 2026: workflow guidance and ticket state reference. |
| Freshdesk | Customer response to a resolved or closed ticket | The preconfigured “Automatically Reopen tickets after the customer responds” rule reopens it so it appears in the open-ticket view. | Enable, disable, or modify the standard rule if its behavior needs to change. Freshdesk: ticket-update automation guidance. |
| Zendesk | Requester comments on a solved ticket | The solved ticket reopens. | No custom rule is needed for that documented behavior. Zendesk: ticket lifecycle guidance. |
| Zendesk | Response to a closed ticket | A follow-up request referencing the original is created; the closed ticket itself does not reopen. | Decide whether this linked follow-up is the desired process. Zendesk: ticket lifecycle guidance. |
Zendesk’s closure timing also affects which path a reply takes: its default automation closes a solved ticket four days later. If an administrator deactivates that automation, a system rule closes it 28 days after it is solved. These are Zendesk rule timings, not response-time or productivity measures. See Zendesk’s lifecycle article.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →#1 Best Overall
- Record Book: the package includes 1 daily service record book with 80 sheets, offering ample space to meet daily logging needs; It's a practical tool for tracking appointments, managing tasks, and enhancing customer service efficiency
- Ideal Size: measuring 8.5 x 11 inches, this activity log notepad balances portability and capacity; With 80 pages, it's ideal for daily use in the automotive industry, serving as a reliable service record management tool for consistent tracking
- Nice Quality: crafted from quality paper, the activity log book features reliable coil binding for easy page turning and tear-out; Its structured layout provides ample space for detailed entries, supporting effective schedule planning
- Friendly Design: designed for convenience, the daily log book's coil binding allows effortless sheet removal whenever needed; The intuitive layout ensures quick access to logging sections, making daily activity recording simple and efficient
- Versatile Usage: the service log book is a helper for the automotive industry or individuals to record scheduled maintenance, the shop can use it to register the maintenance needs of different customers, individuals can use it to keep track of flat rate hours
Decide what the rule should do
Define the triggering reply
Specify whether the event is a customer or requester message, any comment, or a teammate reply. Those events are not interchangeable. For example, Intercom’s documented workflow pattern uses the Inbox event “Customer sends any message”; adding a teammate-reply use case requires additional workflow configuration. See Intercom’s workflow guidance.
Choose eligible starting states and the target
Set out which current states qualify—such as Waiting on customer, Solved, Resolved, or Closed—and the desired active state. A single “reopen on reply” rule may not cover all of them. In particular, a platform may create a follow-up for a closed ticket instead of reopening it, as Zendesk does.
If the help desk supports custom statuses, find out how it selects the target. In Intercom, when multiple custom In progress states exist, a customer reply sends the ticket to the first state in that group for its ticket type. Administrators can make a desired state the default by ordering it first. See Intercom’s guidance.
Set the scope
Use available conditions to limit the update to the ticket types or current states it should affect. Intercom workflows can filter by linked ticket type or current state. Scoping prevents a general reply rule from changing tickets that should follow a different process.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsChoose what a closed-ticket reply means
Decide whether a customer response should revive the original ticket or begin a linked follow-up. That decision matters for routing and history as well as status: Zendesk creates a follow-up request for a reply to a closed ticket, while Freshdesk’s preconfigured rule can reopen closed tickets after a response. These products therefore do not treat “closed” as a universal status with one standard reply behavior.
Configure reply-based status changes by platform
Intercom: use the built-in change for ordinary customer replies
For a reply to a ticket in Waiting on customer or Resolved, Intercom automatically changes the state to In progress. A workflow is unnecessary for this ordinary customer-reply case. If the ticket type has custom In progress states, the first state in that group is the destination; reorder the states if a different one should be the default. Intercom documents these behaviors in its June 23, 2026 workflow guidance and state reference.
Rank #3
- Record all incoming calls needing service
- 2-part carbonless
- Spiral bound on left
- Part one is perforated to give to service person, part two remains in book for records
- White, canary paper sequence
Intercom: create a workflow for additional behavior
Use this workflow approach when you need to cover a case beyond the built-in behavior—for example, a teammate reply or a rule limited to particular ticket types:
- Create a reusable workflow with a Set ticket state action, then save it live.
- Create an Inbox workflow triggered by Customer sends any message.
- Add optional filters, such as the linked ticket type or current ticket state, to restrict which tickets are changed.
- Call the reusable workflow from the Inbox workflow.
- Test it with a test conversation converted to a ticket. Set the ticket to Waiting on customer, reply as the customer, and confirm that the resulting state is the one you intended.
The action runs only when the configured conditions and filters match. Intercom documents Workflows as a visual no-code builder and includes reply-based ticket-state updates among its automation uses; see its workflow setup guidance and Workflows overview.
Freshdesk: adjust the preconfigured reopen rule
Freshdesk documents a ticket-update automation named Automatically Reopen tickets after the customer responds. It reopens a resolved or closed ticket after a customer response so the ticket appears in the open-ticket view. Administrators can enable, disable, or modify standard rules. If closed tickets should not reopen, Freshdesk says to modify or disable the rule for Closed tickets. Its guidance also describes using a webhook to create a new ticket from a reply to a closed ticket when that is the preferred handling. See Freshdesk’s ticket-update automation guidance.
Rank #4
- Custom Receipt Book with Logo Create a custom receipt book with your logo, business name, address, phone number, email, customer information area, payment method, and personalized business layout.
- Carbonless 2-Part Design The 2-part carbonless form design allows duplicate copies without separate carbon paper, helping businesses record payments, services, sales, and customer transactions.
- Great for contractors, repair services, auto shops, cleaning companies, landscaping crews, salons, retail shops, mobile vendors, delivery businesses, and local service providers. Bulk customization is supported for teams, organizations, service companies, and repeat business use.
- Made for Service Industries Perfect for auto detailing, towing, HVAC, home repair, landscaping, cleaning companies, salons, pet grooming, mobile vendors, contractors, and small business owners.
- Multi-Purpose Business Forms Can be used as invoice forms, receipt books, work orders, sales orders, estimate forms, quote forms, service tickets, payment records, and customer copy forms.
Zendesk: account for solved and closed as separate states
Zendesk’s documented lifecycle behavior handles the two states differently: a requester’s new comment reopens a solved ticket, while a response to a closed ticket creates a follow-up request referencing the original. The follow-up is not the original ticket reopening. Zendesk’s default automation closes solved tickets four days later; if that automation is deactivated, a system rule closes them after 28 days. See the Zendesk lifecycle article and its closure automation guidance and system-rule documentation.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Test the rule before enabling it broadly
Test each path that could produce a different outcome, rather than checking only one ordinary reply. Intercom explicitly recommends testing with a test conversation converted to a ticket, setting it to Waiting on customer, replying as the customer, and confirming the resulting state. That is Intercom’s recommended test procedure, not a claim of independent testing.
- Reply as a customer or requester to each eligible starting state.
- Try a teammate reply separately if the rule is meant to include teammate activity.
- Check a ticket that should be excluded by type or another filter.
- For platforms with custom statuses, confirm the exact destination state.
- Test closed-ticket replies and confirm whether the expected result is reopening or a linked follow-up.
These checks expose redundant rules, incorrect scope, and unintended changes before the automation affects live tickets.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallChoose the right setup for your support process
- Use the built-in behavior when it matches the reply event, starting state, and target you need. Avoid adding a duplicate rule that could conflict with it.
- Use a conditional workflow or automation when you need to include additional reply types, restrict changes by ticket type or state, or choose a specific target state.
- Use a follow-up process for closed tickets when the original should remain closed and the new customer response should have its own linked record.
- Review the lifecycle timing when a solved ticket may become closed before the customer replies. This distinction is especially consequential in Zendesk, where the closed-ticket path creates a follow-up.
There is no universal status-change rule across help desks. The reliable pattern is to detect the intended customer event, inspect the current state and scope, and then apply the right active state—or create a follow-up if that is the intended closed-ticket process.
Frequently Asked Questions
How do I automatically reopen a ticket when a customer replies?
First check the platform’s built-in behavior. Intercom changes replies to Waiting on customer or Resolved to In progress; Freshdesk has a preconfigured rule that reopens resolved or closed tickets; Zendesk reopens solved tickets after a requester comments. Closed tickets may follow a different path.
Can I change a ticket status automatically when a customer responds?
Yes. Use the help desk’s built-in rule when it matches the desired event and status, or configure a conditional automation where needed. Set the trigger, eligible current states, scope, and target explicitly.
Should a reply to a closed ticket reopen the original?
That depends on the support process and the platform. Zendesk creates a linked follow-up request for a response to a closed ticket; Freshdesk’s preconfigured rule can reopen closed tickets. Decide whether the original record should resume or remain closed with a new follow-up.
Free tools Windows power users keep installed
One-click scans. No signup required.
Will a reply always move a ticket to the same active status?
No. Intercom’s custom In progress destination depends on the order of custom states for the ticket type. Other platforms may distinguish among waiting, solved, resolved, and closed tickets, so check both the starting state and the configured destination.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
