Skip to content

Escalate a manual sequence step to a task when it is overdue by 48 hours

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Data Hub Professional.

Contact6 stepsUpdated for HubSpot seat pricing
OutcomeA manual sequence step (a call or a LinkedIn touch) that a rep has not completed after 48 hours gets escalated to the manager instead of quietly sitting overdue in the rep's queue.
Workflow mapsales-ops-037
Sequence-generated task created leads to Delay 48 hours. Delay 48 hours leads to Custom code: check original task status. Custom code: check original task status leads to Still not completed?. Still not completed? leads to Yes: Create escalation task for manager; No: End, no action. Create escalation task for manager leads to Increment escalation count. Yes No Sequence-generated task created Delay 48 hours Custom code: check original task status Still not completed? Create escalation task for manager End, no action Increment escalation count
Sequence-generated task created leads to Delay 48 hours. Delay 48 hours leads to Custom code: check original task status. Custom code: check original task status leads to Still not completed?. Still not completed? leads to Yes: Create escalation task for manager; No: End, no action. Create escalation task for manager leads to Increment escalation count. Yes No Sequence-generated task created Delay 48 hours Custom code: check original task status Still not completed? Create escalation task for manager End, no action Increment escalation count

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

When to use it, when not to

Use it

  • Use it when sequences mix automated emails with manual steps (calls, LinkedIn touches, personalized notes) and manual steps are the ones most likely to slip.
  • Use it as a safety net for a team still building the discipline to work manual sequence tasks daily, not as a permanent substitute for that discipline.
Read more on when to use itShow less

Skip it

  • Do not use it if your sequences are entirely automated email steps with no manual actions; there is nothing here to escalate.
  • Do not use it if 48 hours is too aggressive for your team's task-clearing cadence; a rep with a reasonable backlog will trigger this repeatedly and the escalations will be noise instead of signal.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 3 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 6 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 5

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 2 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV, code

The properties JSON creates the fields in one call. The workflow JSON documents the build. The custom coded action ships as a ready-to-paste .js file.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Sales ops spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library