Sanctioned is not disbursed — nudge the file on three hops

Definition

Loan status nudges is the job of clock-based WhatsApp, SES, and stuck-file voice follow-ups from Booked through disbursal, using custom properties you maintain, without claiming a bank LOS integration.

Closed columns hide salary-slip gaps

If Booked means sales is done, files rot. Dedicated stage plus this job. No SMS OTP from the bank in-product. No adaptive “until disbursed.”

Omnichannel sequence

Email docs, WhatsApp pings, voice when idle. Web unused.

How it runs in CoPulse

Drips + workflows + voice. Conversation answers which slip. Autonomous list of booked buyers will nag completed files unless you segment. Success sends/reads. 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

Properties, SES, templates, Plivo, exclude from launch lists.

Eleven days, no salary slips

Drip + weekly SES. Day 11 voice. Buyer emails slips. Inbox shows both. RM still phones the banker. Click-path: properties, workflows, Growth, phone.

NRI uses more email. Affordable volume: wallet preview. No library % for disbursal — we do not fake one. Pricing: nudges and calls on the wallet.

Operators assemble this job on the Project. Click-path remains Pipeline + properties → Workflows → Library + SES → Studio voice → Growth drip → wallet preview before volume nags. Keep the quotable definition in the brief for the team: Loan status nudges is the job of clock-based WhatsApp, SES, and stuck-file voice follow-ups from Booked through disbursal, using custom properties you maintain, without claiming a bank LOS integration. 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, Loan disbursal, Email overlay, Affordable housing, 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 Loan status nudges 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)

Long-close hops. There is no nested playbook-by-channel path.