Agent Studio guardrails
Avoid topics, escalate phrases, min confidence, handoff / queue holding — as the product actually exposes on the agent.
Fewer leads, tighter appointments, cleaner RM handoff
Luxury desks protect appointment quality with Agent Studio guardrails and RM handoff instead of blasting every enquiry. Volume playbooks that spray Saturday slots will burn a high-consideration buyer. CoPulse still tracks Buyers & Tenants and Bookings — the difference is min confidence, escalate phrases, and a human before the site visit is offered.
- Guardrails in Studio
- Appointment quality
- RM inherits the thread
Launch-blast mechanics shame luxury inventory
Early-bird WhatsApp to 2,400 unmatched contacts is the opposite of this ICP. You want qualification that is allowed to stop, a calendar with sparse slots, and Agent Studio guardrails: avoid topics, escalate phrases, minimum confidence, queue holding. Knowledge bases are invitation-only PDFs, not a public price list. Wallet preview still matters so nobody accidentally broadcasts the penthouse to the last launch audience.
Omnichannel journey
Web or referral, short WhatsApp qualify, fast RM on inbox, voice only if the RM wants a confirmation, email for the private deck.
- Web / referral High-intent forms. Visitor tracking is useful; public chat widgets should not dump FAQs about price.
- WhatsApp Qualify softly. Offer a slot only after guardrails pass or the RM approves.
- Inbox handoff The RM sees the full thread. That is the product, not a summary SMS (SMS is not live anyway).
- Voice / email Private tour confirm and deck. Training greeting should sound like the house, not a call center.
How it runs in CoPulse
Conversation agent with strict Studio settings. Workflows to notify the RM on escalate. Skip autonomous win-back blasts unless the RM built the list. Success of those tasks is still sends/reads.
Appointment skill
Sparse calendar. Quality over fill rate. Insights about Saturday saturation apply less than RM availability.
Router
Luxury inventory to a named RM, not a round-robin qualifier that also does affordable housing.
Campaigns
If you launch, segment brutally and preview wallet. Library templates must match the tone.
Operator setup
A dedicated Project so router and knowledge never mix with high-volume towers.
Agents → Studio (guardrails + knowledge) → Router to RM → Channels → Pipeline → optional campaign with wallet preview. Gupshup WhatsApp. No Meta Cloud invention.
When the bot should stop talking
A penthouse enquiry should not receive a Saturday 10–12 mass slot. Agent Studio min confidence and escalate phrases send the thread to the named RM. Avoid-topics keep price lists off a chat the buyer asked to keep private. The RM opens inbox and sees every bubble — that is handoff, not a failure. If someone on the team still clicks Growth and targets last quarter's affordable-housing audience, wallet preview is the last chance to stop. Luxury is not a different product SKU; it is a Project with tighter guardrails, a thinner calendar, and campaigns you mostly do not send.
Put invitation decks in a Project-scoped knowledge base. Router must not share the volume qualifier. If you use voice, the training greeting should sound like the house. Autonomous win-back of people who toured last year is optional and still send/read scored. Prefer a named RM drip you can audit.
Luxury hops
Handoff is a feature, not a failure of the bot.
| Hop | Channel | What happens | Owner |
|---|---|---|---|
| 1 | Web / referral | Quiet capture | Form / chat |
| 2 | Soft qualify / stop | Guarded agent | |
| 3 | Inbox | RM thread | Human |
| 4 | Phone / email | Private tour + deck | RM |
Playbooks for this team
Jobs are omnichannel. Each link is one URL, not a WhatsApp-only clone.
Frequently asked questions
Guardrails, not more broadcasts.
Can we still use launch teasers?
Yes, on a tiny matched list with wallet preview. This ICP exists so that is optional, not default.
What do guardrails actually do?
Agent Studio: avoid topics, escalate phrases, min confidence, handoff. Configure them; do not assume a luxury persona alone is enough.
Autonomous nurture?
Usually skip. If used, it will not stop on appointment booked.
Knowledge leaks?
Scope the knowledge base to the Project. Do not attach the affordable-housing price PDF.
Voice?
RM-controlled. Training greeting in Studio for inbound.
Pricing?
Wallet usage. Pricing.
Related
Parent hub, sibling teams, and product surfaces this ICP actually uses.
Real estate hub
Buyers & Tenants, Bookings, site visits — directory of ICPs and jobs.
Back to hub →NRI sales
Time zones and docs on high-consideration deals.
Open →Developers
When the same house also runs volume launches.
Open →Agent Studio
Persona, knowledge, guardrails, handoff.
Explore →Wallet-only pricing
You still pay usage — you just send fewer, better messages.
See pricing →Turn down the blast
Set guardrails, route to an RM, and treat the site visit as scarce.
Get started free