Guide · Developer vs broker scripts

Developer vs broker qualification scripts

Developers qualify against one project inventory; brokers qualify across projects, so the questions and knowledge bases differ. A shared ‘3BHK script’ that names a single tower will lie in a broker Organization. A broker script that asks ‘which of our 40 projects’ on a developer microsite will stall a campaign lead who already clicked Oakshire.

Scope the knowledge base
Disambiguate before price
One Project in CoPulse ≠ one tower unless you say so

Start free Lead qualification playbook

Definition

A developer qualification script assumes a known project (campaign or page) and checks BHK, budget, timeline against that knowledge base. A broker qualification script first disambiguates inventory (which project or locality cluster), then the same fit questions, with knowledge files scoped so the agent cannot quote Project A’s price list on a Project B thread.

Why one script poisons both ICPs

Agencies paste the developer FAQ into a channel-partner desk. The bot promises a payment plan the broker cannot honour. Conversely, a developer runs a Meta ad to one tower and the bot asks ‘which of our projects?’ like a marketplace. Both look like ‘AI failed.’ Both are scoped files and router mistakes.

CoPulse Projects can hold many campaigns. That does not merge knowledge. Upload Oakshire PDFs to the Oakshire agent or file set. Route Meta campaign leads to that agent.

HowTo: pick and attach the right script

Start from ICP pages, then the lead-qualification playbook. This guide is only the script fork.

Choose ICP Developer vs broker vs channel partner. Do not mix payment-plan claims.
Upload knowledge for that inventory Floor plans, price bands, FAQs. Developers: one project. Brokers: cluster files or honest ‘I will check.’
Write question one differently Developer: confirm BHK on the named project. Broker: locality/project pick.
Router Campaign or channel → the matching Studio agent. Visit Caller stays on confirmations.
Handoff rules Developer RM vs broker RM. Inbox, not a forwarded screenshot.

How it runs on the platform

Conversation agents plus knowledge bases. Do not solve broker vs developer with a Growth blast. 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: same buyer, two Organizations

Buyer clicks a developer ad. Developer Project: qualifier never asks which city project; it asks BHK vs Oakshire stacks and cites the Oakshire knowledge base. Same buyer later WhatsApps a broker. Broker Project: qualifier asks Whitefield vs Sarjapur, then pulls the matching PDF. If the broker uploaded both PDFs into one unscoped bot, the agent may quote both — that is an operator file error, not ‘AI being creative.’

Channel partners need a third honesty: they cannot promise developer discounts. Script says they will check with the principal. See channel-partners ICP.

Script fork

Decision table for question one and knowledge.

Desk	Question one	Knowledge	Forbidden claim
Developer	BHK/budget on this project	That project’s files	Inventory you do not have
Broker	Locality / which listing	Per-cluster or per-project files	Developer payment plan you cannot honour
Channel partner	Project they were assigned	Principal’s allowed FAQ	Independent discount
NRI desk	Timezone + docs after fit	Same inventory plus docs list	Guaranteed visa/loan
Rental desk	Lease dates + budget	Unit availability	Sales token stages

Honest limitations

There is no magic ‘auto-detect developer vs broker’ mode. You configure agents on the Project. Knowledge bases do not scrape RERA sites by themselves. RERA claims stay conservative — see the RERA guide; not legal advice.

Keep this Developer vs broker scripts 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 (separate agents or clearly scoped knowledge). Router. Library. Customers pipeline. ICP-specific playbooks still omnichannel. 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.

ICP pages

Developers and brokers. Knowledge how-to: project knowledge bases.

Frequently asked questions

Agencies pasting one FAQ into every bot.

Can one agent hold three price lists?

Only if you like wrong quotes. Scope files or split agents and route by campaign.

Should brokers use the developer’s exact script?

No. Disambiguate inventory first. Then fit questions can look similar.

Does the library template differ?

Often yes — marketing templates name a project. Brokers need templates that do not imply they own the development.

Workflows?

Stage-change workflows can be shared (Visited → EMI) on developer desks. Brokers may skip loan-disbursal stages.

Autonomous win-back across 40 listings?

List + template you pick. The template still cannot lie about inventory. Success is sends/reads.

Pricing?

Same wallet-only Organization meter. Extra agents are not seats. See pricing.

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

Scope the files, then write question one

Separate developer and broker agents on the Project, route campaigns, qualify without lying.

Get started free