Demo request abandonment re-engagement

Outcome. A contact who reaches the demo request page but never submits the form gets one re-engagement email with an easier next step, instead of being left with no follow-up because they never became a lead through the form.

Workflow map Enrollment, branches and actions at a glance lead-nurturing-020

flowchart TD
    A[Page view: demo request page, known contact] --> B{Wait until form submitted, max 3 days}
    B -- Submitted in time --> C[No action, lead-routing handles it]
    B -- Timed out --> D[Set demo_request_abandoned = true]
    D --> E{Reengagement already sent?}
    E -- No --> F[Send reengagement email]
    F --> G[Set reengagement_sent = true]
    E -- Yes --> H[No action]

When to use it, when not to

• UseUse when the demo request page is a distinct, trackable URL and the form on it is the only path to becoming a demo-request lead.
• UseUse it to offer a lower-friction alternative (a recorded demo, a shorter form, a chat option), not to re-push the same form that already did not convert.
• SkipDo not use it if the demo page also serves anonymous, unidentified traffic almost exclusively. This workflow only reaches contacts who are already known, cookied visitors.
• SkipDo not run this on a contact who did submit the form. That handoff belongs to lead-routing, which should own fast follow-up for actual demo requests; this fiche is for the ones who did not finish.