The completion automation is designed to enhance the efficiency and clarity of managing requests within our platform. This feature automatically completes requests that have been idle for a specified period, ensuring that only active and pending requests are visible to users. This helps in maintaining a clean and manageable workflow, enabling our users to focus on current tasks without the clutter of idle requests.
How It Works
Definition of Idle Requests
An idle request is defined as any request that has not been interacted with by any user within the last 21 days. This feature specifically targets requests that are marked as "Ready for Review" or "Awaiting Response".
Automatic Completion
When a request meets the idle criteria, the platform will automatically mark it as complete and set the status to completed. This action is triggered to prevent clutter and ensure that the user interface remains focused on requests that require attention.
Notifications and Comments
Each automatically completed request will have a comment added by the system detailing the reason for its completion. A notification will also be sent out to ensure transparency and keep all relevant users informed.
User Control and Feedback
While users cannot directly configure the timeframe for which a request is considered idle, feedback is highly encouraged. If adjustments are needed, users can contact support to discuss changes to the default 21-day period. This ensures that our automation aligns with the diverse needs and operations of all our clients.
Benefits
Improved Request Management
By automatically completing idle requests, users will see a more accurate and streamlined view of their active and pending tasks. This reduces confusion and improves the ability to manage ongoing projects efficiently.
Enhanced Platform Performance
The removal of idle requests ensures that the system is only processing and displaying requests that are genuinely active, improving overall platform performance and user experience.
Continued Progress
With idle requests cleared, active slots become available more frequently, allowing new requests to enter the queue and be addressed in a timely manner.
Revisiting Completed Requests
Should there be a need to revisit a request that was completed due to inactivity, users can utilize the feedback tool to initiate a review or directly reopen the request. This allows our team to accurately scope any necessary revisions and reintegrate the request into the production queue as needed. Completed requests can all be found in the completed section of your requests dashboard.
Need Help?
If you have any questions remember that support is just a click away. Use the chat feature to connect with a Customer Success Representative who can provide real-time assistance.