The Workflow Library

Library / Deal hygiene / deal-hygiene-037

Multi-threading check: single-contact deal flagged for stall risk

Deal hygieneDealSales Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. A mid-funnel deal still associated with only one contact gets flagged, so reps widen the relationship before a single champion going quiet takes the whole deal down with them.

Workflow map Enrollment, branches and actions at a glance deal-hygiene-037
flowchart TD
    A[Deal in mid-funnel stage, exactly one associated contact] --> B[Set Single Contact Risk Flag = true]
    B --> C[Create task: add a second contact]
    C --> D[Notify owner]
    D --> E[Delay 10 business days]
    E --> F{Still exactly one contact?}
    F -->|yes| G[Notify manager, still single-threaded]
    F -->|no| H[Reset flag to false, exit]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it on deals past initial qualification, where a single point of contact is a real risk, not on brand-new deals where one contact is normal.
  • UseUse it as a coaching signal for the rep, not an automatic block, multi-threading is a sales behavior, not something a workflow can do on the rep's behalf.
  • SkipDo not use it on inherently single-contact motions, for example a sole proprietor or a very small company where a second contact genuinely does not exist.
  • SkipDo not use it as the only signal for deal risk, pair it with deal-hygiene-022's combined at-risk flag once both are running.
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.7 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 deal hygiene 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.