EMI in chat after intent — PDFs on email, not a list blast

Definition

EMI and loan intro is the job of sending an indicative calculator from knowledge on WhatsApp after the buyer shows loan intent, following with SES documents, and handing confusing numbers to a human — not blasting EMI to an unqualified list.

EMI PDFs to everyone trains buyers to ignore you

Affordable funnels spray calculators. This job waits for intent (Visited loan question or Qualified “need loan”). Insights +24h EMI is the post-visit variant. No bank LOS. No SMS. Wallet preview before a 2,000-person “EMI” campaign — that campaign is the wrong shape.

Omnichannel sequence

Intent on WhatsApp/voice. Calculator on WhatsApp. PDF on email. Voice if they panic.

How it runs in CoPulse

Conversation agent + email. Workflow on loan_interest. Autonomous EMI lists count sends, not sanction. loan-status-nudges is after Booked. 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 legal review. SES connected. Router. Wallet.

90L, 20 years, they asked on the lawn

Indicative WhatsApp. PDF email. Ananya takes over when they argue tenure. Click-path: knowledge, inbox, SES log. Not a Growth blast.

Affordable-housing volume: still per-intent, plus wallet preview if you ever segment. Illustrative visited 12% is not an EMI conversion. Pricing: WhatsApp + SES on the Organization wallet.

Operators assemble this job on the Project. Click-path remains Studio knowledge EMI → Channels email + WhatsApp → Router → Workflows on loan_interest → wallet. Keep the quotable definition in the brief for the team: EMI and loan intro is the job of sending an indicative calculator from knowledge on WhatsApp after the buyer shows loan intent, following with SES documents, and handing confusing numbers to a human — not blasting EMI to an unqualified list. 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, 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 EMI / loan intro 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)

Finance intro hops. There is no nested playbook-by-channel path.

Illustrative funnel (library template estimates)

EMI does not have its own library %; we show the parent blitz estimates. 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.