Difference between revisions of "Responses"
| Line 2: | Line 2: | ||
<div class="noautonum">__TOC__</div> | <div class="noautonum">__TOC__</div> | ||
==Overview== | ==Overview== | ||
| − | Mission Manager can collect status Responses from individual team members for various uses, the most common being mission status for a callout. Responses are independent of a mission and can be done whenever a member chooses to update their status. The four different responses are:<br> | + | Mission Manager can collect status Responses from individual team members for various uses, the most common being mission status for a callout. Responses are independent of a mission and can be done whenever a member chooses to update their status. |
| + | |||
| + | [[File:Responses.PNG |800x400px]] | ||
| + | |||
| + | The four different responses are:<br> | ||
# '''Attending''' - Team member is indicating they are responding to an incident NOW, or within a reasonable period of time as defined by their team.<br> | # '''Attending''' - Team member is indicating they are responding to an incident NOW, or within a reasonable period of time as defined by their team.<br> | ||
# '''Not Attending''' - Team member cannot respond right now or within a short delay as defined by their team.<br> | # '''Not Attending''' - Team member cannot respond right now or within a short delay as defined by their team.<br> | ||
| Line 19: | Line 23: | ||
When the “Request Response” button is pressed, the selected group of users from the left side of the Messages page will be sent a unique SMS text message with an embedded link in the message that, when clicked, will connect the receiving party to a “Mini Response” web page asking for their callout status. | When the “Request Response” button is pressed, the selected group of users from the left side of the Messages page will be sent a unique SMS text message with an embedded link in the message that, when clicked, will connect the receiving party to a “Mini Response” web page asking for their callout status. | ||
| + | |||
| + | [[File:Mini_response_page.png |800x400px]] | ||
Select one of the four choices “Attending”, “Not Attending”, “Maybe Attending” or “On Scene”, and optionally include a 100 character message in the “Notes” field. This message and the response status will be transferred to the “Responses” area under the “Messages” tab. | Select one of the four choices “Attending”, “Not Attending”, “Maybe Attending” or “On Scene”, and optionally include a 100 character message in the “Notes” field. This message and the response status will be transferred to the “Responses” area under the “Messages” tab. | ||
Revision as of 03:58, 23 October 2016
Overview
Mission Manager can collect status Responses from individual team members for various uses, the most common being mission status for a callout. Responses are independent of a mission and can be done whenever a member chooses to update their status.
The four different responses are:
- Attending - Team member is indicating they are responding to an incident NOW, or within a reasonable period of time as defined by their team.
- Not Attending - Team member cannot respond right now or within a short delay as defined by their team.
- Maybe Attending - Team member is not certain yet as to whether they can participate of not. They may need to arrange for child care, or wait to get off work. The 'Maybe' category is useful in that most teams desire a status Response within 10-15 minutes of an initial call. Without the Maybe choice, your team member may withhold their Response until they are certain of their status which may cause their command to unnecessarily contact that member.
- Onscene - Team member can indicate that they have arrived Onscene.
There are three main ways to indicate a Response.
- Clicking on a link within a text message sent from Mission Manager to individual members. That process is initiated by the Request Response button on the Messages tab.
- Manually change a dropdown box on the Responses area of the Messages tab (for those members that have Responses permission).
- By a member sending a properly addressed email into Mission Manager indicating their Response.
Members can enter a short note or explanation with each of the three Response methods.
Responses are viewed by pushing the Responses button on the Messages tab. Members must be system administrators or have the Messaging - Responses login permission to have access to the Responses feature.
Request Response Button Method
When the “Request Response” button is pressed, the selected group of users from the left side of the Messages page will be sent a unique SMS text message with an embedded link in the message that, when clicked, will connect the receiving party to a “Mini Response” web page asking for their callout status.
Select one of the four choices “Attending”, “Not Attending”, “Maybe Attending” or “On Scene”, and optionally include a 100 character message in the “Notes” field. This message and the response status will be transferred to the “Responses” area under the “Messages” tab.
Depending on your smartphone screen size, you may have to pinch zoom into the Mini Response page. After your response is submitted you may have to adjust your screen resolution outwards to be able to see the ‘success’ message.
Important Note: When you use the ‘Request Response’ Button, any text that has been input previously in the “Message field” in MM is not included in this unique “Request Response” message.
The link format that MM sends is pre-configured and cannot be changed. The link will look different depending on your phone type and carrier, but will be similar to:
Update Response Status @ http://www.missionmanager.net/R.php?id=NNNNNN
Do not reply to the MMFRXXXX_YYYYT@missionmanager.net message address. If you do, the “Request Response” will not be sent back to MM.
Website Method
Members who have access to the Responses screen can log enter their responses directly on the screen itself without the need to send a message. Filters are available on the right side of the screen to if it is necessary to view responses from only certain individuals quickly. The total current responses in each category are available at the bottom of the screen.
- Subject and Messages together can be no longer than 256 characters.
- Email prefixes can only contain the characters, 0-9, A-Z, _, or -.
- Only emails from member email or text message address will be accepted for this feature.
- Emails cannot be forwarded from the same email address used in the Return email address set in the Configuration.
- Message responses can be delayed up to 5 minutes using this method.
Email Method
The following is a sample of how you might set up these forwarding addresses in the Configuration (replace myteam below with the name of your team):
- Responding Email Prefix for Attending: yes.myteam
- Responding Email Prefix for Not Attending: no.myteam
- Responding Email Prefix for Maybe Attending: maybe.myteam
- Responding Email Prefix for On Scene: onscene.myteam
For your members to indicate they are responding or not they must create a new text or email message and send it to the following addresses (replace myteam below with the name of your team):
- yes.myteam@missionmanager.net - if attending
- no.myteam@missionmanager.net - if not attending
- maybe.myteam@missionmanager.net - if maybe attending
- onscene.myteam@missionmanager.net- if they are on scene
The following image is a sample of the Responses screen and shows how depending on what email address the message is sent to will depend on how their response is recorded. The text sent in the message will appear in the Message section of this screen:
