Outcome. An account using only a small slice of the product gets a proactive customer success outreach task, instead of low adoption only surfacing at renewal time when it is too late to fix.
Workflow map
Enrollment, branches and actions at a glance
renewal-expansion-039
flowchart TD
A[Customer, Feature Adoption Score < 40, past onboarding, no outreach yet] --> B[Create outreach task for owner]
B --> C[Notify owner]
C --> D[Set Low Adoption Outreach Created = true]
D --> E[Add to Low Adoption Accounts list]
When to use it, when not to
- UseUse it once a feature adoption or product usage measure already exists as a company property, populated by an integration, a product analytics sync, or a periodic CS review.
- UseUse it as an early-warning, proactive-outreach trigger, separate from renewal-expansion-015's health score decline, which reacts to a broader combined signal rather than adoption specifically.
- SkipDo not use it if no adoption measure exists yet; this fiche only reacts to the score, it does not calculate it from raw product event data. Pair it with an integration or with renewal-expansion-044's custom-code usage pull if raw data needs to be turned into a score first.
- SkipDo not use it on accounts still inside an onboarding window; low adoption in week two of a new account is expected, not a risk signal. Exclude recently-onboarded accounts explicitly.
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.
