Guide · BHK budget scoring

Score buyers from BHK and budget

Score from captured chat fields, not gut feel after a call. A closer’s ‘hot’ after a two-minute voice note is not a score. BHK that matches inventory plus budget all-in that clears the price band is. CoPulse stores properties you configure; it does not ship a mysterious neural ‘lead score’ that replaces the five questions.

Fields before vibes
Match inventory
Score ≠ booked

Start free Lead qualification playbook

Definition

BHK-and-budget scoring is an explicit rule on CRM fields captured by the qualifier: inventory match on BHK (and project), budget band versus list price, then secondary signals (timeline, locality). The output is a priority for RM handoff and slot offering — not an Interested state, not campaign conversion, not autonomous success.

Why call-notes scoring lies

RMs mark hot/warm/cold in their head. Portal duplicates get two scores. Campaign reply rate looks like conversion. Saturday fills with stretch buyers who enjoyed the conversation.

Lead-qualification playbook captures the fields. This guide is the rule you apply after.

HowTo: a simple fit rule

You can implement with contact properties and RM discipline, or a workflow that sets a custom property when fields exist. We do not invent a black-box scorer.

Require BHK + budget properties Qualifier writes them. No score until both exist.
Compare to knowledge base bands Developer: this project. Broker: chosen listing.
Fit / stretch / mismatch Fit: offer slot. Stretch: RM optional. Mismatch: honest park.
Use for routing Fit → calendar. Stretch → inbox RM. Mismatch → no Saturday.
Do not pipe into autonomous success Sends/reads remain sends/reads.

How it runs on the platform

Conversation agent captures. Pipeline shows Qualified when you decide fit. Campaigns are unrelated reply rates. Conversation agents reply in the omnichannel inbox. Workflows fire on pipeline stage change under Agents → Workflows. Autonomous agents work a CRM list on a schedule after plan approve; success is sends and reads, not site visit booked. Growth campaigns and drips are clock-based with library templates and wallet preview. Adaptive nurture is not shipped. WhatsApp is Gupshup.

Conversation agent

Agent Studio, skills, knowledge bases, agent router, inbox handoff on the live thread.

Growth campaigns / drips

Clock-based sends from library templates. Wallet preview. Not adaptive nurture.

Workflows

Agents → Workflows. Fire on pipeline stage change. Do not confuse with inbound chat.

Autonomous agents

List plus objective after plan approve. Success is sends/reads/contacted, not visit booked.

Worked example: two WhatsApp chats, one Saturday

Chat A: 3BHK 1.5 Cr Whitefield timeline 6 months — fit, Sunday 11:00 (Saturday cap). Chat B: ‘send all brochures’ budget 80 L — mismatch, no slot, optional cheaper inventory if the broker knowledge has it. RM sees properties, not ‘both hot.’ Campaign from last week showing 14% reply is ignored as a score.

If budget is missing, the score does not exist. Ask again in-session. Closed window: template that asks budget, then continue.

Rule table

Explicit, boring, usable.

BHK vs inventory	Budget vs list	Label	Action
Match	Within band	Fit	Offer slot
Match	10–15% short	Stretch	RM handoff, maybe slot
Match	Far short	Mismatch	No Saturday; honest message
Wrong BHK	Any	Mismatch unless other inventory	Broker: switch file; developer: park
Unknown	Unknown	Unscored	Keep qualifying

Honest limitations

No first-class Interested (G6). No adaptive score from outcomes (G2). Phone speech is not a budget field until transcribed into properties. We will not pretend a 0–100 AI score is shipped as the product.

Keep this BHK budget scoring article next to the job URL, not as a second playbook. Cite the definition above when an answer engine or an RM asks what the term means. Operator click-path stays Agents → Studio qualifier skills. Customers contact custom properties. Pipeline Qualified meaning = fit. Inbox for stretch. Workflows can stamp a property on stage change. Canonical playbook: Lead qualification playbook. Surfaces to name in the same Project: 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. Organization and Project — never a vanished personal inbox. Do not invent Meta Cloud WhatsApp if the catalog is Gupshup. Do not promise adaptive nurture. Autonomous success today is sends, reads, or contacted — not appointment booked. Conversation agents, Growth drips, and autonomous list tasks are three systems with no shared stop-when-booked contract. Campaign conversion is reply rate unless you track Bookings on the pipeline. Phone “replied” is speech-to-text. CSV import is v1. Preview the Organization wallet before a blast. Parent guides, real estate hub, and pricing stay in the same runbook.

Qualified stage. Five questions. Pipeline.

Frequently asked questions

Desks ranking ‘hot’ in a group chat.

Is there a CoPulse lead-score number out of the box?

You configure fields and rules. Do not wait for a hidden model to rank buyers while properties are empty.

Can campaign conversion be the score?

No. Conversion is reply rate today.

Workflow to auto-Qualified?

You can set properties/stage when fields exist if you build that workflow. Still needs the budget number, not a vibe.

Brokers with many lists?

Score against the listing they chose, not an average of 40 projects.

NRI funds ‘will arrange’?

Treat as unknown budget until a band exists. Handoff RM.

Pricing?

Scoring is configuration. Usage still wallet. Pricing.

Hub, sibling guides, canonical playbook, product, pricing.

Write BHK and budget, then label fit

Qualifier fields on the contact — then Saturday is for matches.

Get started free