Request info view

[WheresHJ]

User Story

• As a city employee, I want to see the details of a request, so that I can evaluate its urgency and utility.
• As a city employee, I want to see the contact info of a requester, so that I can contact them to verify any details of their donation and communication throughout the donation process.
• As a city employee, I want to see potential matches of this request to inbound donations, so that I can match it to the appropriate donation.
• As a city employee, I want to assign this request to myself or another city employee, so that we can manage the case in an effective and timely manner.

---

Description

This screen shows the details of an individual request. Requests are taken in by either a user-facing form, or recorded in the same form or directly in the gSheet by a city employee (for example, if a city employee hears from a donor by phone and records the details manually). Each request has the following user-facing characteristics, laid out in this gSheet:

Request details

• Date received: The date the request was made
• Status: The state of a given request, ie Inbound, Verified, Delivered, etc. Described in this gSheet
• Urgency: The urgency level of the request, in terms of how fast it needs to be acquired by a requester.
• Requester name: The name of the donor organization, or the Contact name if there is no organization listed
• Request category: The primary category of the requested item. Described in this gSheet
• Request sub-category: The secondary category of requested item. Each sub-category is subordinate to the category. Described in this gSheet
• Request location: If the requester would like the donation to be delivered, or if they can travel on-site to pick it up or consume it.
• Request details: Written free-text details of the request as entered by the requester
• Fulfilled by: Which donation was assigned to this request.
• Date fulfilled: The date on which the donation was delivered to / picked up by the requester.
• Recurrence frequency: If the request is recurring, the interval between needs.

Contact information

This information is how the city employee can connect with the requester for verification and other discussion of the request details.

• Contact name
• Organization name
• Requester type (i.e. individual / family, school, non-profit, etc)
• Email
• Phone
• Address 1
• Address 2
• City / State / ZIP

Match information

This is information on any eligible donation matches for this request recorded in the system

• Matching would occur on the sub-category level first, and then the category level
• Any active (not withdrawn, won't do, or completed) donation would be listed, in order of urgency and then by date received as a default view
• A city employee can take an action to match a given donation to a recipient. This would also change the status field to Verifying: 1st attempt, and force the donation to be assigned to a city employee (to be selected)

Assignment information

• All requests can be assigned to a City Employee to work the case. City employees can be found on the users sheet here
• Requests can also have notes listed by the city employee, recorded in the Notes field on the Requests sheet.

---

Done when:

• A city employee can view the details, contact information, and potential matches of a given request
• A city employee can easily contact the requester
• A city employee can match a donation to a request
• A city employee can assign a request to themself or another city employee