Skip to main content
The Web View channel gives you a browser-based chat interface that you can embed directly on your hospital or clinic website. Patients who visit your site can start a conversation, ask questions, and book appointments through the same conversational workflows that power your WhatsApp channel — without leaving the page. Leads captured through Web View are automatically attributed to the web source and appear in your Transactions Console alongside all other channel-originated records.

​
How Web View Works

When a patient opens the embedded chat widget on your website, Neuroncx AI initiates a session and routes the conversation through the appropriate workflow based on the patient’s intent. The experience mirrors the WhatsApp booking flow in structure: the patient selects a location, chooses a consultant, picks an available slot, and receives a confirmation — all within the chat interface. Because Web View shares the same underlying automation engine as WhatsApp, any workflow or template change you make in your Ontology configuration applies to both channels simultaneously, unless you have configured channel-specific overrides.

​
Setting Up the Web View Widget

1

Enable the Web View Channel

Go to Channels → Settings → Web View and toggle the channel to active. Confirm your domain allowlist — only requests from listed domains will be able to initialise a Web View session.
2

Copy the Embed Snippet

Once the channel is active, Neuroncx AI generates a JavaScript embed snippet unique to your account. Copy this snippet from the Settings page.
3

Add the Snippet to Your Website

Paste the embed snippet into the <head> or just before the closing </body> tag of each page where you want the chat widget to appear. For most teams, this is the homepage, the appointments page, and the contact page.
4

Verify the Widget Loads

Open the pages where you added the snippet in a browser and confirm that the chat widget appears and initiates a session correctly. Check the Transactions Console for a test lead to confirm end-to-end connectivity.
If the widget does not load after you add the snippet, verify that your website’s Content Security Policy (CSP) allows scripts and connections from the Neuroncx AI domain. CSP restrictions are the most common cause of embed failures.

​
What Web View Patients Experience

The Web View conversation flow is designed to be low-friction and familiar to anyone who has used a web chat widget before.

Appointment Booking

Patients can book an appointment end-to-end within the chat widget — selecting location, consultant, and slot without switching to a separate booking portal.

General Queries

Patients can ask questions about services, opening hours, or specialist availability. The LLM-backed assistant handles common queries using your configured knowledge base.

Rescheduling and Cancellation

Existing patients can reschedule or cancel bookings directly through the widget. The Transactions Console is updated automatically when a modification is confirmed.

Lead Capture

For patients who do not complete a booking, the Web View channel captures their contact details and intent signal as a new lead, ready for agent follow-up.

​
Lead Attribution and Source Tracking

Every lead created through a Web View session is tagged with the Web View source attribute. This attribution flows through to the Patient Source Attribution panel in the Channels Overview dashboard, where you can compare Web View conversion rates against WhatsApp, imports, and other channel sources.
If your website has multiple landing pages targeting different patient segments — for example, a cardiology page and a general practice page — consider using URL-based source parameters to distinguish between them in your attribution data. Contact your Neuroncx AI account team to configure sub-source tagging for Web View.

​
Monitoring Web View Performance

Web View conversion data appears in the Channels Overview dashboard alongside all other channel metrics. Track the following signals to understand how your embedded chat is performing:
  • Booking Channel Performance — Web View-originated bookings are counted in the Completed, Success, Cancelled, Modified, and Failed totals.
  • Patient Source Attribution — Shows how Web View leads progress through the funnel compared to other sources.
  • Topical Usage — Displays the most common intents triggered through Web View sessions, helping you identify gaps in your conversational coverage.
Web View sessions that end without a booking or a captured lead still contribute to your topical usage data. Reviewing these sessions helps you understand what patients are asking about that your current workflows do not yet address.