Voice agent
Plivo + Voice AI profile. Training greeting on inbound. Confirm visit and pickup.
Confirm the visit, recover the no-show, write the deal
Phone is the confirmation and no-show hop: a Visit Caller-style voice agent confirms tomorrow's site visit and pickup, then writes back to the deal. Qualification usually already happened on WhatsApp. CoPulse uses Plivo telephony and Agent Studio training greeting for inbound voice — not a separate calling CRM.
- Visit Caller pattern
- Training greeting
- STT is not a booking
Brokers cannot dial every Saturday slot
The site-visit booking blitz playbook already pairs WhatsApp qualification with phone confirmation. Without voice, no-shows eat weekend inventory. CoPulse voice agents live in Agent Studio: set the training greeting spoken on inbound when configured, attach confirmation skills, hand off when confidence drops. Outbound visit reminders are a campaign or workflow, not an adaptive nurture brain. Phone replied in analytics is speech detected, not purchase intent. Autonomous tasks may call on WhatsApp/email/phone lists; they still succeed on sends/reads, not appointment booked.
Where this hop sits in the job
WhatsApp books the slot. Phone is hop three. Email is unused unless docs follow. Meta and web are earlier capture.
- Already qualified BHK and budget should be on the Booking before you spend a voice minute.
- T-24h / T-1 WhatsApp template first; voice if no reply or for pickup details.
- No-show day Same-day callback to rebook. That is a playbook hop, not a new channel site.
- Handoff Live inbox call monitoring; escalate to RM. Transcript stays on the contact.
How it runs in CoPulse
Visit Caller is a voice-surface agent in the real-estate playbook pack. Training greeting is configured per agent in Studio. Workflows can trigger an outbound call on stage enter. Do not claim SMS. Do not claim Meta Cloud WhatsApp. Click-to-talk on the website is a web+voice product option, not this overlay’s core story.
Inbox
Live calls, transcript, handoff. Same Buyer as WhatsApp.
Campaigns
Voice campaigns exist on the product channel page. For RE, prefer triggered confirmation over blasts.
Autonomous
May include phone after approve. Success ≠ visit booked today.
Operator setup
Connect phone under Setup → Channels, then bind the voice agent in Studio.
Setup → Channels (phone / Plivo) → Agents → Studio (training greeting, voice surface, handoff) → Workflows on Site visit booked → wallet for minutes. WhatsApp should already be live.
Prestige Lakeside, Saturday 11
Forty-four confirmation calls in the playbook estimate are not a call center hire. The Visit Caller uses the calendar slot already written by the scheduler. If the buyer says they cannot make it, the agent should offer another slot or hand off — not argue. Pickup details land on the deal so the site team is not guessing at the gate. That is why Insights-style notes about missing pickup and Saturday saturation belong next to voice, not next to another WhatsApp blast.
No-show recovery: WhatsApp rebook, then same-day voice. Cold win-back: WhatsApp inventory message, then a qualification call. NRI: schedule the call in their evening. Luxury: RM may take the call instead of AI. Commercial: RM-led. One channel, different playbooks — never a /phone nested playbook URL.
Voice as one hop
If voice is doing first-touch qualify, you are probably skipping WhatsApp badly.
| Job | This channel | Other hops | Exit |
|---|---|---|---|
| Book visit | T-1 confirm + pickup | WhatsApp slot first | Confirmed |
| Remind | If no WhatsApp reply | Template already sent | Confirmed / voicemail |
| No-show | Same-day callback | WhatsApp rebook | New slot |
| Win-back | Requalify call | WhatsApp opener | Visit re-booked |
Playbooks that use this hop
Each playbook is the full omnichannel job. This channel is one step, not a second URL tree.
Guide: Voice AI for site visits
How this hop sits in the omnichannel job.
Guide →Visit reminder
T-24h WhatsApp, voice if silent.
Open playbook →No-show recovery
Rebook chat, then call.
Open playbook →Site visit booking
Scheduler plus Visit Caller.
Open playbook →Cold buyer win-back
Inventory ping, then voice.
Open playbook →Frequently asked questions
Voice minutes, greetings, honest analytics.
Does a spoken yes book the visit?
The appointment skill / CRM write should update the stage. Analytics “replied” on phone is STT after the prompt, not a Booking by itself.
Where is the greeting set?
Agent Studio — training greeting spoken on inbound voice when set.
Telephony?
Plivo on the product phone page. Connect under Setup → Channels.
SMS reminders instead?
Use WhatsApp templates plus voice.
Autonomous stop on appointment?
Not shipped. Sends/reads (or call attempts), not visit booked.
Pricing?
Voice minutes debit the wallet. Pricing.
Related
Hub, sibling hops, product channel page, and the surface operators actually open.
Real estate hub
Buyers & Tenants, Bookings, ICPs, and jobs.
Back to hub →Where the slot was offered.
Open →Web
Optional click-to-talk from the site.
Open →AI agents
Voice surface, greeting, handoff, activity.
Explore →Phone & voice AI
Plivo, Voice AI Studio, live inbox calls.
Product channel →Wallet-only pricing
Minutes and AI usage, not a seat per caller.
See pricing →Put Visit Caller on the calendar slot
Connect phone, set the training greeting, and confirm Saturday without a dialer farm.
Get started free