NRI KYC across time zones — email files, WhatsApp pings, voice last

Definition

NRI document collection is the job of requesting, tracking, and nudging KYC and overseas paperwork on email and WhatsApp, with voice in the buyer’s evening, using custom properties for missing items — not a single IST phone culture.

Calling Dubai at 10 a.m. IST is how files stall

Desks only call. NRI buyers live on WhatsApp/email. Store missing_docs. Drip. No bank LOS. No SMS. Autonomous doc chase counts sends, not “pack complete.”

Omnichannel sequence

WhatsApp ping, SES request, voice in their timezone, inbox exceptions.

How it runs in CoPulse

Drips + conversation + voice. Workflows on missing_docs. Autonomous optional with honest metrics. 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, NRI knowledge checklist.

Passport received, FATCA still missing, call at 8 p.m. Dubai

SES list. WhatsApp ack page 1. Voice only for FATCA. Inbox has the email attachments on the same contact. Click-path: properties, SES, phone. Not a 10 a.m. IST first hop.

loan-status-nudges if the bank file is the blocker. Illustrative funnels from sales blitz do not apply. Pricing: SES + WhatsApp + voice on the wallet.

Operators assemble this job on the Project. Click-path remains Customers properties missing_docs → Channels email + WhatsApp + phone → Library → Growth drip → Studio → wallet. Keep the quotable definition in the brief for the team: NRI document collection is the job of requesting, tracking, and nudging KYC and overseas paperwork on email and WhatsApp, with voice in the buyer’s evening, using custom properties for missing items — not a single IST phone culture. 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, Booked, Email overlay, NRI sales, 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 NRI docs collection 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)

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