The Workflow Library

Library / Sales ops / sales-ops-038

Notify a rep and add the contact to a marketing nurture list when a sequence ends with no reply

Sales opsContactSales Hub ProfessionalIntermediate~30 min to buildalso needs Marketing Hub ProfessionalFull spec

This spec is filed under Sales Hub Professional, and one of its steps belongs to another subscription: add to static list needs Marketing Hub Professional. Both are required to build it as written.

Outcome. A contact who goes through a full sequence without ever replying gets handed to marketing nurture automatically, and the rep gets a heads-up instead of the contact just quietly falling off everyone's radar.

Workflow map Enrollment, branches and actions at a glance sales-ops-038
flowchart TD
    A[Contact finishes a sequence] --> B{No reply during the sequence?}
    B -->|Yes| C[Notify contact owner]
    C --> D[Add to Marketing nurture - no sales reply list]
    B -->|No| E[End, no action]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when sales and marketing agree that "finished a sequence, never replied" is a fair signal to shift a contact from active outbound to a longer-cycle nurture track.
  • UseUse it to close the loop between sales-driven sequences and marketing-driven nurture, so effort is not wasted repeating the same outbound motion on someone who has shown no response.
  • SkipDo not use it if your sequences are short (one or two touches); a contact who does not reply after two emails is not the same signal as one who did not reply after a full multi-week cadence.
  • SkipDo not use it if the contact replied through a channel other than the tracked sequence email address (a LinkedIn message, a phone call); this fiche only checks the tracked email reply property.
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.2 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.4 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.PDF, Markdown, JSON
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.