Sometimes you know what you've just built has a problem and you still have to decide to release it.
Coming up with a viable workaround should be a part of that decision. You absolutely need one, especially if you know the fix will take some time. But what I want to know is whether you have a plan for how you'll help people overcome the problem today.
Let's say patients can't complete an online booking with a keyboard and someone suggests that they can call instead.
That can work. With some caveats. Your known fix for your known issue is only viable if the patient can easily find the phone number, use it and get comparable help in time. If so, calling may help for now.
Just be aware that you haven't avoided the work. You've shifted the workload to other people. The patient has to make a call they didn't plan to make and reception has to handle that call. We have to account for both when we decide to release. If we rely on that option, let's check it works, tell reception what to expect and agree who will fix the booking flow and by when.
I don't want to hold up a release while the team fixes the known issue with the online flow. People need care now. I also don't want "patients can call" to become the end of the discussion.
A workaround can help someone today, but it doesn't mean the feature is done.