T-24h WhatsApp, T-2h if silent, voice if still dark

Definition

Visit reminder is the job of sending T-24h and optional T-2h WhatsApp utility templates for a held calendar slot, then placing a Visit Caller voice hop if there is no reply, so Saturday inventory is not a row of empty chairs.

Calendar holds without reminders become van-and-no-buyer mornings

Ops books 40 Saturdays and hopes. Insights talks Saturday saturation; no-shows are the other half. Drips are clock-based. Planner will not auto-build opener plus closed-window pairs. Phone replied still means speech, not “I will arrive.”

Omnichannel sequence

Slot already exists (WhatsApp). Reminder WhatsApp. Voice. Email rarely.

How it runs in CoPulse

Growth drip is the runtime. Workflow on stage enter attaches it. Conversation agent handles reschedules. Autonomous should not remind random lists without an appointment_query you set — and it still will not know they showed. 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

Approved templates, drip schedule, Plivo, calendars.

Friday 6 p.m. utility, Friday 4 p.m. caller for Saturday 11

Session died Thursday. Template still sends. No reply. Visit Caller connects. Buyer confirms cab. Click-path: Growth, Library, phone logs, Booking appointment pane.

No-show-recovery starts only if they miss. Illustrative blitz visit booked 18% / visited 12% implies reminder quality matters. Pricing: templates + minutes on the wallet.

Operators assemble this job on the Project. Click-path remains Library reminder templates → Growth drip T-24h / T-2h → Studio Visit Caller → Workflows → wallet. Keep the quotable definition in the brief for the team: Visit reminder is the job of sending T-24h and optional T-2h WhatsApp utility templates for a held calendar slot, then placing a Visit Caller voice hop if there is no reply, so Saturday inventory is not a row of empty chairs. 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, WhatsApp 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 Visit reminder 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)

Reminder hops only. There is no nested playbook-by-channel path.

Illustrative funnel (library template estimates)

Visited 12% vs visit booked 18% is the no-show gap the library implies. 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.