How to recover leads who did not book a meeting

TL;DR: This playbook shows you how to recover leads who did not book a meeting by setting up an automated workflow that catches form submissions without a follow-up booking — and re-engages them within minutes. You will need a CRM or form tool, a Zapier account, and SkipUp. Setup takes 30-60 minutes. For the strategic overview, see our complete guide to abandoned form lead recovery.

What do you need before setting up lead recovery?

Before you start, confirm you have everything on this checklist:

• CRM or form tool with webhook or trigger capability (HubSpot, Salesforce, Typeform, Webflow, Gravity Forms)
• Zapier account (free tier works for testing; paid for production volume)
• SkipUp account with an API key (see API key setup documentation)
• Calendar access for the meeting host — Google Calendar or Microsoft Outlook connected to SkipUp
• 30-60 minutes of uninterrupted setup time

Already have all of this? Skip ahead to the next section.

For a deeper discussion of what each component does and why it is needed, see Section 4 of the complete guide.

Should you use Zapier or the API?

There are two paths to build your recovery workflow. This playbook covers the Zapier path.

	Zapier (No-Code)	API (Custom)
Setup time	30-60 minutes	Days to weeks
Technical skill	None	Developer required
Customization	Moderate (Zapier steps)	Unlimited
Best for	Getting started, SMB teams	High-volume, custom logic

Building with the API instead? See Build a Lead Recovery Pipeline with the SkipUp API for the custom integration path.

How do you set up the form submission trigger?

Open Zapier and create a new Zap. Your trigger depends on which form or CRM tool you use.

Step 1: Click Create Zap and search for your form tool as the trigger app.

Step 2: Select the trigger event:

HubSpot users: Select New Form Submission as your trigger event. Choose the specific form you want to monitor (e.g., your demo request form). For a full HubSpot-specific walkthrough, see How to Automate Meeting Scheduling from HubSpot Form Submissions.

Salesforce users: Select New Record as your trigger event, filtered to leads or contacts created from your web form. For the Salesforce-specific guide, see Salesforce Lead Follow-Up Automation.

Typeform, Webflow, Gravity Forms, or other tools: Select New Entry or New Response as the trigger event, then choose the specific form.

Step 3: Test the trigger to pull in a sample form submission. Verify the email field and any context fields (company name, message, etc.) come through correctly.

If this is your first time connecting SkipUp to Zapier, see our Zapier + SkipUp setup guide for authentication and connection basics. This playbook assumes you have already connected the apps.

How long should you wait before triggering recovery?

This is the most important configuration decision in your workflow. The delay window determines how long you give a prospect to book on their own before the recovery triggers.

Too short and you will fire recovery emails at people who are still filling out the scheduling widget. Too long and the prospect’s interest has faded — the prospect has moved on to a competitor or shifted attention elsewhere.

Recommended timing windows

The recommended delay before triggering lead recovery depends on the form type:

Form Type	Recommended Delay	Why
Demo request	15-30 minutes	High-intent lead, short decision window. They either book immediately or they do not.
Contact / inquiry form	30-60 minutes	Lower urgency — prospect may be researching multiple vendors.
Pricing page form	10-15 minutes	Highest urgency — pricing interest signals active evaluation.
Event/webinar registration	45-60 minutes	Often submitted in batches; give time for organic booking.

How to set the delay in Zapier

After your trigger step, add a Delay by Zapier action:

1. Search for Delay by Zapier in the action step
2. Select Delay For as the event
3. Set the delay value (e.g., 30) and unit (minutes)
4. This creates a pause — the Zap will wait the specified time before proceeding to the filter step

Testing your timing

Once your workflow is live, run it for two weeks and then compare recovery rates across timing windows. If you want to A/B test, create two identical Zaps with different delays (e.g., 15 min vs. 45 min) each handling 50% of submissions. Compare which delay recovers more meetings.

How do you filter out leads who already booked?

After the delay, you need to check whether the prospect booked a meeting during the wait period. Without this filter, you will send recovery emails to people who already have a meeting on the calendar — this will undermine trust with your highest-intent leads.

The filter check

The question the filter answers: “Has a meeting been booked for this email address since the form was submitted?”

Choose the filter method that matches your tech stack:

Option A: Check your CRM for a meeting record Add a Search step in Zapier to look up the contact in HubSpot or Salesforce. Check for a meeting, event, or activity record created after the form submission timestamp. If one exists, stop the Zap.

Option B: Check your scheduling tool If you use Calendly or HubSpot Meetings, add a lookup step to search for a booking with the prospect’s email. If a booking exists within the delay window, stop.

Option C: Check SkipUp for an existing meeting request Use SkipUp’s Find Meeting Requests search in Zapier, filtering by participant email (or a “Webhooks by Zapier” GET request to /api/v1/meeting_requests?participant_email={email}, which requires an API key with meeting_requests.read scope). This catches cases where another workflow already triggered SkipUp.

After the lookup, add a Filter by Zapier step:

• Only continue if the meeting/booking record does not exist
• This ensures the recovery action only fires for leads who genuinely did not book

Handling edge cases

Duplicate form submissions: The same person submits the form twice. Add a filter to check for existing SkipUp meeting requests with that email. The SkipUp Zapier integration automatically includes an idempotency key to prevent duplicates on retries. If using the API directly, include an Idempotency-Key header. Filtering upstream avoids unnecessary triggers entirely.

Mid-delay bookings: The prospect books 10 minutes into a 30-minute delay. Your filter step catches this — by the time the delay expires and the filter runs, the booking will exist and the Zap will stop.

Internal or test submissions: Use a Zapier filter to exclude email domains you do not want to trigger recovery for (e.g., your own company domain, test email addresses).

How do you connect SkipUp to recover the lead?

After the filter confirms no meeting was booked, the next step creates a SkipUp meeting request. When your automation triggers this step, SkipUp takes over the scheduling conversation via email — reaching out to the prospect, negotiating a time, and booking the meeting on the calendar.

Configure the SkipUp action

Add SkipUp as an action step with the Schedule Meeting event. Map these fields:

Field	Source	Example
Organizer Email	Static value or workspace member dropdown	[email protected]
Participant Email(s)	Form submission email field	[email protected]
Meeting Title	Static text + form data	”Demo Call with {{Company Name}}“
Duration (minutes)	Static value	30 (defaults to 45 if omitted)
Meeting Purpose	Brief description of meeting type	”Demo request follow-up”
Additional Context for the AI	Form submission fields	”{{Name}} from {{Company}} submitted a demo request. Their message: {{Message}}“
Scheduling Window Start	Leave blank or set to today	(defaults to today if omitted)
Scheduling Window End	Leave blank or set a date	(defaults to 2 weeks from today if omitted)

Best practice for the context fields: Include as much form data as possible in Additional Context for the AI. SkipUp uses this context to write a more relevant scheduling email. A meeting request with context like “Jane from Acme Corp is interested in enterprise pricing” produces a much better outreach than one with no context.

Setting up recovery for your executive’s calendar? The setup is identical. Map the calendar host to your executive’s SkipUp account, and add an optional Slack or email notification step so you are informed when new demos get booked. You stay in control of calendar preferences — SkipUp handles the back-and-forth with the prospect.

Optional: Add a team notification

Add a final Slack or Email action to notify the sales team that a recovery was triggered:

• Post to your #new-demos or #lead-recovery Slack channel
• Include the prospect’s name, company, and form details
• This keeps your team informed without requiring any manual action

How do you test and troubleshoot your recovery workflow?

Before turning on your Zap for production traffic, run through this testing checklist:

• Submit a test form entry with a non-company email
• Verify the delay fires for the correct duration
• Verify the filter correctly stops the Zap when a meeting IS already booked
• Verify the filter lets the Zap continue when NO meeting exists
• Verify the SkipUp meeting request is created with the correct participant email, meeting title, and context
• Verify the prospect receives a scheduling email from SkipUp
• Verify the team notification fires (if configured)

Common issues and fixes

“Recovery fires but no scheduling email goes out” Check your SkipUp API key permissions and verify the meeting host’s calendar is connected. Also confirm the participant email is a valid, non-internal address.

“Recovery fires for prospects who already booked” Your filter logic is misconfigured. Double-check the lookup step — make sure it is searching for the right record type (meeting, event, or booking) and comparing the correct date range.

“The delay seems too short or too long” Zapier’s delay is approximate — it can vary by a few minutes. This is normal. If precision matters, consider the API path for exact timing control.

“Duplicate recovery emails going out” Add a deduplication check before the SkipUp action. Search for an existing SkipUp meeting request with the same participant email. If one exists, stop the Zap.

Once your workflow is live, monitor your recovery rate for at least two weeks before making optimization changes. For benchmarks on what “good” looks like, see Form Submission to Meeting Booking: The Drop-Off Rates Every Sales Team Should Know.

What should you do after your recovery workflow is live?

Your recovery workflow is live. Once you have baseline data, build on your results:

1. Monitor for two weeks before changing timing or filter settings. Let the data accumulate.
2. Check your recovery rate against industry benchmarks — see the benchmarks article for reference.
3. Understand the speed-to-lead context — faster outreach means higher recovery. Learn why automated scheduling is your best response-time weapon.
4. Scale to more forms once your first workflow proves out. Start with your highest-volume form, then replicate for others.
5. Return to the complete guide for the strategic overview of the full detection-to-recovery pipeline: The Complete Guide to Abandoned Form Lead Recovery.

Start with one form, one trigger, one recovery workflow. Measure the results. Then scale. Get started with SkipUp to automate your first recovery workflow today.