Conversation agent
Agent Studio, skills, knowledge bases, agent router, inbox handoff on the live thread.
Project knowledge bases for agents
Floor plans, price lists, and FAQs are uploaded so the qualifier cites the project, not a generic 3BHK script. Agent Studio skills without files will improvise. Improvisation on price is how you discount by accident or quote the wrong tower. Scope files per project or per broker cluster, then route campaigns to the matching agent.
- Upload what you will honour
- Scope per inventory
- Router picks the agent with the right files
Definition
A project knowledge base is the set of files and FAQs attached to a CoPulse conversation agent so answers about stacks, prices, amenities, and process are retrieved from your uploads — not from a general model guessing Indian real estate.
Why one mega-PDF for three towers fails
The bot retrieves the wrong price band. Developer vs broker scripts already warned you. Launch week multiplies the mistake across every reply window.
Brochure-floorplan playbook is the job for sending files. This guide is how the agent knows them.
HowTo: build a usable KB
Small, current, scoped. Update when price lists change. Agents do not scrape RERA for you.
- One inventory per agent or file set Oakshire vs the Sarjapur listing.
- Upload price, plans, FAQ What RMs already send manually.
- Tell the skill to cite, not invent Studio instructions. Handoff when missing.
- Router from campaigns Meta ad for Oakshire → Oakshire agent.
- Refresh on revision Old PDF is a silent liar.
How it runs on the platform
Conversation agent feature. Growth templates may attach media separately (you upload). Autonomous will not build the KB. 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.
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: price list revision Thursday
New band for 3BHK. Operator replaces the PDF in knowledge. Qualifier now quotes the new band. Old WhatsApp marketing template still has old numbers — submit a new template (approval guide) before Friday blast. Inbox RM told. Wallet: new template send later.
Broker: two knowledge sets, two agents, or one agent with clear ‘which project’ first question. Developer-vs-broker guide.
File × use × risk if stale
Keep them boring and true.
| File | Agent uses for | Stale risk | Owner |
|---|---|---|---|
| Price list | Budget fit | Wrong score / angry visit | Sales ops |
| Floor plans | Stack/facing | Wrong expectation | Product |
| FAQ / process | Token, GST, extras | RERA-sensitive slips | Counsel + RM |
| RERA cert | Registration cite | Old certificate | Compliance |
| Launch teaser images | Usually templates, not KB | Wrong campaign | Marketing |
Honest limitations
No auto image generation for plans (G7). No legal engine (RERA guide). Knowledge is not adaptive nurture. SMS not a KB channel.
Keep this Project knowledge bases 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 → knowledge. Router. Library if you also send the PDF on WhatsApp. Brochure-floorplan playbook. Canonical playbook: Brochure & floorplan 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.
Related
Frequently asked questions
Bots quoting last year’s price PDF.
Can one knowledge base hold three price lists?
It can physically. It will quote the wrong one. Scope or disambiguate hard.
Does the agent browse our website live?
It uses what you uploaded / attached. Do not assume live crawl.
Send the PDF as well as cite?
Brochure playbook. In-session if window open; template/media if not.
Autonomous win-back citing KB?
Tasks send templates you pick, not live KB Q&A. Replies go to the inbox agent with KB.
Who updates files?
Ops. Stale files are an operator bug.
Pricing?
AI retrieval still meters. Wallet. Pricing.
Related
Hub, sibling guides, canonical playbook, product, pricing.
All real estate guides
How-to articles. Jobs live on playbooks.
Directory →Brochure & floorplan playbook
The omnichannel job this guide teaches.
Playbook →Developer vs broker scripts
Scope files to the desk.
Guide →Templates
Blasts can still be stale — update both.
Guide →AI agents
Matching product surface.
Product →Pricing
Wallet-only. No seat fees. Preview before send.
Pricing →Upload the list you will honour, then qualify
Studio knowledge + router — brochure playbook when you send the file.
Get started free