A listing or microsite form should open the same qualification thread as WhatsApp, not a CSV in someone's inbox. The real-estate hub already treats visitors as trackable; the web overlay covers the widget. This playbook is the job: visitor or form → lead → New enquiry → RE Qualifier, then the rest of the buyer journey (WhatsApp brochure, phone schedule, WhatsApp post-visit).
Website enquiry is the job of turning a project microsite, listing page, or CoPulse web chat visitor into a Booking on the same qualification timeline used for WhatsApp and portals — not a nightly CSV from the host's mailbox.
Developers pay for landing pages that notify a group inbox. Nobody is on-call. The widget in CoPulse can qualify immediately with the same Agent Studio agent. If they leave, a workflow can start a WhatsApp template (Gupshup, approved) — you pick the template; autonomous planners do not auto-provision session-plus-closed-window pairs. Do not promise SMS follow-up.
Web inquiry is hop one in OmniView. WhatsApp qualify and brochure is hop two. Phone schedules the visit.
Conversation agent on web chat. Workflow on enter. Optional WhatsApp drip if they abandon the widget. Do not use autonomous tasks as the inbound qualifier. Conversation agents, Growth drips, and autonomous list sends are three systems with no shared stop-when-booked contract. WhatsApp live catalog is Gupshup, not an invented Meta Cloud hop. Phone is Plivo; email is SES. Wallet-only pricing: preview the Organization wallet before a blast. Organization and Project — never a shared inbox that vanishes when a broker leaves.
RE Qualifier in Agent Studio asks BHK, budget, locality, timeline. Knowledge holds the one-pager. Human handoff in the omnichannel inbox. Web Push opt-in may exist when the project's Web Push channel is active — not a replacement for WhatsApp.
Agents → Workflows on Booking enter New enquiry: start the qualifier, set source custom property, notify the owner.
Only if they go quiet after the first ping. Clock-based. Approved library template if the 24-hour WhatsApp window closed. Not adaptive nurture.
Keep construction and after-sales bots off brand-new enquiries. Route by pipeline stage and channel.
Setup → Channels web. Embed the widget. Same qualifier as WhatsApp.
Setup → Channels (Web, then WhatsApp) → Agents → Studio → Workflows → Customers visitors and pipeline → wallet for later WhatsApp.
Visitor #4821 asks Tower B pricing. Qualifier sends the knowledge PDF in chat, writes budget, offers to continue on WhatsApp. Morning, Visit Scheduler has Sunday 10. No email blast. No second CRM. Click-path: inbox (web), Booking, Agents → Studio, Setup → Channels web.
If the form is still an external host posting email, ops pastes into Customers or waits for CSV v1 — say that honestly. Illustrative blitz numbers apply only after they join the same funnel. Pricing: web AI usage and WhatsApp on the Organization wallet.
Operators assemble this job on the Project. Click-path remains Setup → Channels (Web, then WhatsApp) → Agents → Studio → Workflows → Customers visitors and pipeline → wallet for later WhatsApp. Keep the quotable definition in the brief for the team: Website enquiry is the job of turning a project microsite, listing page, or CoPulse web chat visitor into a Booking on the same qualification timeline used for WhatsApp and portals — not a nightly CSV from the host's mailbox. Do not use autonomous tasks as the inbound qualifier. Conversation agents, Growth drips, and autonomous list sends are three systems with no shared stop-when-booked contract. While you implement, keep the parent playbooks directory, New enquiry, Web overlay, Developers, Agent Studio, Growth campaigns, and wallet-only pricing in the same runbook. Do not invent Meta Cloud WhatsApp if the catalog is Gupshup. Do not promise adaptive nurture. Human handoff stays in the omnichannel inbox. Appointments and calendars are the visit truth when this job books time. Library templates are required outside the 24-hour WhatsApp window. Workflows fire on pipeline stage change only when you attach them under Agents → Workflows. The agent router keeps the wrong bot off this thread. Knowledge bases hold PDFs you uploaded. Preview the Organization wallet before a blast. Property managers should not paste sales token stages onto leasing jobs. The Website enquiry playbook never forks into a WhatsApp-only or voice-only child URL. Funnel percentages on some leaves are library template estimates from Site-visit booking blitz, New project launch teaser, or Cold-buyer win-back — not an SLA and not Insights. If this job mentions money, the Organization wallet is the meter. If it mentions a Saturday slot, Visit Caller and T-24h templates are in-product; cab dispatch is not. That is the honest operating manual for this URL.
Website job hops. There is no nested playbook-by-channel path.
| Hop | Channel | What happens | Exit to next hop |
|---|---|---|---|
| 1 | Web | Widget / form / visitor | Lead + Booking |
| 2 | Web or WhatsApp | RE Qualifier | Four fields |
| 3 | Brochure + slots | Calendar | |
| 4 | Voice | Visit Caller later | Confirm |
Once on the blitz path, template estimates apply. These percentages come from CoPulse library playbook templates (Site-visit booking blitz, New project launch teaser, or Cold-buyer win-back). They are not your project's Insights chart.
Widget versus forms and WhatsApp continuation.
No. Qualify on web chat. Offer WhatsApp when mobile or when you need templates later.
CRM visitors can become leads. That is already how the real-estate hub describes web.
Autonomous audiences are CRM/appointment/deal queries, not anonymous traffic.
That is the meta-ad-leads playbook, still one omnichannel URL.
Parent directory, sibling jobs, ICP, stage, channel overlay, and product surfaces.
How-to companion. The job URL stays this playbook.
Guide →One URL per omnichannel job.
Directory →All sources together.
Open →Ads, not the microsite.
Open →Microsites per project.
ICP →Where website Bookings start.
Stage →Widget and visitors.
Channel overlay →Agent Studio, skills, knowledge, router, workflows.
Explore agents →Library templates, audiences, wallet preview.
Explore campaigns →Web chat AI and follow-up WhatsApp debit the wallet.
See pricing →Put the widget on the Project, run RE Qualifier in chat, continue on WhatsApp when the buyer is on their phone.
Get started free