The Workflow Library

Library / Sales ops / sales-ops-037

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

Sales opsContactData Hub ProfessionalIntermediate~50 min to buildFull spec

Outcome. A 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 map Enrollment, branches and actions at a glance sales-ops-037
flowchart TD
    A[Sequence-generated task created] --> B[Delay 48 hours]
    B --> C[Custom code: check original task status]
    C --> D{Still not completed?}
    D -->|Yes| E[Create escalation task for manager]
    E --> F[Increment escalation count]
    D -->|No| G[End, no action]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when sequences mix automated emails with manual steps (calls, LinkedIn touches, personalized notes) and manual steps are the ones most likely to slip.
  • UseUse 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.
  • SkipDo not use it if your sequences are entirely automated email steps with no manual actions; there is nothing here to escalate.
  • SkipDo 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.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.3 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.6 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.5 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

or the sales ops pack, 39 EUR

One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.