Inactivity follow-up: remind the customer and escalate to a human

A customer messages, an agent replies… then silence. The conversation stalls halfway and nobody picks it back up. With an inactivity follow-up in Omnifox you rescue those stranded chats: the system sends the customer a reminder, waits a bit and, if they still don't move, escalates the conversation to a human agent. Fully automatic, built with real nodes from the workflow engine.

The trigger that sets it off: Contact inactivity

The backbone of this flow is the Contact inactivity (minutes) trigger. It fires when a contact has gone N minutes without activity inside an open conversation. You set the threshold: 30, 60, 120 minutes, depending on your support pace.

On top of that trigger we build the circuit:

Trigger: Contact inactivity (minutes)
   → Send message (reminder)
   → Wait (delay)
   → Condition: If (did the contact reply?)
        ├─ Yes → Close/Snooze conversation
        └─ No  → Transfer to an agent (Handoff)

Step 1 — The reminder with the Send message node

The first node after the trigger is Send message. Here you tap the customer on the shoulder with something warm and personalized:

"Hi {{$contact.first_name}}, still here for you. Did you get a chance to review what we shared? Let me know and we'll keep going."

Notice the {{$contact.first_name}} variable. If the contact has no name on file, the variable is replaced by an empty string and the greeting still reads fine.

If your main channel is WhatsApp and the 24-hour window has already closed, swap this node for Send WhatsApp template, which can reopen the conversation with an approved template.

Step 2 — Give it time with the Wait node

After the reminder you don't want to escalate right away: give the customer a chance to answer. That's what the Wait node is for, with the unit you choose (minutes, hours). A 15- to 30-minute delay is usually a good balance: enough to read and reply, not so long the case goes cold.

Step 3 — Decide with a Condition

Once the delay is over, a Condition node of type If evaluates the state. The most direct rule looks at {{$conversation.status}} or whether a new inbound message arrived:

• Yes branch (replied): the conversation is alive again. You can end the flow or use Snooze conversation so an agent picks it up calmly.
• No branch (still silent): time to escalate.

Step 4 — Escalate with Transfer to an agent

The silent branch runs the star node: Transfer to an agent (Handoff). The conversation leaves the automation and lands on a human, with full context. Lean on Omnifox's assignment routing so it reaches the right agent or team.

A very handy extra: right before the handoff, add an Add internal note node with something like "No customer reply after automatic reminder — please follow up." That way the agent instantly understands why the conversation showed up.

Variants worth building

• Double reminder: instead of escalating after a single nudge, chain Send message → Wait → Condition → Send message → Wait → Condition → Transfer to an agent. Two gentle taps before you bother a human.
• Escalate only hot leads: add a Condition — contact has tag (e.g. open-deal) before the handoff, so you don't spend agents on tire-kickers.
• Notify instead of transfer: if you'd rather not reassign, use Notify team by email or Post to the Team and let someone decide.
• Close instead of escalate: for low-value chats, the No branch can end in Close conversation with a polite sign-off message.

Common mistakes

• Threshold too short. A 5-minute trigger fires reminders while the customer is still typing. Start at 30–60 minutes.
• Forgetting the WhatsApp window. Outside 24 hours, Send message won't land; use Send WhatsApp template.
• Escalating with no context. Always add an Add internal note before the handoff.
• Infinite loops. If the reminder resets the inactivity, make sure the Yes branch closes or snoozes the flow so it doesn't repeat the cycle.

What you gain from this

An inactivity follow-up cuts abandoned conversations, improves your effective first-response time and keeps a hot lead from going cold over a simple human slip. Because the flow runs on its own, your team spends its time on active chats instead of chasing the ones who went quiet. And because everything is logged with the internal note, any agent can pick the case back up with full context. Over time, watch which threshold and which delay give you the best reactivation rate and tune them: there's no magic number, it depends on your audience and your channel.

How you build it in Omnifox

In the Omnifox workflow editor you pick the Contact inactivity trigger, drag in the Send message, Wait, Condition and Transfer to an agent nodes, wire them up and publish. The follow-up runs on its own, 24/7, with nobody watching the inbox.

Conversations left halfway are sales and tickets quietly slipping away. An inactivity follow-up rescues them before they go cold. Try it in Omnifox and make sure no customer is ever left hanging.