A lobby QR puts the walk-in on the shared inbox instead of the receptionist’s personal chat, then the same qualifier runs. Evening rush stops living in a notebook. Slot offer still needs calendars.
Walk-in QR is on-site capture into New enquiry so the qualifier and slot offer run on the Project, not on a staff phone.
When the only number is the owner’s, walk-ins never become CRM. QR on the gate or token counter writes the contact. Prefer WhatsApp or the web widget on the poster; SMS is MSG91 when you connect it.
QR is capture. WhatsApp session continues. Voice is unused unless they abandon the lobby.
Web or WhatsApp channel behind the QR. Same Studio agent as website-enquiry. 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. Phone is Plivo; email is SES. Wallet-only pricing: preview the Organization wallet before a blast. Organization and Project — never a personal doctor phone that vanishes when the receptionist leaves.
Patient Inquiry Qualifier (reason, service_need, location, preferred_times). Catalogs: Departments, Doctors, Beds, Services — not a chart. Emergency utterances: call emergency services. Inbox handoff. Do not mix campus QR codes across Projects.
Agents → Workflows on stage change: agent.run, route.agent, crm.set_custom_properties, crm.update_stage, crm.create_task, templated send.whatsapp/email. Not adaptive nurture.
Clock-based sequences and list blasts with wallet preview. Campaign conversion is reply rate unless you also track Appointment booked on the pipeline.
Keep a dental bot off a health-check reply. Route by stage, channel, or campaign.
One Organization, one Project. Healthcare pipeline labels. Wallet-only. Library kits are sketches — rewrite hops without SMS and without a diagnostic triage agent.
Setup → Channels (WhatsApp/Gupshup, Web, Meta, Email/SES, Phone/Plivo as needed) → Library templates → Agents → Studio (Patient Inquiry Qualifier, catalogs, appointment skill, emergency guardrail, handoff) → Router → Setup → Customers → Pipeline (five default columns) → Appointments/calendars → Agents → Workflows (stage changed: agent.run, route.agent, crm.set_custom_properties) → Growth with Organization wallet preview. Connect SMS (MSG91) under Setup → Channels when you want that hop.
Ten scans in twenty minutes. Qualifier runs. Two people book 6:30 instead of waiting. Receptionist filters New enquiry on a tablet. Personal WhatsApp is no longer the clinic.
Hospitals use department-specific QR plus router. Clinics use one QR.
Operators assemble this job on the Project. Click-path remains Setup → Channels (WhatsApp/Gupshup, Web, Meta, Email/SES, Phone/Plivo as needed) → Library templates → Agents → Studio (Patient Inquiry Qualifier, catalogs, appointment skill, emergency guardrail, handoff) → Router → Setup → Customers → Pipeline (five default columns) → Appointments/calendars → Agents → Workflows (stage changed: agent.run, route.agent, crm.set_custom_properties) → Growth with Organization wallet preview. Connect SMS (MSG91) under Setup → Channels when you want that hop. Keep the quotable definition in the brief for the team: Walk-in QR is on-site capture into New enquiry so the qualifier and slot offer run on the Project, not on a staff phone. 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, WhatsApp overlay, Clinics, 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 slot 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 Departments, Doctors, Beds, and Services catalogs — not a clinical chart. Preview the Organization wallet before a blast. Do not claim HIS or EMR replacement. The Walk-in QR playbook never forks into a WhatsApp-only or voice-only child URL. Funnel percentages on library kits are estimates, not an SLA. Autonomous success is sends, reads, or contacted — not appointment booked. If this job mentions money, the Organization wallet is the meter. That is the honest operating manual for this URL.
On-site hops. There is no nested playbook-by-channel path.
| Hop | Channel | What happens | Exit to next hop |
|---|---|---|---|
| 1 | QR → web or WhatsApp | New enquiry | Contact exists |
| 2 | Qualifier | Fields | |
| 3 | Calendars | Optional later slot | Booked or wait |
| 4 | Inbox | Desk handoff | Human |
QR, personal phones, same-day walk-ins.
QR can open the web widget instead.
Prefer WhatsApp or the web widget on the poster. SMS is MSG91 when connected.
You may keep them New enquiry or mark Consult done if they were actually seen — do not fake Appointment booked.
Yes. Non-diagnostic.
One Project per calendar cluster or tag location in the qualifier.
Merge via duplicate-patients.
Parent directory, sibling jobs, ICP, stage, channel overlay, and product surfaces.
One URL per omnichannel job.
Directory →Digital sources.
Open →Fields after the scan.
Open →Where walk-in QR earns its keep.
ICP →QR traffic lands here.
Stage →Session after the scan.
Channel overlay →How-to companion. This playbook stays the job URL.
Guide →Agent Studio, skills, knowledge, router, workflows.
Explore agents →Library templates, audiences, wallet preview.
Explore campaigns →Sends and minutes debit the Organization wallet. Creating a CRM row does not.
See pricing →Shared inbox, same qualifier, calendars if they would rather not wait.
Get started free