CoPulse
Start free

Playbooks · real estate

One URL per job — omnichannel, not a page per channel

Each playbook is one omnichannel job, from portal capture to visit booking to launch, not a separate page per channel. CoPulse keeps Buyers & Tenants and Bookings on the Project. WhatsApp, voice, email, web, and Meta are hops inside the job. Library templates seed Site-visit booking blitz, New project launch teaser, and Cold-buyer win-back. You still connect Gupshup, Plivo, and SES, pick templates, and preview the Organization wallet.

  • Capture → convert → launch
  • Leasing jobs are separate
  • No nested WhatsApp URLs
Start free Buyer pipeline

A playbook is not a stage and not a channel

Pipeline pages explain columns (New enquiry, Qualified, Site visit booked). Channel overlays explain hops. Playbooks are the jobs that move cards across columns using several hops. Conversation agents in Agent Studio, Growth campaigns and drips, and autonomous list sends are three systems. They do not share a stop-when-site-visit-booked contract. Autonomous success today is sends, reads, or contacted. WhatsApp catalog is Gupshup. Adaptive nurture is not shipped. Projects configure their own stages under Setup → Customers → Pipeline.

How operators assemble a job

Every leaf repeats a concrete click-path. The pattern is the same; the templates and stages change.

  1. Connect channels Setup → Channels: WhatsApp (Gupshup), Phone (Plivo), Email (SES), Web, Meta. Skip SMS.
  2. Library templates Approve utility and marketing templates before closed-window WhatsApp. Planner will not auto-create them.
  3. Agent Studio RE Qualifier, Visit Scheduler, Visit Caller, Reply Triage — skills, knowledge, training greeting, human handoff.
  4. Pipeline + workflows Name Bookings stages. Agents → Workflows on stage enter. Agent router by stage so construction bots stay off new enquiries.
  5. Growth + wallet Campaigns and drips with wallet preview. Organization pays; no seat fee.

Capture

Get the enquiry onto one Booking before anyone opens Excel. Each card is one omnichannel job. There are no playbook-by-channel nested paths.

Lead captureOne buyer timeline before anyone opens Excel Lead qualificationFour fields before anyone spends a Saturday slot Portal lead follow-upPortal ping to booked visit in 48 hours — one deal Website enquiryMicrosite form to the same thread as WhatsApp Walk-in QRQR at the booth — CRM before they leave the stall Meta ad leadsAd DMs join the same visit job as portal WhatsApp Referral intakeReferrals get a Booking, not a group chat Channel-partner leadsCP leads with partner, SLA, and status — not weekly Excel Duplicate leadsThree portals, one conversation graph

Convert

Collateral, match, Saturday slots, reminders, post-visit, RM. Each card is one omnichannel job. There are no playbook-by-channel nested paths.

Brochure & floor planThe right floor plan in the thread — not a zip at 6 p.m. Inventory matchOffer units that match the wishlist — not the whole tower Site-visit bookingSlots on WhatsApp, confirm on voice, one Booking stage Visit reminderT-24h WhatsApp, T-2h if silent, voice if still dark No-show recoveryMissed the slot? WhatsApp rebook, same-day voice, move the card Cab pickupPickup pin and cab time — or the Saturday slot is theatre Post-visit follow-up48 hours after the tour: EMI, inventory, RM — or the deal dies EMI / loan introEMI in chat after intent — PDFs on email, not a list blast RM handoffRM gets the thread, fields, and visit — not a forwarded “hot”

Launch and nurture

Teasers, listings, alerts, digests, win-back, visited-not-booked. Each card is one omnichannel job. There are no playbook-by-channel nested paths.

Property launchMatched launch teasers on WhatsApp and email — then triage Property campaignsListings campaigns are omnichannel — not a WhatsApp-only URL Price-drop alertPrice and inventory shifts to matches — not the whole database Listings digestWeekly matched 3BHKs — email and WhatsApp, not this Saturday’s panic Cold-buyer win-back60-day silent tours: new inventory on WhatsApp, then voice Visited not bookedToured, no token: a second-pass job — not 60-day dormant yet

After-sales, leasing, compliance

Loan, construction, rentals, NRI docs, opt-out, handover referrals. Each card is one omnichannel job. There are no playbook-by-channel nested paths.

Loan status nudgesSanctioned is not disbursed — nudge the file on three hops Construction updatesSlab photos to booked buyers — not another launch teaser Rental viewingRentals get a viewing job — not a copied sales blitz Lease renewalRenewal is a stage and a cadence — not a sales Closed column Maintenance ticketsMaintenance is a ticket on the timeline — not a supervisor DM NRI docs collectionNRI KYC across time zones — email files, WhatsApp pings, voice last Opt-out complianceOpt-out is every channel — including the next launch template Post-handover referralAfter keys: NPS and a referral ask — not another qualifier

Illustrative library funnels

Percentages below are from CoPulse library playbook templates. They are not your Insights chart and not an SLA.

Library template Job URL Channels in template Estimate
Site-visit booking blitz site-visit-booking (+ capture family) WhatsApp, phone Replied 62% · Qualified 38% · Visit booked 18% · Visited 12%
New project launch teaser property-launch WhatsApp, email Opened 71% · Replied 14% · Site visit 6% · Closed 2%
Cold-buyer win-back cold-buyer-winback WhatsApp, phone Re-engaged 22% · Visit re-booked 8% · Closed 3%

Frequently asked questions

Directory-level questions before you open a leaf.

Why is there no WhatsApp version of each playbook?

IA is one URL per job. Channel overlays explain hops. Nested playbook×channel paths are forbidden.

Which surfaces do I actually open?

Setup → Channels, Library, Agent Studio, agent router, Agents → Workflows, autonomous agents (lists only), Growth campaigns/drips, Customers pipeline, appointments/calendars, omnichannel inbox, wallet preview, pricing.

Can autonomous tasks finish the visit job?

They send after you approve a plan and pick an existing template. Success is sends/reads/contacted — not appointment booked. Use qualifier + calendars + Visit Caller for visits.

Do property managers use the sales playbooks?

Use rental-viewing, lease-renewal, and maintenance-tickets. Do not copy token and disbursal stages.

Is SMS a hop?

Coming soon. Plan WhatsApp, voice, email, web, and Meta today.

Where is the product CRM?

Pipeline, AI agents, campaigns, inbox.

Related

Hub, pipeline, channels, product.

Guides

How and when. Jobs stay on playbooks.

Guides →

Real estate hub

ICPs, channels, pipeline, compare, guides.

Hub →

Buyer pipeline

Columns the jobs write.

Pipeline →

WhatsApp overlay

Session vs template on a hop.

Channel →

AI agents

Studio, skills, knowledge, workflows.

Product →

Campaigns

Library, audiences, wallet preview.

Product →

Wallet-only pricing

No seat fees. Pay for sends, calls, and AI.

Pricing →

Pick the job, not the channel microsite

Connect hops, attach RE Qualifier / Visit Scheduler / Visit Caller, preview the wallet, and keep one Booking timeline.

Get started free