In a low code/no code workflow, escalation policies can be configured to manage business requests that haven't been acted upon within a specific timeframe. These policies can trigger various actions, such as sending notifications to the approver, the approver's manager, potential approvers' managers, or the initiator. Other actions include adding additional assignees to the business request or auto-closing the step or the entire request after a certain period if no action is taken. Suppose you have an approval flow policy with multiple steps. You can create and map different escalation policies to each step. For example:
Notify the potential approver after one day
Add an assignee after two days
Auto-close the step with an "approved" status after three days
By following the steps below, you can ensure that escalation actions are triggered appropriately, enhancing the efficiency and responsiveness of the approval process.
Step 1: Creating Policies
...
...
...
...
...
...
...
...
...
Once an escalation policy is created, it must be mapped to specific approval steps:
...
...
...
Click the Edit icon.
...
In the Escalation Policy dropdown, select the desired escalation policy.
...
Save the changes.
Default Escalation Policy
A default escalation policy is applied if no specific policy is configured for an approval step. The default escalation policy typically includes:
Notify Potential Approver: Sends a notification to the potential approver after three days of no action.
Notify Potential Approver Again: Sends another notification after seven days of no action.
Notify Target Person's Manager: Sends a notification to the target person's manager after 15 days of no action.
Additional Configuration for Notify Escalation
...
...
...
...
...
...
...
...
...
...
Email Templates
...