Attuned Chat
A conversation.
A clear next step.
Give patients another way to ask for help. Connect digital conversations to your approved patient access workflows and keep the handoff to your team clear.
- Patient
Hi, I'm looking for a pediatrician near me for my son. I'd prefer a female doctor, if possible.
- Chat agent
Absolutely. You can share your browser location or tell me your address, and I'll help find an office close to you.
- Patient
Location shared: Riverside.
- Chat agent
Here are two female pediatricians at our Riverside office.
Example clinicianDr. Maya Chen
Pediatrician · Riverside office
Example clinicianDr. Sofia Patel
Pediatrician · Riverside office
Would you like me to book an appointment with Dr. Chen?
Find a nearby office. See the doctors. Take the next step toward an appointment.
Scripted example. Clinicians and office are fictional. Share location uses a sample area; no browser location is requested and no appointment is booked. Tasks are configured with your team.
What this makes possible
More than a chat window.
A request with somewhere to go.
Help without a phone call
Give patients a text-based way to explain several needs.
Keep the context clear
Understand corrections and distinguish who the request is for.
Make the handoff useful
Define the next team, action and follow-up channel.
Follow the work
Make the digital front door part of the patient access strategy.
Choose a step to see how the request moves forward.
Step 1 of 3
Choose the patient need
Identify the information and patient access requests that would benefit from a text conversation.
Scope each channel
Agree the experience, integrations, language support and reporting for each surface. Public web and signed-in experiences have different requirements.
Connect the next step
Define what the channel can complete, what needs staff and how a handoff reaches the right team.
Illustrative agreed workflow. Tasks, integrations and staff responsibilities are confirmed for your organization.
Fit it to your organization
Your workflows.
Your rules.
A useful solution fits the people, protocols and systems already doing the work.
Your channels
Scope public web, signed-in web and mobile separately.
Your identity requirements
Agree authentication, permitted tasks and integrations.
Your staff handoffs
Configure escalation and reporting for each surface.
Channel availability and integrated tasks are confirmed during discovery. This illustration is not a live patient service.
See the potential dollar value
Put a dollar value
on time returned.
Use your Chat workflow volumes and net staff time to explore potential capacity value.
Questions worth asking
Get clear on the scope.
Is Chat available on every website and in every MyChart deployment?
Channel availability and integrated tasks are confirmed during discovery. Public web, signed-in web and mobile are separate scopes; this page does not imply universal deployment.
Is this the same configuration as Voice?
Voice and Chat can serve a shared patient access strategy. Each channel still needs its own configuration, integration requirements and reporting.
What happens when someone needs a person?
Staff handoff and exception paths are defined with your organization as part of the channel workflow.
Start with the outcome that matters
Make the next conversation
a better one.
Bring your patient access priorities. Explore the channel, workflow and outcomes that matter to your team.
Let's start a conversation