Pickup pin and cab time — or the Saturday slot is theatre

Definition

Cab pickup confirmation is the job of capturing a pickup point and window on the Booking, confirming it on WhatsApp, and repeating it on the Visit Caller hop so hot buyers can actually use the Saturday slot.

A slot without a pin is a no-show with a van in the wrong place

Brokers say “we will pick you up.” Nobody writes the gate. Insights can recommend arranging cab pickup for top buyers — you still type the note and dispatch the actual cab outside CoPulse. No Uber API. No SMS OTP to drivers.

Omnichannel sequence

After slot exists. WhatsApp collects pin. Voice repeats. Email unused.

How it runs in CoPulse

Conversation agent collects. Workflow does not dispatch cars. Voice greeting trained with pickup fields. Autonomous cannot book cabs. 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

Custom property, Visit Caller prompt, WhatsApp session or template.

Metro gate 2, van not at gate 1

Buyer texts gate 2. Booking note updates. Visit Caller says gate 2. Show-up happens. Click-path: inbox, Booking, phone script. Ops still booked the actual cab in their vendor chat.

No-show-recovery if they still miss. Illustrative visited 12% improves when pickup exists — still an estimate. Pricing: extra WhatsApp confirm on the wallet; the cab vendor is separate.

Operators assemble this job on the Project. Click-path remains Customers properties pickup_text → Studio scheduler + Visit Caller training → Workflows optional prompt on enter → wallet. Keep the quotable definition in the brief for the team: Cab pickup confirmation is the job of capturing a pickup point and window on the Booking, confirming it on WhatsApp, and repeating it on the Visit Caller hop so hot buyers can actually use the Saturday slot. 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, Developers, 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 Cab pickup 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)

Logistics hops. There is no nested playbook-by-channel path.

Illustrative funnel (library template estimates)

Pickup quality is why visited lags booked in the template. 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.