Offer units that match the wishlist — not the whole tower

Definition

Inventory match is the job of using BHK, budget, and locality on the Booking (and saved-search style custom properties) to choose which units the agent offers, then continuing to brochure send or a site-visit slot.

Every buyer hears about every unsold 4BHK

Launch lists blast the whole database. Match first. Saved-search digest is listings-digest. This playbook is the conversational match. Do not claim adaptive unit ranking. Do not claim marketplace inventory.

Omnichannel sequence

After capture and qualify. WhatsApp offers units. Voice if they book. Email digest is a different job.

How it runs in CoPulse

Conversation agent. Optional workflow on inventory_updated custom property to start a campaign — that is price-drop-alert. Autonomous list match only if you built the list; success sends/reads. Do not use autonomous tasks as the inbound qualifier. Conversation agents, Growth drips, and autonomous list sends are three systems with no shared stop-when-booked contract. 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

Fields, knowledge, qualifier. Wallet for offers.

Five new 3BHKs, only two in budget

Qualifier offers 12 and 14, not the 1.8Cr unit. Saturday 11 for 12. Click-path: Booking fields, knowledge, appointment. Launch teaser is excluded.

Cold-buyer win-back uses the same fields for 60-day dormant. Illustrative blitz 38% qualified. Pricing: matched WhatsApp on the wallet, not a per-unit SaaS fee.

Operators assemble this job on the Project. Click-path remains Customers properties → Studio knowledge → qualifier skills → optional Growth segment → pipeline. Keep the quotable definition in the brief for the team: Inventory match is the job of using BHK, budget, and locality on the Booking (and saved-search style custom properties) to choose which units the agent offers, then continuing to brochure send or a site-visit slot. Do not use autonomous tasks as the inbound qualifier. Conversation agents, Growth drips, and autonomous list sends are three systems with no shared stop-when-booked contract. While you implement, keep the parent playbooks directory, Qualified, WhatsApp overlay, Developers, 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 Inventory match 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)

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

Illustrative funnel (library template estimates)

Match quality changes visited %; estimates stay labeled. These percentages come from CoPulse library playbook templates (Site-visit booking blitz, New project launch teaser, or Cold-buyer win-back). They are not your project's Insights chart.