Stage · site visit booked

Site visit booked is capacity, pickup, and T-24h — or it melts

Site visit booked is where calendar slots, pickup details, and T-24h reminders start, or Saturday inventory saturates. Insights for real estate calls this out when qualified buyers do not convert to visits: missing pickup and too many Saturday-only offers. This stage is not the site-visit booking playbook. The playbook is the job (WhatsApp slot + Visit Caller). This column is the Booking after the calendar event exists.

  • Calendar event exists
  • Drip + Visit Caller
  • No autonomous stop

A booked slot with no reminder is a no-show with a van waiting

Brokers treat the WhatsApp “ok Saturday” as booked. CoPulse should have an appointment on the contact. Without a library utility template, the T-24h WhatsApp fails outside the 24-hour session. Visit Caller in the Site-visit booking blitz library template is the voice hop: confirm tomorrow and share pickup. Autonomous tasks that “nurture until visit” still only count sends and reads — they will not flip this column or stop at booked. SMS reminders are not live.

Hold the slot through show-up

Phone schedules the visit in the omni playbook; WhatsApp then carries post-visit. This stage is the middle.

  1. Prove the calendar Appointment skill / public calendar. Pickup on the Booking.
  2. T-24h WhatsApp Growth drip or workflow-started campaign with an approved template if the session died.
  3. Voice confirm Visit Caller. Phone replied means they spoke, not that they will arrive.
  4. Exit Visited if they came. Same-day rebook offer if they no-showed — still not a playbook×channel URL.

How it runs in CoPulse

Drips and voice are the workhorses. Conversation agent still answers “can I come at 12 instead?” Workflow on enter attaches the reminder. Do not assign an autonomous list blast to people already holding a Saturday slot unless you like double-booking.

Appointments / calendars

The source of truth for the slot. Pipeline stage should match.

Growth drips

T-24h template. Wallet preview. Not smart send-time.

Voice AI

Training greeting in Agent Studio. Visit Caller role from the library playbook.

Workflows

On enter: start drip + enqueue voice. On no-show custom property: reoffer Sunday.

Operator setup

Plivo for voice, Gupshup for WhatsApp, calendars on the Project.

Setup → Channels (WhatsApp, Phone) → Library (reminder template) → Agents → Studio (Visit Caller greeting) → Workflows on enter → Growth drip → wallet.

Saturday 11 with a metro pickup

Card enters Site visit booked. Workflow starts a utility template reminder for Friday evening and a Visit Caller task for Friday afternoon. Operator trained the greeting in Agent Studio (“CoPulse calling about your Prestige Lakeside visit”). Cab note sits on the Booking so the caller is not guessing. Buyer confirms on the call. Saturday they show; ops moves to Visited. If Insights still shows visit conversion dropping, add Sunday 10–12 on the calendar — that is an operator action, matching the dashboard’s suggested fix label, not an autonomous stop rule.

Click-path: Customers → Booking → appointments pane; Agents → Workflows; Growth → drip schedule; inbox if they WhatsApp a reschedule. Pricing: template send and voice minutes on the Organization wallet.

Booked slot operations

Exit is show / no-show, not “reminder sent.”

Stage Automation Human Channel hops Exit criteria
Site visit booked T-24h drip, Visit Caller Capacity, cabs WhatsApp + voice Arrived or no-show path
Qualified Slot offer Inventory WhatsApp Calendar hold
Visited EMI / RM intro Tour notes WhatsApp Next intent
Growth visits bar Demo funnel None Campaign Not this card

Jobs that create and protect this column

The playbook is omnichannel. This page does not fork by WhatsApp vs phone.

Frequently asked questions

Reminders, voice, and what autonomous cannot do.

Will autonomous tasks stop when the visit is booked?

No. Success specs are sends, reads, contacted, or text match — not appointments.

24-hour WhatsApp window?

If it closed, the reminder must be an approved library template. Planner does not auto-provision the pair today.

Phone replied = they will show?

Replied means STT heard speech after the template. Confirm the intent in the transcript or inbox.

Can Insights add Sunday slots?

It can recommend opening Sunday 10–12. You add the windows on the calendar.

SMS the morning of?

Coming soon. Use WhatsApp or voice.

Playbook vs this URL?

One job URL under playbooks. This is only the CRM column.

Protect Saturday like inventory

Attach T-24h plus Visit Caller on stage enter, and treat pickup notes as required fields — not optional chatter.

Get started free