48 hours after the tour: EMI, inventory, RM — or the deal dies

Definition

Post-visit follow-up is the job of logging the tour, continuing the same omnichannel thread with inventory and EMI context, introducing the RM, and running a short +24h drip so Visited Bookings do not go silent.

The van leaves and the personal WhatsApp goes quiet

Brokers promise EMI from their phone. Monday is too late. Inbox should already have the tour. Do not send launch teasers. Do not claim autonomous stops at token. Email carries the calculator PDF if WhatsApp is a poor fit.

Omnichannel sequence

OmniView last hop is WhatsApp post-visit. Voice optional. Email for EMI sheets.

How it runs in CoPulse

Conversation agent + drip + workflow on Visited enter. Autonomous win-back is a later job (60 days), not tomorrow morning. 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

Knowledge EMI sheet, RM roster, drip, templates for closed window.

They asked about loans on the lawn at 1 p.m.

Visited at 1:10. Same-day EMI in-session. +24h calculator. Ananya in inbox. Click-path: kanban, workflows, inbox. Token talk is the next playbook.

emi-loan-intro deepens the loan beat. Illustrative visited 12% of reached — post-visit quality is how you beat it. Pricing: follow-up WhatsApp/email on the wallet.

Operators assemble this job on the Project. Click-path remains Studio knowledge → Router → Workflows on Visited → Growth +24h → Library → wallet. Keep the quotable definition in the brief for the team: Post-visit follow-up is the job of logging the tour, continuing the same omnichannel thread with inventory and EMI context, introducing the RM, and running a short +24h drip so Visited Bookings do not go silent. 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, 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 Post-visit follow-up 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)

Post-visit hops. There is no nested playbook-by-channel path.

Illustrative funnel (library template estimates)

Visited 12% is the library’s last blitz bar before Closed. 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.