Outcome. Grade A MQLs reach sales the moment they qualify, while Grade B MQLs get batched into a once-a-day notification, so a rep's inbox reflects real urgency instead of treating every MQL as equally time-sensitive.
Workflow map
Enrollment, branches and actions at a glance
marketing-ops-021
flowchart TD
A[Lifecycle stage = MQL] --> B{Contact grade?}
B -->|A| C[Notify sales rep immediately]
C --> D[Set mql_notified_date]
B -->|B| E[Delay until next 9:00 AM]
E --> F[Notify sales rep, digest framing]
F --> D
B -->|Not set| G[Notify marketing ops: grade missing]
When to use it, when not to
- UseUse once a lead grade (a fit indicator, separate from a behavioral score) is already set on the contact, whether by a manual sales-and-marketing agreed rubric or a calculated property built from firmographic fields.
- UseUse when sales has said real-time alerts for every MQL create too much noise and asked for a way to separate "call now" from "call today."
- SkipDo not use this as a substitute for marketing-ops-001. This fiche assumes the contact has already been promoted to Marketing Qualified Lead and a grade is present; it only changes how the notification behaves after that point.
- SkipDo not use if your portal has no grading concept at all yet. Build and agree on the grade definitions (what makes something A versus B) before wiring up the cadence logic.
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.8 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 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 marketing 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.
