Guide · Saturday capacity

Saturday site visit capacity

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.

  • Capacity is a number, not a hope
  • Sunday is overflow, not a rumor
  • Pickup is a field

Definition

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.

Why qualified never becomes visited

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.

HowTo: make Saturday real

Treat appointments as inventory. The site-visit-booking playbook is the job. Cab pickup is a related job — CoPulse does not dispatch cabs.

  1. Count real accompanies RMs × hours × site constraint. That integer is Saturday cap.
  2. Publish Sunday / twilight slots Calendars on the Project. Qualifier must offer them, not only 11:00.
  3. Require pickup field Pin or landmark before booked is green. Missing pickup is an Insights cue for a reason.
  4. Stop offering over cap If 11:00 is full, the agent says so. Do not double-book to ‘look busy.’
  5. T-24h confirm Visit reminder templates + optional Visit Caller. Reads ≠ they will come.

How it runs on the platform

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.

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: cap 6, 14 qualified chats on Friday

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.

Demand vs inventory

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

Honest limitations

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.

Measure it

Visit rate math: measuring visit rate. No-shows: no-show guide. Pipeline: site visit booked.

Frequently asked questions

Sales heads staring at a full Saturday and empty Sundays.

Will CoPulse auto-open Sunday slots when Saturday saturates?

No. Insights may tell you. You add calendar inventory and the qualifier starts offering it.

Is cab pickup automated?

No. Collect the pin, coordinate with your vendor. The cab-pickup playbook is the job checklist.

Can we overbook because 30% no-show?

That is an ops policy. If you overbook, the calendar is no longer truth. Prefer confirmations and recovery over silent overbook.

Does a read reminder free a slot?

No. Only a cancel, a no-show process, or an operator edit.

Wallet for extra reminder templates?

Yes, Organization wallet. Preview before a Friday night blast to 200 ‘maybe Saturdays.’

Property managers / rentals?

Viewing capacity is a different pipeline. Do not copy token stages. See rental vs sales.

Publish Sunday before you close Friday qualification

Calendars, pickup fields, honest caps — then the qualifier can tell the truth.

Get started free