After keys: NPS and a referral ask — not another qualifier

Definition

Post-handover referral is the job of sending an NPS or satisfaction prompt after possession, then a referral ask, and handing any new numbers to the referral-intake playbook on a new Booking — without putting booked customers back through sales qualification.

Launch lists still include people who already have keys

Growth audiences rot. Exclude construction-complete from teasers. This job is a small drip. Autonomous NPS lists count reads, not scores. No SMS. Router must not use RE Qualifier.

Omnichannel sequence

WhatsApp/email NPS, optional voice for detractors, WhatsApp ask, then intake on a new contact.

How it runs in CoPulse

Growth drip after handover. Conversation agent for the ask — not the sales qualifier. Workflows on handover_complete. Autonomous optional with honest metrics. Autonomous agents may follow a launch list on WhatsApp, email, or phone after plan approve. They do not create templates, do not adapt from prior outcomes, and do not stop when a site visit is booked. Campaign reply rate is not an Interested CRM state. 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

Handover flag, after-sales agent, templates, exclude from launch.

Keys Friday, NPS Saturday, cousin number Sunday

NPS 5. Ask. Cousin number. referral-intake creates New enquiry. Original customer stays off launch lists. Click-path: property, drip, inbox, new Booking.

No library conversion % for NPS. Do not reuse launch 2% closed as referral rate. Pricing: two templates plus cousin qualifier on the wallet.

Operators assemble this job on the Project. Click-path remains Property handover_complete → Workflows → Library NPS/ask → Studio after-sales agent → Router → Growth exclude from launch → wallet. Keep the quotable definition in the brief for the team: Post-handover referral is the job of sending an NPS or satisfaction prompt after possession, then a referral ask, and handing any new numbers to the referral-intake playbook on a new Booking — without putting booked customers back through sales qualification. Autonomous agents may follow a launch list on WhatsApp, email, or phone after plan approve. They do not create templates, do not adapt from prior outcomes, and do not stop when a site visit is booked. Campaign reply rate is not an Interested CRM state. While you implement, keep the parent playbooks directory, Construction / handover, 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-handover referral 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)

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