Playbook · knowledge

The right floor plan in the thread — not a zip at 6 p.m.

Agents pull the right brochure and floor plan from the project knowledge base during the chat instead of mailing a zip later. This job is knowledge plus the qualifier, usually on WhatsApp or web, with email only when NRI files are huge. It is not a WhatsApp-only URL and not the inventory-match job (that picks units from wishlist fields).

  • Knowledge PDFs
  • In-session send
  • Email if the file is huge

Definition

Brochure and floor-plan send is the job of attaching the correct project PDF from knowledge during a live qualification or visit-intent thread so the buyer does not wait for an RM to email a zip from a laptop.

Brochures live on laptops; buyers live on WhatsApp

RMs forward 40MB zips that fail. Knowledge in Agent Studio holds the one-pagers you are willing to send. In-session WhatsApp can free-text; outside 24h you need a library template (maybe with a URL). AI template draft is text-only — operators upload header images. No generated floor-plan art.

Omnichannel sequence

Usually after web/portal/Meta capture. WhatsApp or web chat delivers the PDF. Voice does not read PDFs. Email for NRI packs.

  1. Know the unit Four fields or at least BHK + tower.
  2. Knowledge retrieve Agent Studio knowledge, not a random Drive link.
  3. Send on the open channel WhatsApp session or web chat.
  4. Offer the slot Visit Scheduler after they have something to look at.

How it runs in CoPulse

Conversation agent with knowledge. Workflows unused unless you auto-send on Qualified enter. Drips are the wrong tool for a one-shot PDF. Autonomous list brochure blasts belong under property-campaigns, not this job. 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.

Knowledge bases

Per-project PDFs. Stale plans are worse than no bot.

Conversation agent

RE Qualifier sends the file. Handoff if they want a custom stack plan.

Library templates

Closed window: template with brochure URL.

Email

SES when WhatsApp cannot carry the pack (NRI).

Operator setup

Upload knowledge. Train the agent which filename is Tower B. Wallet for the send.

Agents → Studio → knowledge → Setup → Channels WhatsApp/email → Library URL template → pipeline Qualified.

They ask for Tower B while still in session

Qualifier sends the typical floor. Buyer asks car park. Handoff to RM in inbox. Slot offered after. Click-path: Studio knowledge, inbox, appointment. No zip.

Inventory-match decides which tower; this job delivers the PDF. Illustrative blitz: replied 62% then qualified 38% — estimates. Pricing: WhatsApp media/sends on the Organization wallet.

Operators assemble this job on the Project. Click-path remains Agents → Studio → knowledge → Setup → Channels WhatsApp/email → Library URL template → pipeline Qualified. Keep the quotable definition in the brief for the team: Brochure and floor-plan send is the job of attaching the correct project PDF from knowledge during a live qualification or visit-intent thread so the buyer does not wait for an RM to email a zip from a laptop. 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 Brochure & floor plan 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)

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

Hop Channel What happens Exit to next hop
1 Web / portal / ads Enquiry Booking
2 WhatsApp / web PDF from knowledge Buyer has plan
3 WhatsApp Slot offer Calendar
4 Email Huge NRI pack Optional

Illustrative funnel (library template estimates)

Collateral sits inside the blitz path. 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.

100%Reached (est.)
62%Replied (est.)
38%Qualified (est.)
18%Visit booked (est.)

Frequently asked questions

Knowledge versus campaigns.

Can autonomous email every brochure?

That is a list campaign. This job is in-thread retrieve. Autonomous success is sends/reads.

Generate a new floor-plan image?

Not shipped. Upload the PDF you own.

24h window?

In-session send. Else approved template with link.

Wrong tower PDF?

Human handoff. Fix knowledge.

SMS the link?

Coming soon.

Put Tower B in knowledge, not in a zip

Agent Studio knowledge, in-thread send, then Visit Scheduler — one job URL.

Get started free