Letting recipients propose another date, and what your team has to do when they do.
Last updated
When you turn on Allow Recipients to Reschedule, recipients of a Request get a third option, Request Different Date, alongside approving and denying.
They choose that option, pick an alternative date, and can add a note explaining why. The page tells them plainly that the proposal requires approval, so nobody should come away believing the new date is confirmed.
The unit's card moves to Pending, which means waiting on your team, not on them. The proposed date is recorded against the request along with any note.
Nothing else happens automatically. The proposed date does not move the ticket's schedule, does not notify the technician, and does not reschedule anything. A reschedule proposal is information, and a person has to act on it.
You have three practical routes:
Turn it on when the date is genuinely flexible and you would rather negotiate than be denied. A reschedule proposal is a much better outcome than a flat no, because it tells you the person is willing.
Leave it off when the date is fixed, for example a contractor booked for a single day across many units. Offering flexibility you cannot honour produces proposals you have to decline, which is worse than never having offered.
Pending is the easiest status to lose track of, because it looks like waiting. Sweep the tab for it before the scheduled date. Someone who took the trouble to propose an alternative and then heard nothing is the person who is genuinely annoyed when a technician knocks.