Mission feedback

From VPOIDS Documentation

Mission Feedback

This process captures feedback from passengers and requesters after their missions via a survey form.

Batch process to send the emails

There are two batch processes, one which sends emails to passengers, and one to requesters.

Passengers

  • Process id: requester_feedback
  • Stored procedure: bp_passenger_feedback
  • XSL template: passengerFeedback.xsl

The logic in the stored procedure that selects the recipients is:

  • exclude camp passengers
  • Only mission type 1 passengers are included
  • the mission date is within the range specified in the batch process. The period is specified as the number of day prior to today, so the period might be from 34 days prior to todaty until 21 days prior to today (this is the default). The delay is designed to give passengers a chance to get settled back home.
  • the passenger has not provided feedback within the past 180 days
  • The passenger has not been contacted by phone or email by staff with a resulting status of "Declined" or "Disconnected"
  • Email is not null or empty

The template can be customized with language specific to the organization.

Requesters

  • Process id: passenger_feedback
  • Stored procedure: bp_requester_feedback
  • XSL template: requesterFeedback.xsl

The logic in the stored procedure that selects the recipients is:

  • Exclude camp flights
  • Only mission type 1 passengers are included
  • The mission date is within the range specified in the batch process. The period is specified as the number of day prior to today, so the period might be from 34 days prior to today until 21 days prior to today (this is the default). The delay is designed to give requester a chance to get feedback from passengers.
  • The requester has not provided feedback within the past 180 days
  • The requester has not been contacted by phone or email by staff with a resulting status of "Declined" or "Disconnected"
  • Email is not null or empty

The template can be customized with language specific to the organization.

Survey form

The survey form is accessed via the url: http://xxx.xxx.com/mission_feedback/feedback

The script expects a mission id (mid), and a token. In addition, it expects a passenger id (pid) or a requester id (rid) depending on whether the recipient is a passenger or requester. The purpose of the token is to connect the survey with the email link when went to the passenger, and also to prevent spam.

The questions are determined by the form. In other words, the save process captures whatever questions are in the form using the question field and the response. Each question/response is stored as a separate record in the mission_feedback table. These questions are saved as numeric responses. The form determines the scale, e.g. 1-5 as well as the text of the question, which is captured along with the response. This also allows for questions to be specific to the passenger versus the requester (the form script and link are the same for both).

Two additional fields, comments and problems, are saved as text responses.

One possible question on the form is, "Are you ready to schedule your next flight". If the response to this question is yes, then an email specified in system emails a "PassengerNextMission" is sent. This alerts staff so they can follow up promptly.

Notification emails to staff

Another batch process sends a weekly email to staff with a report of the previous week's feedback.

  • Process id: report_mission_feedback
  • Stored proc: bp_mission_feedback_detail
  • Template: missionFeedback.xsl

Status

AFW

  • Status: Done
  • Passenger emails: Saturday Morning
  • Requester emails: Wed Morning
  • Report to staff: Wed Morning

AFE

  • Status: Requested
  • Passenger emails: Saturday Morning
  • Requester emails: Wed Morning
  • Report to staff: Wed Morning

AFSC