Slots on WhatsApp, confirm on voice, one Booking stage

Definition

Site-visit booking is the omnichannel job that qualifies, offers calendar slots, stores pickup, sends T-24h WhatsApp reminders, confirms on a Visit Caller voice hop, and moves the Booking to Site visit booked — not three disconnected tools.

“Ok Saturday” on personal WhatsApp is not a calendar event

Brokers screenshot chats. Saturday saturates. Insights flags missing pickup. This job writes the appointment on the contact. Autonomous tasks will not stop when the visit is booked — they count sends and reads. SMS reminders are not live.

Omnichannel sequence

Web/portal/ads already captured. WhatsApp qualify + slot. Voice confirm. Email unused.

How it runs in CoPulse

Conversation + drip + workflow on stage enter. Visit Caller is voice AI. Autonomous is not the primary runtime. Do not use autonomous tasks as the inbound qualifier. Conversation agents, Growth drips, and autonomous list sends are three systems with no shared stop-when-booked contract. WhatsApp live catalog is Gupshup, not an invented Meta Cloud hop. Phone is Plivo; email is SES. Wallet-only pricing: preview the Organization wallet before a blast. Organization and Project — never a shared inbox that vanishes when a broker leaves.

Operator setup

Gupshup, Plivo, calendars, reminder template, three agent roles, wallet preview.

Prestige Lakeside Saturday 11 with metro pickup

Library campaign preview: “Hi {{name}}, thanks for Prestige Lakeside — 2BHK or 3BHK?” Qualifier writes fields. Scheduler books. Friday Visit Caller. Kanban shows Site visit booked. Click-path matches Setup → Channels, Agents → Studio / Workflows, Customers appointments.

Illustrative template funnel: Reached 100, Replied 62, Qualified 38, Visit booked 18, Visited 12. GrowthLoop demo separately shows 47 site visits booked on a launch broadcast — campaign analytics, not this kanban. Pricing: WhatsApp + voice on the Organization wallet.

Operators assemble this job on the Project. Click-path remains Setup → Channels WhatsApp + Phone → Library reminder → Studio (three agents) → Router → Pipeline → Workflows → Growth drip → wallet. Keep the quotable definition in the brief for the team: Site-visit booking is the omnichannel job that qualifies, offers calendar slots, stores pickup, sends T-24h WhatsApp reminders, confirms on a Visit Caller voice hop, and moves the Booking to Site visit booked — not three disconnected tools. Do not use autonomous tasks as the inbound qualifier. Conversation agents, Growth drips, and autonomous list sends are three systems with no shared stop-when-booked contract. While you implement, keep the parent playbooks directory, Site visit booked, Phone overlay, Brokers, Agent Studio, Growth campaigns, and wallet-only pricing in the same runbook. Do not invent Meta Cloud WhatsApp if the catalog is Gupshup. Do not promise adaptive nurture. Human handoff stays in the omnichannel inbox. Appointments and calendars are the visit truth when this job books time. Library templates are required outside the 24-hour WhatsApp window. Workflows fire on pipeline stage change only when you attach them under Agents → Workflows. The agent router keeps the wrong bot off this thread. Knowledge bases hold PDFs you uploaded. Preview the Organization wallet before a blast. Property managers should not paste sales token stages onto leasing jobs. The Site-visit booking playbook never forks into a WhatsApp-only or voice-only child URL. Funnel percentages on some leaves are library template estimates from Site-visit booking blitz, New project launch teaser, or Cold-buyer win-back — not an SLA and not Insights. If this job mentions money, the Organization wallet is the meter. If it mentions a Saturday slot, Visit Caller and T-24h templates are in-product; cab dispatch is not. That is the honest operating manual for this URL.

Channel sequence (one job, not extra URLs)

The canonical buyer-journey hops for visits. There is no nested playbook-by-channel path.

Illustrative funnel (library template estimates)

Copied from playbook-templates.ts re-lead-followup conversions. These percentages come from CoPulse library playbook templates (Site-visit booking blitz, New project launch teaser, or Cold-buyer win-back). They are not your project's Insights chart.