Rentals get a viewing job — not a copied sales blitz

Definition

Rental viewing is the job of capturing a leasing enquiry, qualifying beds, budget, and move-in date, booking a viewing on the appointment calendar, confirming on WhatsApp and optional voice, then handing application to humans — on a leasing pipeline, not developer Closed.

Copying New enquiry → Token breaks leasing ops

PMs inherit a sales board. Viewings look like site visits but evenings and lockboxes differ. No EMI drip. No construction mail. SMS not live. Autonomous list of expired listings is a different job (lease-renewal).

Omnichannel sequence

Web/portal/Meta listing → WhatsApp qualify → voice confirm viewing → email application pack.

How it runs in CoPulse

Same three systems, leasing labels. Conversation agent. Drip for viewing reminder. Workflows on viewing booked. Autonomous not required. 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

Leasing pipeline names. Knowledge rent PDF. Calendars. Channels.

Tuesday 6 p.m. lockbox viewing, not Saturday 11 sales van

WhatsApp qualify. Tuesday 6 booked. Reminder template. Optional voice. Application SES if they want it. Click-path: pipeline names, Studio, appointments. No EMI sheet.

Do not use Site-visit booking blitz percentages as leasing SLAs. Pricing: WhatsApp/voice/email on the Organization wallet. Human handoff for credit checks you do outside CoPulse.

Operators assemble this job on the Project. Click-path remains Setup → Customers pipeline (viewing/application) → Channels → Studio leasing qualifier → calendars → Library viewing reminder → wallet. Keep the quotable definition in the brief for the team: Rental viewing is the job of capturing a leasing enquiry, qualifying beds, budget, and move-in date, booking a viewing on the appointment calendar, confirming on WhatsApp and optional voice, then handing application to humans — on a leasing pipeline, not developer Closed. 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, Pipeline hub, WhatsApp overlay, Property managers, 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 Rental viewing 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)

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