A patient asks an AI assistant for the casualty number of a hospital and receives a number that belongs to a different department, or to a hospital that closed. Another is told that a surgeon works at a branch where they no longer practise. These errors are not rare curiosities. For a hospital, a wrong phone number or address is a service failure and sometimes a patient-safety one.
This article is for hospital marketing and digital teams, and for the operations leaders who own contact information. It sets out a process: detect the error, document it, classify its cause, fix the source, report it to the platform and check that it stays fixed. We describe a method, not a guarantee. No hospital can force an AI system to change an answer, and the platforms say so in their own feedback tools. What you can do is remove the wrong evidence and add clear right evidence.
Why the errors happen
Assistants assemble answers from retrieved pages, stored knowledge and patterns learned in training. Wrong contact details typically come from one of five causes:
- Stale sources. An old directory listing, press release or PDF with a former number.
- Conflicting sources. Your site, your Google Business Profile and a directory give three different numbers, and the system picks one or blends them.
- Entity confusion. Two hospitals with similar names, or two branches in one city, are merged.
- Missing sources. There is no accessible page for the fact, so the system guesses from nearby text.
- Model invention. The system fabricates a plausible-looking value. This is the hardest to fix, because there is no wrong source to correct.
Knowing which cause you face decides the fix.
Step 1: Detect
Make detection routine, not reactive. Build a small "facts audit" prompt set of twenty to forty prompts covering every fact a patient depends on:
- Main number, casualty or emergency number, appointment number and WhatsApp number.
- Address, landmarks and parking for each branch.
- Visiting hours, OPD timings and 24-hour services.
- Doctors by name and specialty, and the branch they practise at.
- Services offered and not offered.
- Insurance and cashless panels.
- Website and appointment link.
Run them monthly on the assistants your patients use, three times each, in a fresh session. Also add detection sources that cost nothing: front-desk and call-centre staff who hear "the internet told me" complaints, social media mentions and Google Business Profile questions. Give staff a simple internal form for reporting a wrong detail with a screenshot.
Step 2: Document
For every error, create a record in a shared log. Capture the following.
| Field | Why it matters |
|---|---|
| Date, time and surface | Answers change; you need a timestamp |
| Exact prompt | Reproducibility |
| Full answer text and screenshot | Evidence for platform reports |
| Wrong fact and correct fact | Clarity |
| Cited sources, if any | Points to the source of the error |
| Severity | Drives urgency |
| Owner and status | Accountability |
Set severity with clinical and operations leaders. A wrong emergency or casualty number, or a wrong location for a time-critical service, is the highest level and should be escalated the same day. A wrong consultation fee or an outdated doctor is medium. A slightly off description is low.
Never copy patient details into the log. If a user-reported error includes patient information, remove it before logging.
Step 3: Classify the cause
Use the cited sources, if any, to decide.
- A cited page has the wrong fact. Fix that page or ask its owner to.
- Cited pages disagree. Reconcile your own sources first.
- No sources are cited and the fact is wrong. Likely invention or a stale memory. Add correct sources and report it to the platform.
- The answer confuses you with another entity. Disambiguate your own entity pages, and link to official profiles.
Where an assistant shows no citations, run the same prompt with search enabled, which often reveals the page it is leaning on.
Step 4: Fix the source of truth
Treat one internal record as the master for each fact, and push it everywhere else.
- One owner, one file. Operations holds a verified record of numbers, addresses, timings, doctor rosters and services. Marketing publishes from it.
- Your website first. Put the facts in HTML on a contact or locations page, in text, not images. Give each branch its own page with its own number and address. Use
telephone,addressandopeningHoursSpecificationin structured data that matches the visible text. Our schema markup service and healthcare schema guide explain the types to use, and the glossary entry on NAP consistency covers why identical name, address and phone details matter. - Google Business Profile. Update each profile and check for suggested edits that others have submitted. Our Google Business Profile guide covers verification and management.
- Directories and aggregators. List every place the hospital appears: health directories, insurer panels, map and navigation apps, government listings and old press pages. Submit corrections, keep a tracker of requests and follow up. Our reputation SEO service handles this at scale.
- Doctor profiles. Keep each doctor's page, branch and specialty current. When a doctor leaves, redirect or update the page and the directory entries promptly, and publish an accurate note instead of leaving the old one live.
- Old documents. Remove or update stale PDFs, brochures and press releases that carry old numbers. If you cannot delete them, replace them with updated versions at the same URL.
Disambiguation matters if you share a name with another hospital: include city, branch and legal name consistently in titles, headers and structured data, and link to official profiles from your pages.




