Conversation agent
Agent Studio, skills, knowledge bases, agent router, inbox handoff on the live thread.
Saturday saturation and missing pickup details are why qualified buyers never visit; open Sunday slots and confirm pickup. CoPulse Insights can narrate that the roster is full and pickup is missing — those are operator cues, not an auto-reshuffle of your calendar. If every qualified chat is offered only 11:00 Saturday, you will manufacture no-shows.
Saturday slot capacity is the honest number of accompanied visits your Project can run that day (RMs, cabs, site staff) represented as appointment inventory. Qualification without capacity is how funnels look healthy in Qualified and die in Site visit booked. Pickup confirmation is part of capacity, not a nicety.
Desks qualify all week into one magic hour. Cabs bunch. Site staff rush. Buyers without a pickup pin wander. Insights STAGE_NARRATIVE may mention Saturday-slot saturation and missing pickup. If you treat that as a dashboard trophy instead of opening slots, nothing changes.
Library playbook estimates (e.g. visit booked 18 / visited 12 on a blitz template) are not your capacity. Your capacity is the calendar.
Treat appointments as inventory. The site-visit-booking playbook is the job. Cab pickup is a related job — CoPulse does not dispatch cabs.
Booking is conversation agent + calendars. Autonomous tasks do not ‘find more Saturday hours.’ 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.
Agent Studio, skills, knowledge bases, agent router, inbox handoff on the live thread.
Clock-based sends from library templates. Wallet preview. Not adaptive nurture.
Agents → Workflows. Fire on pipeline stage change. Do not confuse with inbound chat.
List plus objective after plan approve. Success is sends/reads/contacted, not visit booked.
Friday evening 14 qualified contacts want Saturday. Calendar has six 11:00s and four 16:00s and six Sunday 11:00s. Qualifier offers in that order. Eight buyers take Sunday. Pickup pins collected. Insights still flags Saturday as tight — operator does not add a seventh 11:00 ghost. Two no-shows Saturday are recovered per the no-show guide; slots not backfilled magically.
Click-path: set calendar hours, attach qualifier skill, test a WhatsApp book, confirm wallet if templates send. Organization wallet meters reminders.
Decision table when qualifier wants to offer a slot.
| Calendar state | What agent offers | What not to do | Stage |
|---|---|---|---|
| Slot open + pickup missing | Ask pin first | Book without pickup | Stay Qualified until pin |
| 11:00 at cap | 16:00 or Sunday | Overbook 11:00 | Booked only on real slot |
| All weekend full | Waitlist / next week | Promise ‘we will squeeze you’ | Qualified |
| Buyer is NRI timezone | Voice + weekday video? then visit | Force Saturday 11:00 IST blindly | See NRI guide |
| No-show released | Offer to next Qualified | Keep ghost name on 11:00 | Booked transfers |
Insights cues are not auto-scheduling. Cab dispatch is not a CoPulse module. Autonomous success will not equal ‘visited.’ Template estimates in the library are not this Project’s cap.
Keep this Saturday capacity 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 Appointments/calendars on the Project. Agents → Studio qualifier offers those slots. Customers → Pipeline Site visit booked. Optional Insights for saturation cues. Cab ops remain human. Canonical playbook: Site-visit booking 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.
Visit rate math: measuring visit rate. No-shows: no-show guide. Pipeline: site visit booked.
Sales heads staring at a full Saturday and empty Sundays.
No. Insights may tell you. You add calendar inventory and the qualifier starts offering it.
No. Collect the pin, coordinate with your vendor. The cab-pickup playbook is the job checklist.
That is an ops policy. If you overbook, the calendar is no longer truth. Prefer confirmations and recovery over silent overbook.
No. Only a cancel, a no-show process, or an operator edit.
Yes, Organization wallet. Preview before a Friday night blast to 200 ‘maybe Saturdays.’
Viewing capacity is a different pipeline. Do not copy token stages. See rental vs sales.
Hub, sibling guides, canonical playbook, product, pricing.
How-to articles. Jobs live on playbooks.
Directory →The omnichannel job this guide teaches.
Playbook →Free the ghost slot.
Guide →Funnel vs reply rate.
Guide →Matching product surface.
Product →Wallet-only. No seat fees. Preview before send.
Pricing →Calendars, pickup fields, honest caps — then the qualifier can tell the truth.
Get started free