The Workflow Library

Library / Lead nurturing / lead-nurturing-034

Chatbot conversation without meeting booked nurture

Lead nurturingContactMarketing Hub ProfessionalIntermediate~35 min to buildFull spec

Outcome. A contact who talks to the website chatbot but never books a meeting gets a short follow-up sequence with a direct booking link, instead of the conversation quietly going nowhere.

Workflow map Enrollment, branches and actions at a glance lead-nurturing-034
flowchart TD
    A[chatbot_captured_no_meeting = true] --> B{Wait: meeting booked, max 3 days}
    B -- Booked --> C[Task: booked own meeting, informational]
    B -- Not booked, timed out --> D[Send: still want to talk, booking link]
    D --> E[Delay 2 days]
    E --> F{Clicked booking link?}
    F -- Yes --> G[Task: clicked link, follow up]
    F -- No --> H[Send: one last thing]
    C --> I[Set chatbot_captured_no_meeting = false]
    G --> I
    H --> I
    I --> J[Set chatbot_nurture_completed = true]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse when the chatflow's own logic ends in a hand-off ("someone will reach out" or a resource link) rather than a booked meeting.
  • UseUse to recover chat conversations that show real intent (the contact answered qualifying questions) but stalled before scheduling.
  • SkipDo not use this for chatbot conversations that were purely support questions with no sales intent; scope the enrollment property to the chatflow(s) built for that purpose only.
  • SkipDo not stack this with an immediate live chat handoff to a rep; if a human already picked up the conversation, exclude those contacts.
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.10 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 lead nurturing 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.