CRM · docs read 9 November 2026
Demo no-show, speed-to-lead and form-to-CRM checks for Close
Close takes demo requests through Close Forms (or Calendly), books one-to-one meetings with Close Scheduling, and records held vs no-show as a Playbook meeting Outcome. Below: what Close's own docs say about speed to lead, routing and owner assignment, confirmations and reminders, the ways a demo funnel in Close usually leaks, and which free check to run on your own numbers.
Checks to run with your Close data
Demo Request Response Check
How long does a contractor who asks for a demo wait to hear back?
What to bring from Close
- Close's own guide says median time from form submission to first call is "Not native. Use Explorer or CSV export."[7]
- Support Tools can export Leads, Contacts, Opportunities or Activities from any Smart View to CSV using only the columns visible in that view (not legacy text-based Smart Views).[6]
Demo No-Show Check
Why do owners book a demo and then not turn up?
What to bring from Close
- With Close Scheduling the documented confirmation is the calendar invite the contact receives (if they have an email address); no reminder emails are described.[1]
- Activity Overview and Activity Comparison reports show a count, total duration and average duration per outcome.[3]
Held-Demo Leak Finder
You booked more demos. Why didn't more owners show up and buy?
What to bring from Close
- Activity Overview and Activity Comparison reports show a count, total duration and average duration per outcome.[3]
- Support Tools' Export Meetings downloads meeting activity records to a CSV, filterable by Smart View and date range.[6]
Lead Form to CRM Match
Did every demo request from your site actually reach your CRM?
What to bring from Close
- Build a Smart View of new inbound leads with email and created date visible, export it from Support Tools, and match against the form CSV by email + date.[6][7]
Also free: Trial Stall Check. Nothing you enter in a tool leaves your browser.
Speed to lead in Close
- Close Forms (Settings > Connect > Forms) create Lead and Contact records with no integration layer; enabling "Email notifications on submission" alerts the team in real time.[7]
- Close recommends using Groups to define the rep pool that handles a given lead source.[7]
- When a meeting is booked with Close Scheduling, the Close user is not sent an email notification.[1]
Routing and owner assignment in Close
- Close Scheduling does not support round-robin scheduling or pooled calendars; meetings are booked with a specific Close user, one user and one contact per meeting.[1]
- With the Calendly integration, the Calendly "Event Host" can be mapped to a Close User field (matched by email), but it is not available on Calendly Event Types with multiple hosts (Collective and Multi-Pool).[2]
Confirmations and reminders in Close
- With Close Scheduling the documented confirmation is the calendar invite the contact receives (if they have an email address); no reminder emails are described.[1]
Where a no-show is recorded in Close
- Outcomes represent the result of a connected call or a completed meeting; meeting outcomes can be set before, during or after the meeting, and the example dropdown shows No Show, Follow Up Needed and Demo Completed.[3]
- Outcomes come from the Playbook applied to the meeting; if no Playbook is applied, no Outcomes are available. Call and Meeting Outcomes are available on Growth and Scale plans.[3]
- Meeting status in Close follows the calendar: Upcoming, Completed, Declined and Canceled.[1]
Webhooks and triggers in Close
- Each organization can have up to 40 webhook subscriptions; failed deliveries are retried with exponential backoff for up to 72 hours, then dropped, and events can arrive out of order.[5]
- A subscription pauses (and its queue clears) when its backlog reaches 100,000 events, or after 3 days of failed deliveries, and must be reactivated through the API.[5]
| Event or trigger | When it fires |
|---|---|
| object_type=lead, action=created | New lead (e.g. a form submission or booking) |
| object_type=activity.form_submission, action=created | A form submission was recorded |
| object_type=activity.meeting, action=scheduled | Future meeting created or rescheduled, or moved to status upcoming |
| object_type=activity.meeting, action=completed | Meeting moved to status completed |
| object_type=activity.meeting, action=canceled | Meeting moved to status canceled |
| object_type=activity.meeting, action=updated | Any meeting update |
| object_type=activity.custom_activity, action=created | A custom activity (e.g. a demo-held log) was created |
| object_type=activity.opportunity_status_change, action=created | Opportunity moved to a new status |
Getting form requests and CRM records out in Close
- Close Forms capture UTM and custom URL parameters with every submission; forms not hosted by Close send submissions via webhook or Zapier.[7]
- With Calendly connected and "Create Contacts" enabled on an Event Type, Close creates a new Contact when a meeting is booked; if the invitee's email already exists no Contact is created; Submission Date/Time and UTM fields can be mapped. Not available on Calendly's Free plan.[2]
- Export Lead Status Changes downloads a history of lead status changes to CSV, filterable by Smart View, date range and lead custom fields.[6]
How a demo funnel in Close usually leaks
No outcomes without a Playbook
Close only offers meeting Outcomes (like No Show) when a Playbook is applied, and only on Growth and Scale plans, so on other setups there is no No Show outcome to pick.[3]
Fix: Attach a demo Playbook with a No Show outcome to every demo meeting type.
No round robin for demos
Close Scheduling books with one named user and has no round-robin or pooled calendar, so inbound demo requests don't spread across reps by themselves.[1][2]
Fix: Assign the lead to a rep (or use a round-robin Calendly event connected to Close) before sending a booking link.
Reps aren't emailed on new bookings
Close Scheduling does not send the Close user an email notification when a meeting is booked; they only see the calendar event.[1][7][4]
Fix: Turn on form "Email notifications on submission" and watch the calendar, or subscribe to activity.meeting.scheduled.
Contacts without email mis-sync
If the contact has no email, the booked meeting may not sync back to the correct Lead, so the demo is missing from the lead's history.[1]
Fix: Require email on demo-request forms before booking.
Calendly round robin needs every host connected
For round-robin group events, every Calendly account in the group must be connected to Close for Contacts to be created.[2]
Fix: Connect each rep's Calendly account to Close before enabling the round-robin event.
Sources
Close's own documentation, read on 9 November 2026. Products change menus, plans and limits; if your account shows something different, your account wins.
Rather have someone look at your Close setup?
Tell me how a demo with a contractor owner gets booked at your company today, and within 48 hours I'll send a free written review: what I'd fix first in how requests are answered, reminded and followed up.
Not affiliated with Close; product names belong to their owners. This is a sales-process checklist built from public docs: not a security audit, legal, compliance or investment advice.