Cold deals: detect inactivity and reactivate the contact

A pipeline full of "lukewarm" opportunities nobody has touched in weeks is money sitting still. The rep forgets, the contact goes cold, and the deal dies without a single recovery attempt. With the Omnifox workflow engine you can reactivate cold deals automatically: the system detects inactivity and fires a re-engagement touch without relying on anyone's memory.

In this guide we build the flow with the workflow editor (chat/omnichannel).

The flow at a glance

Trigger Deal with no activity (N days) → Send WhatsApp template → Create follow-up task → Log activity

Optionally we add an If (single rule) condition so we don't bother deals that are about to close or flagged as do-not-contact.

Step 1: the inactivity trigger

The trigger is Deal with no activity (cold deal), which fires when a deal goes N days without any logged interaction. In the trigger settings you set the threshold: 7, 14, or 30 days depending on your sales cycle.

This trigger belongs to the CRM family and comes with deal variables ready to use:

• {{$trigger.title}} — the opportunity name.
• {{$trigger.amount}} — the amount.
• {{$trigger.stage_name}} — the stage where it went cold.

Remember: one trigger per workflow. If you want different thresholds (one at 7 days, another at 30), build separate workflows.

Step 2: filter before you bother anyone

Before sending anything, add an If (single rule) node or a Switch to exclude cases where reactivating would backfire. Example rules:

• Stage other than "Negotiation" or "Proposal sent" (don't poke what's already hot).
• The contact doesn't carry the do-not-contact tag.
• The amount is above a certain value (prioritize big deals).

The Contact has tag node is perfect for the second case: you branch on whether an exclusion tag is present.

Step 3: the reactivation touch

Since more than 24 hours have probably passed since the last message, on WhatsApp you need an approved template. That's why we use Send WhatsApp template and not Send message.

Personalize the template with variables so it doesn't read like a robot:

Hi {{$contact.first_name}}, I wanted to pick up {{$trigger.title}} again. Still interested, or should we pause it for now?

If the deal's channel is email rather than WhatsApp, swap that node for Send email to customer. And if the contact replied less than 24 h ago, a plain Send message is enough.

Step 4: create the task for the rep

The automated message opens the door, but a human closes. So we chain Create follow-up task: it generates a task for the deal owner like "Call {{$contact.first_name}} — cold deal reactivated" due in 2 days.

That way the rep doesn't depend on remembering: the task shows up in their list, with context and a clock running.

Step 5: leave a trail with Log activity

So the pipeline keeps its history, we close with Log activity (a CRM note/activity). This records on the deal's timeline that an automatic reactivation was sent on day X. Next time someone opens the opportunity, they see exactly what happened.

This also avoids the worst mistake: reactivating the same contact twice because nobody knew they'd already been messaged.

Variants worth adding

• Stagger the re-engagement: after Send WhatsApp template add a Wait node (3 days) and an If (did they reply?). If no reply, Update deal to stage "Lost" or send a second template.
• Internal heads-up: a Notify team by email or Post to Team node so the sales lead sees which deals are being reactivated.
• Reassign: if the original owner is gone, Assign deal owner in round-robin before creating the task.

Common mistakes

• Using Send message instead of a template. Outside WhatsApp's 24 h window, a free-form message won't deliver. For cold deals that window has almost always passed: use Send WhatsApp template.
• Not filtering hot deals. Without the If node, you'll bother opportunities that were about to close. Exclude advanced stages.
• Miscalibrated threshold. 3 days is too soon for many B2B cycles; 60 days may already be too late. Tune it to your real funnel.

How to know it's working

An automation you don't measure gets abandoned. Since every run leaves a trail via Log activity, you can filter opportunities in the CRM by the "automatic reactivation" note and see how many moved stages again. Add an Add tag node (say reactivated) right after Send WhatsApp template: that segments the pipeline so you can compare the close rate of reactivated deals against those that never got the touch. If the reactivated tag ends up closing above average, you have proof the workflow pays. And when a contact does reply, a separate workflow with a Message received trigger can strip the reactivated tag and ping the rep with Add internal note that the cold deal just thawed. That closed loop keeps your reps focused on the opportunities that actually re-engaged instead of chasing everyone blindly.

Start today

Automatically reactivating what goes cold is one of the cheapest ways to lift conversion without adding reps. In Omnifox this workflow takes minutes to build and runs on its own, every day. Set your threshold and let the pipeline clean itself up.