The Workflow Library

Library / Renewal and expansion / renewal-expansion-016

NPS survey auto-send after renewal or usage milestone

Renewal and expansionContactService Hub ProfessionalSimple~25 min to buildFull spec

Outcome. A contact receives an NPS survey right after their account renews or hits a usage milestone, instead of on a flat calendar schedule that misses the moment that matters.

Workflow map Enrollment, branches and actions at a glance renewal-expansion-016
flowchart TD
    A[Deal closed won, Deal Type = Renewal] --> C{Last NPS Survey Sent Date older than 90 days or blank?}
    B[Usage Milestone Reached becomes true] --> C
    C -->|Yes| D[Send NPS survey]
    D --> E[Set Last NPS Survey Sent Date = today]
    C -->|No| F[No action]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when NPS currently goes out to the whole customer base on the same date each quarter, regardless of where each account sits in its lifecycle.
  • UseUse it alongside a renewal deal workflow (renewal-expansion-001 or renewal-expansion-019) so the survey lands right after a positive event.
  • SkipDo not use it as the first survey a brand-new customer receives. Sending NPS before anyone has used the product produces noise, not signal.
  • SkipDo not use it if no usage milestone signal exists yet. Without Usage Milestone Reached, only the renewal branch below will ever fire.
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.4 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 renewal and expansion 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.