Renewal is a stage and a cadence — not a sales Closed column

Definition

Lease renewal is the job of reminding tenants on WhatsApp and email at operator-chosen offsets before lease_end, collecting intent in the inbox, and handing rent changes to a human — on a renewal pipeline stage, not developer Booked.

Spreadsheets of end-dates that nobody messages

PMs notice expiry when the tenant already left. Store lease_end. Drip. Router to human on price. No SMS. No invented accounting integration.

Omnichannel sequence

Email + WhatsApp reminders, inbox negotiation, optional voice for important units.

How it runs in CoPulse

Growth drips + conversation + workflows on property dates if you configured them. Autonomous CRM query optional with honest metrics. Autonomous agents may send a list-based win-back after you approve the plan and pick an existing library template. Success today is sends, reads, or contacted — not visit booked or token paid. Move the Booking with a workflow or by hand. 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, drip, templates, SES, router.

30 June end, 30-day WhatsApp, human on 5% ask

Drip fires. Tenant wants a cut. PM in inbox. Letter on SES. Click-path: property, Growth, inbox. Autonomous report would have shown reads only.

rental-viewing is for new tenants. maintenance-tickets is repairs. Pricing: reminder sends on the wallet. Lists: campaigns prefer static lists — refresh the expiry cohort.

Operators assemble this job on the Project. Click-path remains Customers properties lease_end → Library renewal templates → Growth drip → Studio → Router → wallet. Keep the quotable definition in the brief for the team: Lease renewal is the job of reminding tenants on WhatsApp and email at operator-chosen offsets before lease_end, collecting intent in the inbox, and handing rent changes to a human — on a renewal pipeline stage, not developer Booked. Autonomous agents may send a list-based win-back after you approve the plan and pick an existing library template. Success today is sends, reads, or contacted — not visit booked or token paid. Move the Booking with a workflow or by hand. While you implement, keep the parent playbooks directory, Pipeline hub, Email 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 Lease renewal 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)

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