Price and inventory shifts to matches — not the whole database

Definition

Price-drop and inventory alert is the job of notifying a matched segment when you change price or availability properties, on WhatsApp and email, then qualifying replies into a fresh visit — without blasting every number in the Project.

Price-drop to 50,000 numbers is how template quality dies

Ops hears “alert everyone.” Wallet preview should scare them. Match on wishlist fields. Autonomous may send the list; it will not know they booked. No SMS. No adaptive who-to-alert.

Omnichannel sequence

CRM segment → WhatsApp/email → qualify → voice visit.

How it runs in CoPulse

Campaigns + qualifier. Optional autonomous list. Workflow if you fire on property change. Autonomous agents may follow a launch list on WhatsApp, email, or phone after plan approve. They do not create templates, do not adapt from prior outcomes, and do not stop when a site visit is booked. Campaign reply rate is not an Interested CRM state. 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

Properties, templates, segments, wallet.

Five new 3BHKs, 318 matched, not 12,000

Win-back library preview is similar copy. Ops sends 318. Replies book Sunday. Click-path: segment, Growth, inbox.

Win-back is 60-day dormant; this alert can be same week as a price change. Illustrative launch or win-back % depending on audience. Pricing: wallet.

Operators assemble this job on the Project. Click-path remains Customers properties → Library alert template → Growth segment → wallet → Studio qualifier. Keep the quotable definition in the brief for the team: Price-drop and inventory alert is the job of notifying a matched segment when you change price or availability properties, on WhatsApp and email, then qualifying replies into a fresh visit — without blasting every number in the Project. Autonomous agents may follow a launch list on WhatsApp, email, or phone after plan approve. They do not create templates, do not adapt from prior outcomes, and do not stop when a site visit is booked. Campaign reply rate is not an Interested CRM state. 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 Price-drop alert 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)

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

Illustrative funnel (library template estimates)

When the audience is dormant-like, use win-back template estimates. 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.