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.
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]

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.
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.





