How to overcome objections
Objections often signal unmet needs, such as time, safety, confidence, or clarity. Keep the conversation focused on workflow and patient care, and guide them towards a safe next step.
A four-step objection-handling framework
Use this pattern to stay consistent:
Listen and label the concern (“It sounds like you’re worried about…”).
Validate without over-promising (“That’s a common concern when starting.”).
Redirect to workflow and responsibility (“The workflow includes review so you stay in control.”).
Offer a next step (“Let’s try it in a quick scenario and review together.”).
Common objections and responses (examples)
“I don't want to record in the room.”
Response: “You're in control of when recording is appropriate. Let's review your unit guidance on consent and safe use and identify moments where it feels comfortable. We'll start with one scenario and build confidence.”
“This feels awkward.”
Response: “That's normal. Care out loud is a new habit. Start with short, clear phrases you already think through - then build over time.”
“I don't trust the output.”
Response: “Treat output as a draft that reduces your documentation effort. Your review step is where accuracy is confirmed. Let's compare one example together.”
“I'm worried this will slow me down.”
Response: “Early on it can feel slower because it's new. We'll focus on consistency and small wins. Once the habit forms, it reduces end-of-shift reconstruction.”
“If I ask a question in Copilot chat, what is it using?”
Response: “In the patient view, transcript Q&A uses the transcripts from your current shift as the grounding context. If the transcript doesn't contain the answer, it might route to Information Assist, depending on your configuration.”