Force BIEB to notify FS in case of slot (pickup/pick-up) rejection and kicking
Description
Right now, a foodsaver is not always notified about what happens to her/his slot applys. We often see frustration about slot kicking or confusion (and therefor frustration) about what happend why and when. On the other hands, we sometime do have problems with BIEBs acting in a wrong way when kicking or rejecting slot applys.
We lack of transparency if BIEBs can kick without logging and we could be able to help BIEBs to act in a correct and fair way.
Impact
Every foodsaver and above who has applied for a pickup slot is affected. And it will help BIEBs to act correctly and BOTs to get less reports regarding slot kicking.
Proposal
Right now, a slot can have three states. Free, applied (A), and occupied (O).
If a slot is in state (A), a BIEB can click on it and gets two context menu items reading something like "approve" and "reject".
NEW If the BIEB hits "reject", a modal is oppend containing three parts:
- A descripton for the BIEB (yellow box or alike): "Dear BIEB, you are about to reject an apply. Please be aware of .... [add great guidance to the BIEB here. I am willing to provide such text of course].
- An obligatory message part: "Dear {FoodsaverName}, I, {RejecterName, RejecterID}, as one of the BIEBs in {StoreName}, have rejected your apply for the slot {SlotDate}. This is an automatically generated message."
- A free text input field wich adds the following "Please see my explanation for the rejection below: {ExplanationFromFreeTextInput}" This field is not mandatory.
The parts 2 and 3 compose a message which is automatically sent via PM from the BIEB to the FS in concern. Rejecting a slot without sending this message is not possible anymore.
If a slot is in state (O), a BIEB can click on it and gets one new context menu item reading something like "kick from slot".
NEW If the BIEB hits "kick", a modal as above is opend. The text from point 1 will be different. The text of point 2 will need a minimal adaption to say "kicked" and not "rejected".
An extra logging such as in #120 (closed) is not needed anymore as the action is logged via messages in both accounts of the kicker and the kicked. We do not have to collect more data as the two persons in charge of the current situation can discuss the matter just in time and not later in some report handling.