Appointment Machine — Book Qualified Sales Calls

Inbound Demo Follow-Up Plan

Evidence boundary: The request for a demo, RevOps role, company size, supported CRM count, and setup range are supplied facts for this fictional case. No name, email, pricing, case study, ROI, calendar availability, or conversion baseline was provided. This is draft copy only; nothing is sent or booked.

1. Lead status and qualification

• Source / intent: Inbound demo request; explicit interest in a demo.
• Fit: Potentially relevant based on RevOps role and B2B context; product fit remains unverified.

Unknown: Current analytics workflow, CRM platform, reporting pain, stakeholders, timing, budget, security needs, and decision process.

Next status: NEEDS_DISCOVERY until a short conversation confirms use case and feasibility. Do not infer buying authority or urgency from job title/company size.

2. First response draft

Subject: Your workflow analytics demo

Thanks for requesting a demo. To make it useful, which CRM platform do you use, and what RevOps workflow or reporting question would you most like to improve? Our product connects with three CRM platforms and typical setup takes 2–4 weeks; I can confirm whether your setup fits once I know your environment. If helpful, reply with a couple of times that work, or use the booking link if one is available.

Before sending: insert the correct sender identity, verify which three integrations are supported and whether the lead's CRM is included, confirm the 2–4 week statement is current, and add a booking link only after it is authorized and available. Keep the demo request's consent and communication channel within applicable policy.

3. Follow-up and qualification

If there is no reply after the team's approved interval, send one brief reminder in the same permitted channel, then pause and respect any opt-out or suppression request. Do not use fabricated scarcity or an assumed deadline.

Ask only what helps determine a useful next step: CRM platform/version; workflow and reporting problem; current process; affected team; desired outcome; timing; security/data constraints; and who should join the demo. Defer budget questions until appropriate. Disqualify or nurture only using agreed criteria and recorded evidence.

4. Booking and show-rate support

Offer a short, clearly described demo with time zone and duration once calendar access and availability are confirmed. After booking, send the agreed confirmation and reminder, include a brief agenda, invite relevant stakeholders with the lead's agreement, and allow easy rescheduling. If a no-show occurs, send one courteous rescheduling note under the approved cadence, then pause.

5. Handoff notes

Known: inbound demo requested; RevOps role; 120-person B2B company; three CRM integrations; typical implementation 2–4 weeks.
Verify: CRM fit, use case, current workflow, success criteria, stakeholders, timing, security requirements, expected implementation path, and whether a qualified sales conversation is appropriate.
Do not claim: ROI, customer results, price, compatibility with an unverified CRM, or guaranteed implementation date.

6. Measurement plan

Establish a baseline before setting targets. Track request-to-first-response time, response rate, qualified-to-booked, booked-to-attended, attended-to-qualified, disqualification/nurture reasons, opt-outs/complaints, sales capacity, and lead-source cohort. Optimize qualified attended calls and fit, not send volume or bookings alone. Review message variants only with a permitted, sufficiently sized sample and stop tests that harm recipient experience or deliverability.

Next step: Verify integration fit and communication policy, then personalize using only confirmed lead context and authorized scheduling options.