To set up a stalled deal alert, pick an inactivity rule, confirm your plan, attach an action, then set the delay. Copper documents that if you set the threshold to 7 days, opportunities will turn red on the 8th day of inactivity.
Key takeaways: what an inactivity alert needs
- Define the specific rule that triggers the flag, such as a set number of days without activity.
- Verify that your current subscription plan includes access to workflow automation features.
- Select the action the system performs when the trigger fires, like creating a task for the owner.
- Determine the delay period before the action executes, and confirm whether the system respects communication windows during execution.
- Understand how the platform calculates activity dates to ensure the trigger logic matches your intent.
The threshold setting defines when a deal is considered stalled. According to Copper, if you set the threshold to 7 days, opportunities turn red on the 8th day of inactivity. This indicates the flag appears one day after the threshold is met. HubSpot offers a different approach where a workflow can trigger a task for a contact owner to follow up when the contact's Date entered Sales Qualified Lead is more than 5 days ago, according to HubSpot. These examples illustrate that thresholds vary by vendor and are not universal standards for all teams.
Steps 1 and 2: pick the inactivity rule and check your plan
Selecting the right inactivity threshold is the first technical decision. In Copper, you define a specific number of days for a deal to remain inactive before it triggers a visual flag. For instance, if you set the threshold to 7 days, your opportunities will turn red on the 8th day of inactivity Copper. This indicates that the alert appears one day after the defined limit expires. You must choose this value based on how long your sales team typically waits between touchpoints. The 7-day figure is a specific example from Copper documentation, not a universal standard for every sales organization. Adjust this number to match your actual follow-up cadence before saving the rule. For other warning signs, see stale deal signals.
HubSpot offers a different approach by tying the trigger to a lifecycle stage date rather than a generic idle period. A documented workflow triggers a task for a contact owner to follow up when the contact's Date entered Sales Qualified Lead is more than 5 days ago HubSpot. This method focuses on the time elapsed since a specific stage change occurred.
Before configuring these rules, verify that your current subscription includes access to workflow tools. Not every CRM plan provides the same automation capabilities, so checking your license level prevents setup errors later. In Close, workflows are only available on the Growth and Scale plans Close. If your team uses a lower-tier plan, you cannot create these automated alerts until you upgrade.
EspoCRM requires a specific add-on to enable its automation features. The Workflows tool is available in Advanced Pack EspoCRM. Check with your administrator to confirm whether the Advanced Pack is licensed for your instance. If it is not, the feature remains inaccessible. Verifying this requirement early saves time during the configuration process.
Illustrative example: a 7-day inactivity rule
Imagine a team that sets its threshold to 7 days and attaches a follow-up task for the deal owner. A deal with no activity after day 0 would be flagged on day 8, one day after the threshold passes. If the team then sets a 1-hour delay on the task, the task is created 1 hour after the trigger. Before saving, the team checks that the resulting time falls inside an active communication window, then writes down the threshold, action, delay and window. Writing each choice down lets the team check the rule at its next quarterly review. The numbers are chosen for illustration only; your own follow-up cadence should set the threshold.
Steps 3 and 4: choose the alert action and set the delay
Once you have selected your inactivity rule, the next move is to define what happens when that rule triggers. The action determines whether the CRM creates a task, updates a record field, or changes a stage. You must match this action to the capabilities of your specific platform. HubSpot allows you to update stages automatically in your settings or using other tools such as workflows or chatflows.
For platforms focused on process automation, the scope of actions may differ. EspoCRM describes its Workflows tool as a way to automate business processes in an easy way. Specifically, it can automatically modify records when specific conditions are met. This capability allows you to alter record data based on the stalled status identified in previous steps. When configuring this step, ensure the condition logic aligns with your chosen inactivity threshold so the modification occurs at the correct moment.
If you are using Close, the available actions center on engagement tasks. Close states that workflows can be used to automate tasks and outreach. This ensures the team receives a prompt to re-engage with the prospect rather than just seeing a visual flag.
After selecting the action, you must define the timing of that action relative to the trigger event. This is where the delay setting comes into play. In Close, you can delay a Workflow step from 1 minute up to 365 days. However, if you want to give a deal a final chance before flagging it, you might set a delay of several hours or days within that 1-minute to 365-day window.
Steps 5 and 6: check the send window and read the activity dates
Step five requires checking whether your workflow step lands within a permitted communication block. In Workflows | Close Help Center, a step scheduled at 9:32 AM with a 1 hour delay computes to 10:32 AM. This places the step into the 10:00 to 11:00 AM “block” or communication window, so the action performs between 10:32 AM and 11:00 AM. For longer delays of 24+ hours, the window covers the entire day according to the communication schedule. Verify that your alert time falls inside an active block before saving the workflow.
Step six involves reading how your CRM calculates inactivity dates. According to Pipedrive glossary - Knowledge Base | Pipedrive, the last activity date shows the date of the last activity marked as done. The next activity date shows the date of the next scheduled activity not yet marked as done. If you rely on these fields for your stall threshold, confirm that your team marks activities as done promptly. For how activities attach to deals, see Activity linking: 8 rules for deals and visibility.
Check your deal list for three open opportunities and note their last activity dates. Compare those dates against your chosen inactivity rule to see if any would currently trigger an alert. This manual check validates that your date definitions match your operational reality before you automate the process.
Stalled deal alert reference table: five vendors side by side
The following comparison outlines the specific trigger rules, plan prerequisites, and access permissions documented for each platform. Use this overview to verify whether your current subscription includes the necessary workflow capabilities before configuring inactivity alerts.
| Publisher | Documented rule |
|---|---|
| Copper | Opportunities turn red on the 8th day of inactivity when the threshold is set to 7 days |
| HubSpot | Triggers a task for the contact owner when Date entered Sales Qualified Lead is more than 5 days ago |
| EspoCRM | Workflows tool is available in Advanced Pack; only administrators can view or configure workflows |
| Close | Workflows are only available on Growth and Scale plans; step delay ranges from 1 minute up to 365 days |
| Pipedrive | Last activity date shows the last activity marked as done; next activity date shows the next scheduled activity not yet marked as done |
Close restricts its workflow features to specific higher-tier subscriptions, while EspoCRM limits configuration rights strictly to administrator roles. Verify your license level against these requirements before building the logic. If your plan lacks the necessary tier, the alert will not execute regardless of how you set the thresholds. Check your account settings to confirm which of these constraints apply to your team's current access.
What to keep on file once the alert is live
Document who holds configuration rights and where the workflow settings reside. In EspoCRM, you can access Workflows from the Administration panel EspoCRM. Record this location in your runbook so any team member knows exactly where to look when verifying an active rule. The same documentation should note that only administrators can view or configure workflows EspoCRM. Write down the specific threshold values and delay settings you selected during setup. While other sections cover how to pick those numbers, keeping a static record of what was chosen prevents drift during quarterly reviews. Note whether the alert triggers a task, updates a stage, or sends a notification. This creates a clear baseline for comparing future performance against the original configuration. For forecast categories used in the review, see Pipeline, Best Case, Commit: Forecast Categories Explained.
Next step today: check whether your current plan includes workflows before you save any rule, using the plan rules in the table above.
Related guides: Check deal stage duration across 4 CRM tools · Log seller emails to the right deal: 4 CRM rules to check · Assign leads equally across 5 CRM platforms.
Stalled deal alert setup: frequently asked questions
What is a stalled deal alert and how do I set one up?
A stalled deal alert is an automation triggered by inactivity that flags quiet deals before your forecast call. To build it, pick the inactivity rule, confirm your plan and admin access, attach an action like a follow-up task, set the step delay, and check the send window. These steps ensure the alert runs within your CRM's documented limits.
Can I build a stalled deal alert on any Close plan?
No, workflows are only available on the Growth and Scale plans Close. If you are on a different tier, this feature is not accessible for building automated alerts. Verify your current subscription level before attempting to configure these steps.
Does Copper flag a deal on the day the inactivity threshold is reached?
No, if you set the threshold to 7 days, opportunities turn red on the 8th day of inactivity Copper. The flag appears one day after the threshold period ends. This timing rule applies specifically to the Copper platform as described in its documentation.
Who can configure workflows in EspoCRM?
Only administrators can view or configure workflows EspoCRM. Standard users do not have permission to change these settings. Ensure your RevOps team has administrator rights before starting the setup process.
How long can a Close workflow step be delayed?
You can delay a Workflow step from 1 minute up to 365 days Close. Choose a delay that aligns with your weekly review cycle.