Conversation agent
Studio persona for leasing. Appointment skill for viewings. Handoff to a supervisor for disputes.
Viewings, renewals, and tickets — not a sales clone
Leasing teams treat viewing, renewal, and maintenance as pipeline stages, not a sales booking funnel copied from developers. CoPulse still says Buyers & Tenants, but your Project pipeline should read enquiry, viewing, application, active lease, renewal due, and maintenance — Bookings are viewings and renewals, not tokens.
- Viewing slots
- Renewal reminders
- Maintenance in inbox
A developer funnel will lie to tenants
If you import Enquiry → Qualified → Site visit → Booked, renewals look like dead deals and a leaking tap looks like a cold lead. Property managers need different stage labels under Setup → Customers → Pipeline. The conversation agent still lives in Agent Studio, but skills skew to appointments (viewings), forms (applications), and inbox tickets for maintenance. Knowledge bases are house rules and inventory, not launch brochures.
Omnichannel journey
Web listing or WhatsApp in; viewing on chat plus voice confirm; email for agreements; WhatsApp again for renewal and tickets — one Tenant timeline.
- Web / listing portals Enquiry creates a contact. Do not dump them into a sales launch audience.
- WhatsApp Offer viewing slots. Later: renewal window and maintenance intake on the same number.
- Phone Confirm the viewing. Training greeting can be a PM line, not a sales pitch.
- Email Draft agreements and KYC. Construction-style marketing blasts do not belong here.
How it runs in CoPulse
Conversation agent for viewing and tickets. Drips for renewal windows. Workflows on stage enter (viewing done → application form). Autonomous lists are a poor fit until you have a defined send/read campaign; they will not mark a lease signed.
Inbox tickets
Maintenance stays on the omnichannel thread with a deal or custom property for unit ID — not a side WhatsApp with the plumber only.
Drips
Renewal at 90/60/30 days via library templates. After 24h, templates only.
Workflows
On Renewal due, start the drip. On Maintenance, notify the vendor queue. Custom properties on the account hold unit and lease end.
Operator setup
Separate Project from the sales tower if the same Organization builds and leases.
Setup → Channels → Agents → Studio (leasing persona + appointment skill) → Pipeline stages named for PM → Growth drips for renewals → wallet for WhatsApp/email.
One Tenant, two jobs
Priya books a Sunday viewing on WhatsApp. The appointment skill writes Viewing on the pipeline you named — not Site visit booked copied from a developer template. After she signs, the same number is used for a geyser ticket: the agent files a custom property for unit 4B and hands off to a supervisor. Ninety days before lease end, a Growth drip sends approved templates; after the 24-hour window it cannot free-text. You do not run a launch teaser at her. You do not wait for an autonomous task to decide the lease is signed. That honesty is what keeps PM operations from looking like a failed sales CRM.
If the Organization also sells primary inventory, use a second Project so sales Bookings never mix with renewal drips. Knowledge should be house rules and unit inventory. The omnichannel inbox is where tenants already are; forcing email-only tickets recreates the call-center voicemail pile. Wallet usage is WhatsApp and email, not a seat per building manager.
PM channel sequence
Sales hops (token, disbursal) are out of scope on this page.
| Hop | Channel | What happens | Owner |
|---|---|---|---|
| 1 | Web / WhatsApp | Rental enquiry | Capture |
| 2 | Viewing slot | Agent | |
| 3 | Phone | Confirm viewing | Voice |
| 4 | Agreement / KYC | Human | |
| 5 | Renewal + tickets | Drip + inbox |
Playbooks for this team
Jobs are omnichannel. Each link is one URL, not a WhatsApp-only clone.
Frequently asked questions
Leasing pipelines are not sales pipelines.
Can I reuse the developer playbook?
Reuse channels and Agent Studio, not the stage names. Copying Booked/Loan will hide renewals.
Who owns maintenance?
A supervisor via handoff. The agent logs the ticket and unit custom property.
Autonomous renewals until signed?
Autonomous success is sends/reads, not a signed lease. Use drips plus a human for the close.
Wallet?
Usage for WhatsApp and email. Pricing.
Knowledge?
House rules, inventory, pet policy — so the agent does not promise a builder amenity.
SMS?
Coming soon. WhatsApp templates for reminders.
Related
Parent hub, sibling teams, and product surfaces this ICP actually uses.
Name stages like a PM
Create the Project, relabel the pipeline, and book the next viewing from WhatsApp.
Get started free