Use shifts to allocate roles and responsibility - i.e allocate an alias
All the specification of a role/responsibility for each shift that can then be use to identify or @ a user.
For example lets say I assigned an on-call shift '8pm-8am as 1st floor on-call' then I gain the alias @first-floor-on-call for the duration of the shift so someone can @GeorgeHarvey or @first-floor-on-call, both will come to me, except when my shift ends @first-floor-on-call is then forwarded to the next user, and they can see any outstanding tasks/messages due for @first-floor-on-call
Thanks for the feedback. My name is Amir and I am a product manager in the Shifts team. Can you please explain a bit more about this scenario? I am trying to understand what is applicable for the Shifts app vs. general group/1:1/channel chat. Thank you!
You are receiving this email because you agreed to be contacted by Microsoft about your product feedback
Microsoft Corporation, One Microsoft Way, Redmond, WA 98052 USA
Dr George Harvey commented
Dr George Harvey commented
So currently the Shifts app is useful for rota'ing and viewing shift patterns, but does little to aid communication.
Most shift work includes two things not true of non-shift work 1) Unsociable hours and 2) Hand-over of responsibilities. These create an opportunity for the Shift App.
Imagine a scenario in Healthcare (my industry). In a hypothetical hospital here are two shifts 8am to 8pm (day-shift) and 8pm (night-shift) titled 'Wards A, B and C on-call doctor'. Lets say Alice is the day shift doctor and Bob is the night shift doctor.
As it currently stands:
Lets say various the nursing teams are on Teams and they can all message @Alice to ask for advice/help with their patients. However let's assume Alice is very busy and does have time to complete all the tasks or see the messages sent to her. Come 8pm she hands-over to Bob (and may forget or miss out some tasks). Alice heads home. However, she continues to receive messages from nurses by mistake and so has to forward them to Bob, or deal with them. Similarly she receives messages from Bob asking for clarification on events from the day. This is disruptive to her life and to her nursing colleagues.
How it should be:
There is an alias Teams user (or Tag) associated with the shift Wards A, B and C on-call doctor. Let's call it @ABCdoctor. Via the Shifts app, Teams forwards any messages sent to @ABCdoctor to @Alice between the hours of 8am and 8pm. Then come 8pm Teams starts forwarding messages sent to @ABCdoctor to @Bob, and ideally Bob can see all messages go back and see messages sent to @ABCdoctor during the day and any tasks assigned to them. This means nurses only have to remember one user, and responsibility are handed over.
A currently possible workaround would be to have a channel for *every* role that includes everyone who would want to contact that role and everyone who performs that role. This would be a messy solution.
One line summary: create a Microsoft Teams Tag (or alias) for each role or responsibility that can be moved between users automatically according to shift assignments.
On a similar track, the number one feature that would be useful for our operation would be the ability to tag staff in a channel post from a particular shifts group that are working (even better on a particular day). I'm finding it hard to keep my staff from disabling notifications as they get notifications for channel messages when they are not working or are not involved.
The ability to focus notifications via tags on only those staff that are working and in a particular group of workers would be extremely valuable.
Ok, we have similar use case.
Every shift might be assigned a “head nurse” role or a “team leader” role. One might want to tag the team leader or ‘head nurse’ even though they don’t know which individual is covering that role.
Retail has the concept of an MOD (manager on duty) that is typically the manager in charge for a shift.
Hospitals and clinics have similar roles.
Now this would be a LOT easier if ***** allowed us to assign the ROLES first (including an alias, for example) and THEN assign people to the role.
If you’re wondering how that would work then check out competitive products like wheniwork or deputy.