I would like the ability to automate reminders for pending Update Requests where the user has not yet responded. When the user submits the update request, the reminders would stop. Ideally it could be built into Automations to select pending update requests and send a reminder after X days or within X days of a due date, with the original update request link. Another option would be to have a resend option in the Update Request options dropdown. Thanks!
It would be helpful if for update requests you could set a due date and for a reminder email to go out at a designated interval prior to that due date if the update has not been submitted. It would also be beneficial to allow for the manual sending of a reminder off of that update request record as well.
I agree. I get around this on some sheets, by sending update requests every day that criteria hasn't been met. But that's not really helpful as it generates multiple requests so that's not helping me train my users to keep their notifications cleared.
Also I'd like our managers to be notified of update requests for their employees that aren't complete. Either by a report or by escalating the update request to manager.
this is a must
as well we need a report to see all the pending update requests across different sheets
similar idea here and should be merged
please upvote here:
https://community.smartsheet.com/discussion/109848/update-request-reminder-resend
This is exaclty right! The ability to manually resend when necessary, automated reminders for pending requests, reports of pending requests, and notifications for managers so follow can happen.
Love the collaboration here!
I would like the ability to automate reminders for pending Update Requests where the user has not yet responded. When the user submits the update request, the reminders would stop. Pending update requests would send a reminder after X days or within X days of a due date, with the original update request link.
I agree that some kind of automatically recurring reminders "until they do what they're supposed to" are needed. This could (and should) also apply to the Approval workflow.
The current workaround of setting up multiples upon multiples of automations "in case" someone doesn't provide the required info is too cumbersome and can quickly push you up against the # of automation limit.