Settings and activity
648 results found
-
3 votes
Jeremy Shieh supported this idea ·
-
8 votes
Jeremy Shieh supported this idea ·
-
4 votes
Jeremy Shieh supported this idea ·
-
7 votes
An error occurred while saving the comment Jeremy Shieh supported this idea ·
-
2 votes
Jeremy Shieh supported this idea ·
-
5 votes
Jeremy Shieh supported this idea ·
-
6 votes
Jeremy Shieh supported this idea ·
-
10 votes
Jeremy Shieh supported this idea ·
-
13 votes
Jeremy Shieh supported this idea ·
-
29 votes
Jeremy Shieh supported this idea ·
-
2 votes
Jeremy Shieh supported this idea ·
-
5 votes
Jeremy Shieh supported this idea ·
-
2 votes
Jeremy Shieh supported this idea ·
-
8 votes
Jeremy Shieh supported this idea ·
-
3 votes
Jeremy Shieh supported this idea ·
-
6 votes
Jeremy Shieh supported this idea ·
-
14 votes
Jeremy Shieh supported this idea ·
-
55 votes
An error occurred while saving the comment Jeremy Shieh commented
I definitely see the advantage of this for appointments that potentially require:
Forms/chart completion
Consultation requirement
Product purchase, or package purchase
Staff resource availability checkup
Payment procedure requirement(s)For these otherwise complicated appointments, there would be multiple reasons how this could benefit both clients and businesses. I imagine in the same way checkout is a "flow" to get clients through it with understanding they are moving through steps to checkout, that there is a similar flow to these special appointments:
Choose services, date, provider < payment collection/deposit < forms/acknowledgements/waivers < data collection on client history related to appt < consultation if necessary and date/time assignment < intended service date/time approval < appt < checkout flow
-
5 votes
Jeremy Shieh supported this idea ·
-
12 votes
Jeremy Shieh supported this idea ·
Often staff will put blocks for legitimate reasons, but sometimes not so. Not that it really solves the problem, but requiring a reason for a block would at least provide a small barrier to missuse.