Toured, no token: a second-pass job — not 60-day dormant yet

Definition

Visited-not-booked is the job of working Bookings that completed a site visit but did not token, using a second inventory angle, RM conversation, and optional new slot — distinct from same-week post-visit and from 60-day cold win-back.

One post-visit template then silence until a 60-day blast

The middle is empty. This job fills weeks 2–3. Do not mix launch teasers. Autonomous list of visited-not-tokened can send; it will not detect token. SMS no.

Omnichannel sequence

WhatsApp/RM inbox, maybe email payment plan, voice if rebook.

How it runs in CoPulse

Conversation + RM + optional drip. Autonomous optional with honest metrics. Not the primary 48h drip. Autonomous agents may send a list-based win-back after you approve the plan and pick an existing library template. Success today is sends, reads, or contacted — not visit booked or token paid. Move the Booking with a workflow or by hand. 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

Idle filter, RM, optional drip, wallet.

Tower B liked, no token day 12, Tower C 4L less

Ananya offers Tower C. Sunday 10. If they ghost to day 60, cold-buyer-winback. Click-path: kanban Visited, inbox, appointment.

Illustrative blitz visited 12% is the pool. This job tries to move them toward token without waiting for 60-day win-back 8% rebook estimates. Pricing: extra WhatsApp/voice on wallet.

Operators assemble this job on the Project. Click-path remains Customers filter Visited idle → Router RM → optional Growth → calendars → wallet. Keep the quotable definition in the brief for the team: Visited-not-booked is the job of working Bookings that completed a site visit but did not token, using a second inventory angle, RM conversation, and optional new slot — distinct from same-week post-visit and from 60-day cold win-back. Autonomous agents may send a list-based win-back after you approve the plan and pick an existing library template. Success today is sends, reads, or contacted — not visit booked or token paid. Move the Booking with a workflow or by hand. While you implement, keep the parent playbooks directory, Visited, WhatsApp 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 Visited not booked 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)

Second-pass hops. There is no nested playbook-by-channel path.

Illustrative funnel (library template estimates)

Pool is visited 12% of the blitz estimate. 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.