Guide · Voice AI for visits

Voice AI confirmation calls for site visits

What the confirmation call should say, when to escalate, and how training greeting is set in Agent Studio. Visit Caller is a conversation agent on phone, not an autonomous list with appointment-booked success. Phone ‘replied’ means speech-to-text after the template, not purchase intent. Use it to confirm Saturday and pickup, then hand off haggling to the RM.

Greeting lives in Studio
STT ≠ interested
Escalate discounts

Start free Visit reminder playbook

Definition

Voice AI for site visits is an outbound or inbound Plivo call driven by an Agent Studio agent (Visit Caller) that confirms appointment time, pickup point, and project name, captures a yes/no in the transcript, and escalates objections — while the calendar and pipeline remain the source of truth for booked vs visited.

Why silent robocalls burn numbers

Generic IVR ‘press 1’ on a high-ticket home feels like spam. Missing pickup is already an Insights cue. A call that does not mention project and time wastes Plivo minutes and wallet.

Visit-reminder playbook is the job (WhatsApp + voice). This guide is the call script and Studio setup.

HowTo: set up Visit Caller

Phone channel connected. Agent with greeting. Calendar truth. WhatsApp still first in many desks; voice is confirm/miss.

Connect Plivo Setup → Channels → Phone. SMS is a separate channel (MSG91), not this hop.
Studio greeting Project name, time, pickup. Training greeting field.
Skills Confirm / reschedule if calendar allows / escalate price.
Router Do not let Visit Caller answer brochure PDF questions on WhatsApp.
Write the outcome Still coming → keep booked. Reschedule → new slot. No → recovery playbook. STT log is not enough.

How it runs on the platform

Conversation agent on phone. Autonomous may call a list but success is contacted, not visit booked — prefer Visit Caller on known appointments. 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: Friday 18:30 confirm for Saturday 11:00

WhatsApp utility already sent. No reply. Visit Caller dials. Greeting from Studio: Oakshire, 11:00, metro pickup. Buyer says Sunday. Agent offers Sunday 11:00 if open (capacity guide). Calendar updates. Pipeline stays Site visit booked with new time. If buyer asks 10% off, handoff RM — voice agent does not discount.

NRI: schedule the call in their evening. Same Studio agent, different slot. NRI journey guide.

Call outcome × action

STT is input. Ops is output.

Heard	Calendar	Pipeline	Next
Yes, coming	Keep	Site visit booked	Gate ops
New time	Move if cap allows	Booked new time	Pickup reconfirm
No / cancel	Release slot	Qualified or Dormant	No-show playbook if they vanish
Price objection	Keep until RM	Handoff	Inbox
Voicemail / no speech	Keep	Unchanged	Do not mark replied as interested

Honest limitations

G16 phone replied = STT. G3 autonomous success ≠ appointment. G11 SMS not live. No GPS no-show detection. Minutes meter wallet.

Keep this Voice AI for visits 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 Setup → Channels Phone. Agents → Studio Visit Caller. Router. Appointments. Inbox if escalate. Wallet for minutes. Canonical playbook: Visit reminder 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.

Phone overlay. AI agents. No-show.

Frequently asked questions

Desks buying a dialer that does not know the slot.

Where is the greeting configured?

Agent Studio on the Visit Caller agent. Not in a Growth campaign body.

Can autonomous replace Visit Caller?

List calls possible on phone channel for tasks, but success is contacted, not booked. Appointment-specific confirmations belong on the reminder job.

Does any speech count as campaign conversion?

Campaign conversion is reply rate; phone replied is STT. Neither is a Booking.

Escalate how?

Inbox / RM. Router stops the bot. Handoff checklist.

Recording and consent?

Follow your policy and law. This guide is not legal advice.

Pricing?

Voice minutes from Organization wallet. See pricing.

Hub, sibling guides, canonical playbook, product, pricing.

Confirm time and pickup, then stop talking

Visit Caller in Agent Studio, Plivo connected — visit-reminder playbook.

Get started free