Web chat agent
Studio deploy on web. Handoff to RM from the widget.
Chat on the listing, continue on WhatsApp
Project-site web chat captures the enquiry, then hands the same thread toward WhatsApp qualification instead of a disconnected form dump. The real-estate hub already calls out visitor tracking: web visitors can become leads before they message. CoPulse web chat is the widget on the microsite; the Booking should not restart when they switch to WhatsApp.
- Widget on the project site
- Visitors → leads
- Handoff to WhatsApp
Forms that email a CSV are how microsites leak
A “contact us” form that dumps to Gmail never qualifies BHK. Web chat on CoPulse is an inbox channel with the same conversation agent. Visitor tracking can attach a person before they authenticate. QR at the site booth should hit the same Project, not a paper register (walk-in-qr playbook). After capture, WhatsApp is still the right place for templates and slots. Voice confirms. Email is the brochure follow-up if they never switch numbers. Click-to-talk on the site is a phone overlay concern; this page is chat plus visitors.
Where this hop sits in the job
Web is hop one. WhatsApp hop two. Voice hop three. Meta is a parallel capture, not a child of web.
- Land Listing or campaign URL. Widget loads. Visitor token if web push/chat tracking is on.
- Chat Qualifier can start here, but keep public copy conservative.
- Identify Phone or WhatsApp number merges the visitor into a Buyer.
- Continue WhatsApp session for floor plan + appointment skill.
How it runs in CoPulse
Conversation agent on web. Knowledge for public FAQs. Router so the luxury penthouse widget does not use the affordable-housing agent. Workflows on enquiry created. Autonomous tasks do not scrape the widget; they need a CRM list.
Visitors
Hub copy: web visitors become leads before they message on WhatsApp. Keep that promise in CRM, not a side analytics tool only.
QR / walk-in
Same widget or a short URL into the Project. Do not start a second database.
WhatsApp handoff
Collect the number, continue qualification, respect 24h templates later.
Operator setup
Embed the CoPulse widget on the project domain. Connect WhatsApp on the same Project.
Setup → Channels (web chat) → Studio (web surface) → visitor/lead settings → WhatsApp channel → Pipeline. Wallet for chat AI. SMS not live.
Tower B page, then Saturday
A paid listing click opens tower B. The widget answers availability from the knowledge base, captures a number, and creates the enquiry while the visitor is still anonymous-to-named. WhatsApp receives the floor plan. The scheduler offers Saturday. Voice confirms. If they never give WhatsApp, email the brochure — but expect lower slot conversion. That is website-enquiry plus lead-capture plus site-visit-booking, not a web-only funnel page.
Walk-in QR at the sample flat should open the same widget or a prefilled chat so the booth does not invent a new lead class. Independent agents can put the widget on a Linktree. Developers should scope knowledge per tower. Do not run a launch blast from web chat; that is Growth campaigns on WhatsApp/email.
Web as capture hop
The widget’s job is identity plus first answer, not the whole close.
| Job | This channel | Other hops | Exit |
|---|---|---|---|
| Website enquiry | Widget + visitor | WhatsApp qualify | Enquiry |
| Lead capture | Identify visitor | Ads / portal | Buyer created |
| Qualify | Light FAQ | WhatsApp four questions | Qualified |
| Walk-in QR | Booth chat | Same CRM | Enquiry |
Playbooks that use this hop
Each playbook is the full omnichannel job. This channel is one step, not a second URL tree.
Guide: Web chat to WhatsApp
How this hop sits in the omnichannel job.
Guide →Website enquiry
Microsite form/chat into CRM.
Open playbook →Lead capture
Visitors and ads on one timeline.
Open playbook →Lead qualification
Usually finishes on WhatsApp.
Open playbook →Walk-in QR
Booth capture, same Project.
Open playbook →Frequently asked questions
Widgets, visitors, and not restarting the lead.
Is the widget the same agent as WhatsApp?
It can be the same Studio agent on two surfaces, or routed separately. The Buyer should still merge.
Visitor tracking vs GDPR?
Operators configure the widget and consent on their site. CoPulse stores the visitor-to-lead path the hub describes.
Click-to-talk?
That is phone/web voice on the product phone page. This overlay is chat capture.
Launch from the widget?
No. Use Growth campaigns. Web is inbound.
SMS the visitor?
Pricing?
AI on chat is wallet usage. 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 floor plan and slot usually go.
Open →Meta
Parallel capture from ads.
Open →Inbox
Web chat in the same queue as WhatsApp.
Explore →Web chat
Product widget, inbox, optional web voice.
Product channel →Wallet-only pricing
Chat AI usage on the Organization wallet.
See pricing →Stop emailing microsite CSVs
Embed chat, turn visitors into Buyers, and continue qualification on WhatsApp.
Get started free