Appointments / calendars
The source of truth for the slot. Pipeline stage should match.
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.
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.
Phone schedules the visit in the omni playbook; WhatsApp then carries post-visit. This stage is the middle.
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.
The source of truth for the slot. Pipeline stage should match.
T-24h template. Wallet preview. Not smart send-time.
Training greeting in Agent Studio. Visit Caller role from the library playbook.
On enter: start drip + enqueue voice. On no-show custom property: reoffer Sunday.
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.
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.
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 | Calendar hold | |
| Visited | EMI / RM intro | Tour notes | Next intent | |
| Growth visits bar | Demo funnel | None | Campaign | Not this card |
The playbook is omnichannel. This page does not fork by WhatsApp vs phone.
Reminders, voice, and what autonomous cannot do.
No. Success specs are sends, reads, contacted, or text match — not appointments.
If it closed, the reminder must be an approved library template. Planner does not auto-provision the pair today.
Replied means STT heard speech after the template. Confirm the intent in the transcript or inbox.
It can recommend opening Sunday 10–12. You add the windows on the calendar.
Coming soon. Use WhatsApp or voice.
One job URL under playbooks. This is only the CRM column.
Parent hub, sibling stages, CRM product, and jobs that move this column.
Buyers & Tenants, Bookings, channels, and playbooks.
Back to hub →Gate before the slot.
Open →The 48-hour clock starts after they tour.
Open →Appointments on the contact, stage-enter automation.
Product CRM →Reminder templates and Visit Caller minutes debit the wallet.
See pricing →Attach T-24h plus Visit Caller on stage enter, and treat pickup notes as required fields — not optional chatter.
Get started free