Getting Started
- How Plumsail HelpDesk works
- HelpDesk installation
- Quick HelpDesk configuration
- Frequently asked questions
- Resources
Configuration guide
- Email settings
- Triggers
- Web widget
- Tab for Microsoft Teams
- Customize widget forms
- Customize ticket and contact forms
- Customer satisfaction survey (CSAT)
- Scheduling tasks and reminders
- Business hours and holidays
- SLA policy
- Localization
- Appearance settings
- Color theme
- Customize ticket statuses
- Reports customization
- Ticket numbering customization
- Update HelpDesk
- Uninstall HelpDesk
User guide
- Home page
- Ticket management
- Ticket search
- Knowledge base
- All tickets
- Contacts
- My contact
- Reports
- Canned responses
- Ticket merging
- Ticket splitting
- SLA policies
General
- Version history
- Data protection and security
- Data center location
- Licensing details
- Billing and subscription management
- Support plans
- Status page
Power Automate (Microsoft Flow) and Public API
How to
- Notifications
- Automations
- Automatically evenly assign tickets to agents
- Skill-based ticket assignment
- Assign tickets based on weights
- Assign ticket to first agent who replies
- Assign ticket to multiple agents
- Assign ticket to specific person
- Assign ticket based on forwarding address
- Detect changes made by others
- Edit ticket’s properties from mailbox
- Reassign ticket from disabled user
- Start a workflow with a trigger
- Close tickets if customer hasn't replied
- Create a new ticket in HelpDesk from a Twitter mention
- Submit tickets from an online form with the help of Power Automate (Microsoft Flow)
- Import Microsoft 365 users into contacts list
- Use SharePoint HelpDesk with Microsoft Teams for employee onboarding
- How to forward a ticket from one HelpDesk instance to another
- SLA
- Ticket management
- Custom charts and views
- Advanced
Close tickets when customers do not reply in SharePoint HelpDesk
Tickets awaiting a customer reply can accumulate and distract the support team from current tasks. Automatically closing these tickets after a waiting period saves agents from closing them manually.
Plumsail HelpDesk is a solution for deploying a ticketing system based on SharePoint Online. It includes HelpDesk Scheduler, which allows you to perform recurring or one-time actions on unsolved tickets updated within the last 30 days. These actions are executed on a schedule defined in a task.
In this article, you will see how to create the task that will automatically close all tickets without a reply from a customer if 3 days have passed after support specialist (agent) replied.
Create or open a task
Open Settings from the left navigation menu, then select Scheduler.

Select New task to create a scheduler task, or select an existing task’s title to edit it.

Enter a descriptive task title so that other users can understand its purpose. Ensure that Active is enabled so the task runs on schedule.

Configure the schedule
Configure when the task runs using standard scheduling options or advanced CRON syntax. In this example, select Daily, set a nighttime Start time, and set Recur every to 1 day.

Set conditions and action to close tickets
Define ticket conditions and configure actions in the Conditions and Actions blocks.

The condition block works in the same way as in triggers. After replying to a customer, agents should set the ticket status to Pending if they are waiting for a customer reply. When the customer replies, the ticket status automatically changes to In progress, so the ticket no longer matches this task’s conditions.
To find tickets that are still waiting for a customer reply, combine both conditions using AND:
[Ticket.Status.Title]equals'Pending'.[Ticket.Metadata.LastPendingDate]less thanAddDays(Today(), -3).
You can select [Ticket.Status.Title] from the dropdown list. To define the second condition, use advanced condition syntax. The Today() function returns the current date, and the AddDays() function allows you to add an arbitrary number of days to the chosen date. To subtract 3 days from the current date, pass -3 to AddDays: AddDays(Today(), -3).
Finally, choose a Set field action in the Actions block, select Status, and set its value to Solved. Select Save & Close to save the task.

Review execution logs
Review task executions under Execution logs. If you need, you can export the logs.

Enable Record runs to ticket history to add scheduler run information to the ticket history.

Summary
The scheduler will now run at the configured time and set matching Pending tickets to Solved. Review the execution logs and ticket history to confirm that the task processes the expected tickets.