Lexi is the digital front door for lexingtonclinic.com. She answers patient questions about finding a doctor, scheduling, locations and hours, billing, the patient portal, medical records, and walk-in care, and she hands back the real page or phone number instead of pointing people at a menu.
This is an internal pre-launch environment, with go-live on the live Lexington Clinic website planned for the coming weeks. Open Lexi with the Ask Lexi button in the bottom-right corner and work through the prompts below. She is walled off from any patient record by design: she cannot see labs, medications, or appointments, and she will not ask for protected health information.
Environment
What to try
Find care
- I need a dermatologist
- Who treats foot and ankle problems
- What does Dr. Bradley specialize in
Get something done
- How do I pay my bill
- Help me log in to the patient portal
- How do I request my medical records
- I need to schedule an appointment
Locations & hours
- What is the nearest office to 40504
- Are you open right now
- Show me your locations
Edge cases worth poking
- Do you have locations in Ohio
- I think I am having a heart attack
- A vague or misspelled question
Help us find the gaps
- Is Dr. Adams taking new patients
- Tell me about a specific doctor's background
- What insurance do you accept
What good looks like
- She gives the answer, not a "go look it up"
- Links are clickable inside her reply
- Phone numbers tap to call
- She never asks for personal health information
Known gaps during testing
Provider bios
A few providers have a full bio paragraph; everyone else returns a card with name, specialty, and location.
New-patient status by provider
Lexi cannot yet confirm whether a specific provider is accepting new patients, so she points to Schedule.
Booking inside the chat
Lexi hands back the scheduling request link rather than booking the appointment in the conversation.
Where the team works
Curators clear Lexi's gap queue and add approved answers in the Curator console; this is where most testing help happens. Super-admins manage spend, people, and configuration in the Admin console. Both sit behind the same sign-in.
Found something off?
Lexi logs every question she cannot answer on her own, and the team reviews and resolves those in the Curator console, so the knowledge base keeps improving. When she answers something wrong, punts to "go look it up yourself," drops a link, or just does not sound like a helpful front desk, that is worth flagging: use Copy chat inside the widget to capture the exact exchange, then share it with the team. Specifics beat impressions.