A dental site should put the chat box on the emergency page, the new patient page, and the contact page, open it with a 911 line and a request for a callback number, and make sure the chat vendor has a business associate agreement. A GoHighLevel chat widget can collect contact details and start a callback task. The bottom line: visitors at night are often in pain, so the first message must help them decide where to go, and the box must not invite them to type their symptoms.
Who is on the site at night
Dental guides describe the late night visitor as someone with severe pain, swelling, or a damaged tooth deciding between an emergency room and waiting for the office to open. They say swelling toward the throat, difficulty breathing or swallowing, or uncontrolled bleeding means the emergency room, and that a knocked out tooth is time critical, with the best chance of reimplantation within about 30 minutes. A chat box that answers with a callback form wastes that time, so the first lines should send the visitor to the right place.
What the tracking rulings mean
In American Hospital Association v. Becerra, decided June 20, 2024, a federal court in Texas vacated the part of OCR's online tracking technologies bulletin that treated an IP address plus a visit to an unauthenticated public page as protected health information, and OCR withdrew its appeal in August 2024. Law firm summaries note that guidance on authenticated pages and other combinations was not vacated, and they advise business associate agreements with vendors that have access to protected health information. A chat box differs from a tracking pixel because visitors type into it. If a visitor types a symptom, the chat vendor has received health information.
| Page | Why | First message |
|---|---|---|
| Dental emergency page | Visitors in pain land here | 911 line, emergency number, then ask for a callback number |
| New patient page | Booking intent | Offer to book, and ask for a name and number |
| Contact page | Ready to reach out | Ask for a name and number |
| Patient portal or login | Not appropriate | No chat box |
Build it in GoHighLevel
A third party guide describes GoHighLevel's chat widget as a box that collects contact details so the business can reply by text or email. Confirm in your account whether it is covered by the HIPAA add on and your agreements.
GoHighLevel's help portal says accounts are not HIPAA compliant by default, and that HIPAA Compliance is a paid upgrade, $297 a month as an account wide add on, that must be enabled for the agency and then configured for the sub accounts that need it. Third party guides add that the add on provides a business associate agreement, encryption, audit logging, and multi factor authentication, that the practice also needs its own agreement with the agency, and that GoHighLevel itself recommends avoiding protected health information in SMS and email even with the add on. Whether the AI features are covered by the agreement is a question to put to HighLevel in writing before any patient data reaches them.
- Confirm in writing with HighLevel that the chat widget is covered, before any visitor can type health information.
- Create the widget with the first message from the table, and a line telling visitors not to type medical details.
- Add a consent line for texts, tied to your A2P opt in language.
- Place the script on the pages in the table, and leave it off login pages.
- Build a workflow that starts on submission, texts a generic confirmation, and creates a callback task due at opening time.
- Add an after hours branch: if the visitor selects Emergency, show the on call number and alert the on call dentist.
- Review transcripts weekly for typed health details.
Worked example
For example, if the emergency page gets 200 visits a month and 5 percent start a chat, that is 10 chats (200 times 0.05). If 6 leave a number, the practice has 6 callbacks at opening time from visitors who might have gone to another office.
Mistakes to avoid
- No 911 line. Visitors may have a medical emergency.
- No vendor agreement. Typed symptoms are health information.
- An after hours chat nobody reads. Create the morning task.
- Putting the box in the patient portal. Authenticated pages carry more risk.
How this was handled before
Dental websites offered a phone number and a contact form. Visitors in pain at night called a number that rang to voicemail. A chat box with a clear emergency message gives them a next step, and the privacy rules decide how much it may collect.
What to measure after launch
Track chats started by page, numbers captured, after hours callbacks made at opening, and chats with typed health details. If visitors keep typing symptoms, change the first message.
Check before you switch it on
US text messages sent from a standard 10 digit number need A2P 10DLC registration. The HighLevel support portal says registration is required for texts to US recipients from 10 digit long code numbers and that toll free numbers do not require it. HighLevel's opt in guidelines also say a person cannot be forced to agree to text messages in order to submit a form, so keep the consent box optional. One compliance guide separates informational texts, which need documented consent, from marketing texts, which need prior express written consent. Ask your attorney which category your reminders fall into. Have counsel review the chat, scripts, and vendor agreements under HIPAA and your state's privacy laws. This is general information, not legal advice.
Questions people ask
Did a court end OCR's tracking guidance?
It vacated only the part on unauthenticated public pages, and OCR withdrew its appeal. Other guidance and other laws remain.
What should the first chat message say?
A 911 line for breathing or swallowing trouble and heavy bleeding, the emergency number, and a request for a callback number.
Does the chat vendor need an agreement?
If it has access to protected health information, summaries advise a business associate agreement.
Ready to try it yourself? Start a GoHighLevel account here.
You can also see this in action in our GoHighLevel capabilities demo.
