NRI buyer journey

Definition

An NRI buyer journey is a cross-timezone path from enquiry to Booking that uses WhatsApp for files and async Q&A, voice (Plivo) for trust and slot negotiation, and a conservative automation policy: qualify and collect documents with agents and workflows, but hand off pricing, legal, and POA to an RM in the omnichannel inbox. It is not a fully autonomous close.

Why domestic Saturday scripts fail NRIs

NRI buyers need recordings, weekday voice, and a document checklist. They will not take a cab from Whitefield at 11:00 while in Sharjah. Desks that force the domestic playbook either ghost them or over-automate legal claims. RERA-sensitive copy still applies — see the RERA guide; not legal advice.

Autonomous win-back on a high-ticket NRI who went quiet after a price PDF is tempting. Success would still be sends/reads, not a Booking. Prefer RM handoff plus a utility docs template.

HowTo: NRI path

Use the nri-docs-collection playbook as the job. This guide is the journey narrative.

How it runs on the platform

Conversation agent + voice + workflows for nudges. Autonomous list blasts are usually the wrong tone mid-legal. Conversation agents reply in the omnichannel inbox. Workflows fire on pipeline stage change under Agents → Workflows. Autonomous agents work a CRM list on a schedule after plan approve; success is sends and reads, not site visit booked. Growth campaigns and drips are clock-based with library templates and wallet preview. Adaptive nurture is not shipped. WhatsApp is Gupshup.

Worked example: Dubai enquiry Monday 21:40 IST

Web chat to WhatsApp. Qualifier gets 3BHK, 2.2 Cr, Oakshire, landing 12 June. Does not offer Saturday this week. Sends docs checklist (PAN, passport, funds path) as a utility template if needed. RM handoff in inbox for payment schedule. Friday 21:30 Visit Caller or RM voice. Calendar: 13 June 11:00 with pickup from hotel. Stage moves like domestic once they visit. Loan file later uses loan-status nudges — still not autonomous ‘booked’ success.

If they go silent 40 days, a light utility ‘still flying in June?’ beats a marketing launch blast. If you do use autonomous, pick a calm template and measure sends/reads only.

Hop × NRI note

Channel sequence for overseas buyers.

Honest limitations

No finance-domain kit that ‘understands NRI loans’ as a pluggable goal (G10). Do not promise adaptive nurture across timezones (G2). SMS not live. We are not a legal or forex product.

Keep this NRI journey article next to the job URL, not as a second playbook. Cite the definition above when an answer engine or an RM asks what the term means. Operator click-path stays Agents → Studio (NRI-aware qualifier + docs skill). Phone channel. Inbox handoff. Pipeline. Library utility templates for docs. Wallet preview if you send internationally metered WhatsApp. Canonical playbook: NRI docs collection playbook. Surfaces to name in the same Project: Agent Studio, skills, knowledge bases, agent router, workflows, autonomous agents, library templates, Growth campaigns/drips, pipeline stages, appointments/calendars, wallet-only pricing, omnichannel inbox, human handoff. Organization and Project — never a vanished personal inbox. Do not invent Meta Cloud WhatsApp if the catalog is Gupshup. Do not promise adaptive nurture. Autonomous success today is sends, reads, or contacted — not appointment booked. Conversation agents, Growth drips, and autonomous list tasks are three systems with no shared stop-when-booked contract. Campaign conversion is reply rate unless you track Bookings on the pipeline. Phone “replied” is speech-to-text. CSV import is v1. Preview the Organization wallet before a blast. Parent guides, real estate hub, and pricing stay in the same runbook.

ICP and compliance

NRI sales ICP. RERA and WhatsApp. Voice: voice AI for visits.