How to connect new patient intake chat help to a chat widget

The chat widget is the patient-facing front end – a small bubble patients click to ask questions. Behind it, a Chatref agent holds your practice's intake content (forms, insurance accepted, first-visit instructions, what to bring, FAQs). When a patient asks "What forms do I bring?" or "Do you accept my insurance?", the agent pulls the answer from that uploaded material and displays it in the widget.

You do not need to wire the two together manually. As soon as you train an agent with your intake documents and embed the widget code, the connection is automatic. The agent listens for questions and uses your practice's own information, never guessing or making up answers.

1. Sign up and create an agent
   Go to app.chatref.ai and create a new account (the first $50 of usage is free, no credit card required). Once inside, click "New agent" and name it something like "New Patient Intake". Choose healthcare as the industry so the agent understands the context.

2. Add your intake content
   Upload the documents and pages that a patient would need before a first visit. Typical sources:

   • PDFs of new-patient intake forms or welcome packets
   • A page from your website listing accepted insurance plans
   • A document with step-by-step first-visit instructions (arrive 15 minutes early, bring ID, etc.)
   • Links to your online scheduling tool or phone number You can add files (PDFs, text), paste raw text, or point Chatref at your website's relevant URLs. The agent reads everything and learns how your practice works.

3. Customize the widget
   In the agent's settings, find the "Widget" tab. You can set the chat bubble's primary color to match your clinic's brand. Optionally, add a welcome message like "Ask me anything about your first visit or our intake forms."

4. Embed the snippet on your site
   Copy the JavaScript snippet from the widget setup page. Paste it just before the closing </body> tag on every page where you want the chat to appear – usually your homepage, contact page, and any "New Patients" landing page. If your site builder uses a global footer HTML block, placing the snippet there works sitewide.

5. Allow-list your domain (if needed)
   By default, the widget works only on domains you specify. In the widget settings, add your clinic's website domain (e.g., yourclinic.com). This prevents the widget from being used on unauthorized sites.

That is it. The agent will now answer intake questions on your site, powered by your own content.

After a few minutes, a chat bubble appears at the bottom corner of your site. When a potential patient clicks it, they see a simple chat window with your custom color and welcome text. They can type questions like:

• "What forms do I need for my first appointment?"
• "Do you take Medicare?"
• "Can I schedule online?"
• "What should I bring on the day of my visit?"

The agent replies instantly with a direct answer pulled from the documents you uploaded. It might say: "Please bring your insurance card, a photo ID, and a list of current medications. Download the new-patient form here so you can fill it out before you arrive." If the question needs a human – for example, a complex insurance verification – you can turn on the handoff option so your team takes over the conversation inside Chatref's shared inbox.

Patients never wait, and the answers always reflect your actual policies because they come from your own materials.

Widget does not appear on the site

• Check that the snippet is placed just before </body>. Some site builders strip extra scripts from footers; test in an HTML block or a dedicated code injection area.
• Verify your domain is listed in the widget's allow-list. If there's a typo or missing subdomain (www vs non-www), the widget will be hidden.
• Clear your browser cache or open an incognito window to rule out stale caching.

Answers seem off or incomplete

• The agent can only answer based on what you uploaded. If it cannot answer "Do I need a referral?", check whether your content explicitly mentions referrals.
• Add a short FAQ document listing the top 10–15 new-patient questions and clear answers. This gives the agent direct examples to draw from.
• If you added website URLs, confirm those pages are live and publicly accessible. Locked or password-protected pages will not be read.

Widget is live but only shows a generic greeting and no answers

• While the agent processes new content, answers may be brief. Wait a few minutes and test again.
• Make sure the agent is toggled "Active" in its settings. An inactive agent will show the widget but not respond to questions.
• For a quick check, ask a question that appears almost verbatim in your uploaded text. If that still fails, the content may not have been fully ingested – delete the source and re-upload it.

Patients ask in a language other than English

• Chatref can answer in up to 11 languages, but it works best when your source content covers those languages. If you serve a multilingual patient base, consider uploading translated versions of your intake documents or adding a bilingual FAQ.

For more on tailoring Chatref for your practice's unique front-desk workflow, read Private Clinics.

What causes new patient intake chat problems for Private Clinics?

Most issues come from incomplete training content. If the agent hasn't seen a document about referral requirements, it won't answer that question. Outdated insurance lists, missing languages, and ambiguous phrasing in source materials also create confusion. Sometimes the widget snippet is placed incorrectly, or the domain isn't allow-listed, so patients never see the chat.

How do I improve new patient intake chat for Private Clinics?

Regularly update the agent's content as your forms, hours, or insurance policies change. Add a short FAQ document with the exact wording patients use – "Do I need a referral?" is better than a policy paragraph they have to decode. Use Chatref's Insights tab to see what patients keep asking but aren't getting good answers to, then fill those gaps. If you serve multiple languages, provide content in those languages so the agent doesn't default to generic phrasing.