Real estate guides: how and when, not extra job URLs

Definition

CoPulse real-estate guides are operator how-tos under /guides/realestate: definitions, numbered steps or decision tables, FAQPage JSON-LD on each leaf, and a single link to the omnichannel playbook that is the job. They are not a documentation theme (no docs.css), not a dated article feed, and not a second sitemap of WhatsApp-only jobs.

What you will not find here

SMS as live. Meta Cloud WhatsApp as the catalog path (Gupshup is live). Adaptive nurture. Autonomous success equal to appointment booked. A shared stop-when-booked contract across conversation agents, Growth drips, and autonomous tasks. Seat-priced logins. Those gaps are documented in the GTM loop notes and repeated in the leaves that touch them. If a capability is partial, the guide says what the operator does today: pick an existing library template, mark Visited by ops, exclude STOP from every runtime, preview the Organization wallet.

Surfaces named throughout: Agent Studio, skills, knowledge bases, agent router, workflows, autonomous agents, library templates, Growth campaigns/drips, pipeline stages, appointments/calendars, wallet-only pricing, omnichannel inbox, human handoff. Terminology: Organization and Project. Buyers & Tenants and Bookings match the real-estate vertical labels in product.

How to use this directory

If you are implementing, open the playbook in the In CoPulse box, not only the guide. If you are learning a mechanic (24-hour window, scoring, RERA posture), stay on the guide, then jump. Compare URLs remain canonical for vendor-class bake-offs; we did not clone those keywords here. Product URLs stay under /product/* — this hub does not invent /product/autonomous unless a later prompt asks.

Grouped index

Twenty-seven leaves. The industry hub and the site footer link here so primary nav stays Product, Channels, and Industries.

How CoPulse runtimes work

• Agents vs workflows vs autonomous — canonical job: Cold-buyer win-back playbook
• Workflow on stage change — canonical job: Post-visit follow-up playbook
• Autonomous win-back — canonical job: Cold-buyer win-back playbook
• Project knowledge bases — canonical job: Brochure & floorplan playbook
• Lead-capture agent — canonical job: Lead capture playbook

WhatsApp mechanics

• Qualify on WhatsApp — canonical job: Lead qualification playbook
• 24-hour window — canonical job: Property campaigns playbook
• Template approval — canonical job: Property campaigns playbook
• Opt-in and opt-out — canonical job: Opt-out compliance playbook
• RERA and WhatsApp — canonical job: Opt-out compliance playbook
• Listing campaigns how-to — canonical job: Property campaigns playbook

Capture and ads

• Speed to lead — canonical job: Portal lead follow-up playbook
• Instagram to visit — canonical job: Meta ad leads playbook
• Web chat to WhatsApp — canonical job: Website enquiry playbook
• Duplicate portal leads — canonical job: Duplicate leads playbook
• BHK budget scoring — canonical job: Lead qualification playbook

Visit operations

• No-show recovery — canonical job: No-show recovery playbook
• Saturday capacity — canonical job: Site-visit booking playbook
• Voice AI for visits — canonical job: Visit reminder playbook
• Measuring visit rate — canonical job: Site-visit booking playbook

ICP journeys

• Developer vs broker scripts — canonical job: Lead qualification playbook
• NRI journey — canonical job: NRI docs collection playbook
• Rental vs sales — canonical job: Rental viewing playbook
• RM handoff — canonical job: RM handoff playbook

Launch and after-sales

• Launch day — canonical job: Property launch playbook
• Loan file stuck — canonical job: Loan status nudges playbook
• Construction cadence — canonical job: Construction updates playbook

Map: guide to canonical playbook

One job URL per row. Guides never fork a WhatsApp-only twin. First-segment /guides does not collide with the client SPA.

Worked path for a new Project

Create the Organization wallet mindset first: usage, not seats — see pricing. Setup → Channels: Gupshup WhatsApp, Plivo phone, SES email, Meta if you run ads, web chat if the site matters. Library: submit visit utility and one marketing template before you need them. Agents → Studio: qualifier with knowledge, Visit Caller greeting, router. Agents → Workflows: Visited → EMI if you sell. Customers pipeline with real stages (leasing gets a different board). Growth for listing sends with wallet preview. Autonomous only for a clean dormant query, success = sends/reads. Inbox staffed for handoff. That is the platform. The guides below explain the sharp edges; the playbooks are what you run on Saturday.

Funnel language in product: Reached → Replied → Qualified → Site visits booked → Bookings. Campaign conversion remains reply rate. Phone replied is STT. CSV import is v1. Insights cues (Saturday saturation, loan follow-up cold) are operator prompts, not auto-fixes. Library estimates on blitz/launch/win-back templates are illustrations. Repeat that in measurement and launch leaves so nobody pastes a template percentage into a board meeting as Insights.

All guides

Same site.css chrome as the industry hub: hero, mock, steps, cards, one table, FAQ, CTA. More H2s than a playbook, still not a blog theme.