Referrals get a Booking, not a group chat

Definition

Referral intake is the job of creating a new Booking from a referred mobile number, linking it to the referrer’s contact with a custom property, sending a thank-you on WhatsApp or email, and running the same qualification as portal leads.

Referral WhatsApp groups hide SLA

RMs collect cousins in personal chats and never put them in CRM. CoPulse: new contact, New enquiry, source=referral. Thank-you is a library template (wallet). Qualification does not skip because they are “warm.” Autonomous should not blast the referrer’s whole phone book.

Omnichannel sequence

Source is a booked buyer (WhatsApp). New thread to the referred. Voice if a visit books. Email thank-you optional.

How it runs in CoPulse

Conversation agent on the new thread. Workflow on create: thank-you send + assign owner. Drip if they ghost. Not autonomous list-from-referrals unless you built a static 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. 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

Custom property for referrer. Thank-you template approved. Qualifier live.

Booked buyer forwards a cousin at 10 p.m.

RM pastes the number; or the agent extracts it and asks confirm before creating a contact (do not auto-spam). Thank-you fires. Cousin qualifies 2BHK 60L. Sunday slot. Click-path: inbox, Customers, workflow log, appointment.

Post-handover-referral is the NPS ask later. This page is intake. Illustrative blitz funnel once they qualify. Pricing: two WhatsApp threads debit the wallet.

Operators assemble this job on the Project. Click-path remains Setup → Customers properties → Library thank-you → Studio → Workflows on New enquiry source=referral → wallet. Keep the quotable definition in the brief for the team: Referral intake is the job of creating a new Booking from a referred mobile number, linking it to the referrer’s contact with a custom property, sending a thank-you on WhatsApp or email, and running the same qualification as portal leads. 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, New enquiry, 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 Referral intake 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)

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

Illustrative funnel (library template estimates)

Warmth may beat estimates; still labeled template 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.