QR at the booth — CRM before they leave the stall

Definition

Walk-in QR capture is the job of turning a physical booth or site scan into a Booking within seconds, qualifying on web chat or WhatsApp, and offering a same-day tour slot instead of a paper lead sheet.

Notebooks do not survive the tea break

Supervisors collect numbers on paper, type them at 9 p.m., and the buyer already left. A QR to CoPulse web chat on the Project writes New enquiry while they stand there. If connectivity dies, say so: the operator still has a fallback form. No SMS ticket. No invented badge printer integration.

Omnichannel sequence

Physical presence is the source. Web/QR is hop one. WhatsApp if they prefer the phone. Voice only if a later visit is scheduled off-site.

How it runs in CoPulse

Conversation agent on web. Optional WhatsApp. Workflows tag source=walkin. No autonomous list of people who never scanned. 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.

Operator setup

Web channel live. Qualifier trained on launch inventory. Wallet for WhatsApp after they leave.

Sunday launch booth, 80 scans, 11 same-day tours

QR hits web chat. Qualifier filters tyre-kickers. Visit Scheduler offers 3 p.m. and 4 p.m. waves. Eleven accept. Others get WhatsApp continuation for Saturday. Ops watches visitors and Bookings, not a clipboard. Click-path: web inbox, kanban, appointment calendar.

Independent agents can run a single QR on a personal Project. Developers print per tower. Illustrative funnel still the blitz estimates once they join qualification. Pricing: chat and WhatsApp on the wallet; printing QR codes is free.

Operators assemble this job on the Project. Click-path remains Setup → Channels web + WhatsApp → Studio → pipeline → print QR to the public chat URL → wallet. Keep the quotable definition in the brief for the team: Walk-in QR capture is the job of turning a physical booth or site scan into a Booking within seconds, qualifying on web chat or WhatsApp, and offering a same-day tour slot instead of a paper lead sheet. 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, Independent agents, 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 Walk-in QR 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.

Channel sequence (one job, not extra URLs)

Physical-to-digital hops. There is no nested playbook-by-channel path.

Illustrative funnel (library template estimates)

Same-day show-up will beat the 12% visited estimate if they are already on site — still an estimate. 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.