Conversation agent
In Agent Studio, attach the project knowledge base (PDF brochures, floor plans, price sheets), the appointment skill, and handoff to an RM queue when confidence drops or the buyer asks for a human.
Launches, inventory, and CP leads on one project pipeline
Project sales desks run launches, inventory matching, and channel-partner leads from one pipeline while agents are trained on that project's brochures and floor plans. CoPulse labels the project as Buyers & Tenants and Bookings, so site visits sit on the deal instead of a side spreadsheet.
- Project knowledge bases
- Launch to matched buyers
- Channel-partner intake
Why developer desks leak demand
A launch week is not a broker's personal WhatsApp. Inventory changes hourly, channel partners dump Excel, and the same 3BHK FAQ is answered twenty times. If the qualifier is not trained on this project's brochure and floor plans, it invents availability. If the blast is not filtered by stated BHK and locality, you spend wallet on people who asked for a different micro-market. CoPulse keeps one Organization with a Project per development (or cluster), knowledge bases on the qualifier, and Growth campaigns with a wallet preview before the teaser goes out.
Omnichannel journey
Capture from the microsite, portals, and partner forwards; qualify on WhatsApp; confirm the visit on voice; send launch and construction mail on email — one buyer timeline in the omnichannel inbox.
- Web and portal capture Project site chat and portal webhooks create the enquiry. Visitor tracking can attach a person before they message on WhatsApp.
- WhatsApp qualification The conversation agent asks BHK, budget, locality, and timeline against this inventory, then offers Saturday slots from the appointment skill.
- Voice confirmation A Visit Caller-style voice agent uses the Agent Studio training greeting to confirm tomorrow's site visit and pickup — not a second CRM.
- Email for the long list Launch teasers and later construction milestones go to matched Buyers & Tenants. Hot replies stay on WhatsApp in the same thread.
How it runs in CoPulse
Conversation agents, Growth campaigns, and workflows on stage change. Autonomous outbound is optional for a dormant list after a launch — success today is sends and reads, not site visit booked.
Campaigns and drips
Library templates on WhatsApp (Gupshup) plus email. Filter CRM by BHK and locality. Preview wallet cost. After 24 hours, use an approved template — free-text session replies will fail.
Workflows
Agents → Workflows: on Site visit booked, send the reminder template and set a custom property. On Visited, queue EMI follow-up. Do not pretend this is the same runtime as an autonomous task.
Agent router
Route by pipeline stage or channel so launch replies do not land on a generic support agent. Human handoff keeps the full inbox thread.
Operator setup
One Organization, one Project for the development. Pick Real Estate at signup so nav reads Buyers & Tenants and Bookings.
Setup → Channels (WhatsApp via Gupshup, email, phone, web, Meta if you run ads) → Library (templates) → Agents → Studio (knowledge + appointment skill + guardrails) → Agents → Router → Setup → Customers → Pipeline → Growth campaigns with wallet preview.
Monday launch, Saturday visits
A typical developer week on CoPulse looks like the in-product Growth loop, not a generic chatbot demo. Monday: segment Buyers & Tenants who asked for Whitefield last quarter, preview wallet cost, send the launch teaser from Library templates, and let the qualifier handle tell-me-more replies in the omnichannel inbox. Wednesday: the appointment skill has filled Saturday slots; T-24h WhatsApp reminders are queued; a Visit Caller-style voice agent confirms pickup using the training greeting in Agent Studio. Friday: Bookings in disbursal get a drip, not a second launch blast. None of this requires SMS. None of it claims an autonomous task will stop when the visit is booked — if you later add an autonomous list for 60-day dormant buyers, you will still measure sends and reads until product success criteria change.
Operators should keep one knowledge pack per tower. Mixing three price lists without routing is how the bot quotes the wrong inventory on launch day. Use Agents → Router if teams split by cluster. Human handoff stays on for token talks.
Channel sequence for a launch week
Every hop writes the same Booking. There is no separate WhatsApp playbook URL.
| Hop | Channel | What happens | Owner |
|---|---|---|---|
| 1 | Web / portal | Enquiry + visitor | Capture agent |
| 2 | Qualify + floor plan + slot | RE Qualifier | |
| 3 | Phone | T-1 confirm + pickup | Visit Caller |
| 4 | Launch digest / construction | Campaign | |
| 5 | Inbox | RM handoff with thread | Human |
Playbooks for this team
Jobs are omnichannel. Each link is one URL, not a WhatsApp-only clone.
Frequently asked questions
Developer desks, knowledge bases, and wallet launches.
Can one agent cover three towers?
Yes, if the knowledge base is scoped per Project or you route by campaign. Mixing three price lists in one agent without files is how the bot quotes the wrong tower. See project knowledge bases.
Do we need a calling team on launch day?
Voice AI covers confirmation and no-shows. Negotiation and token remain human. The RM sees the WhatsApp thread in the omnichannel inbox — not a call-only silo.
How do channel partners fit?
Tag source and partner on the deal, enforce SLA with workflows, and send status back. That job is channel partners, not a second spreadsheet.
Will autonomous nurture stop when they book a visit?
No. Autonomous tasks count sends and reads today. Use the conversation agent and appointment skill to book the visit; use autonomous only for a dormant list after you approve a plan.
WhatsApp via Meta Cloud API?
Live WhatsApp in the catalog is Gupshup. Connect it under Setup → Channels. Do not plan a Meta Cloud WhatsApp hop that is not in the project.
Where is pricing?
Wallet-only — no seat fees. Preview the launch blast. Pricing.
Related
Parent hub, sibling teams, and product surfaces this ICP actually uses.
Real estate hub
Buyers & Tenants, Bookings, site visits — directory of ICPs and jobs.
Back to hub →Brokers
Multi-project portal speed-to-lead in a shared inbox.
Open →Channel partners
CP intake and SLA on the same developer pipeline.
Open →Campaigns & drips
Launch teasers, matched audiences, wallet preview.
Explore →Wallet-only pricing
Launch blasts debit the Organization wallet, not per-user seats.
See pricing →Stand up the project qualifier
Connect WhatsApp, upload the brochure pack, and book the first site visit from chat.
Get started free