Within Tripshot you have the ability to create custom incidents to track areas of concern. These incidents are fully customizable and can be set to require followup and/or if they are SLA monitored. Additionally, you can create incidents that allow riders to give feedback through the app and the incident can automatically be assigned to any user account and/or email address.
To create incidents navigate to Tripshot Admin > Incidents > Incident Types
To create a new incident, click "Add Incident Type". Then fill in the blank fields:
Incident Type: This field will denote what the incident is.
Incident Type Group: This field allows you to group various incidents together and will provide a drop down choice of the incidents in this group.
Description: This field allows you to briefly describe the incident.
Requires Followup: If this field is checked, the incident will stay in a open state until it set to a closed state.
SLA Monitored: This field is to keep track of all incidents that are tied to Service Level Agreements (SLA).
Feedback: Checking this field will open the incident up to riders to provide feedback via the rider application.
Default Assignee: If this field is filled in, Tripshot will automatically assign the incident to the respective user. The user account must have an email associated with it to receive email notifications.
Watcher Emails: A watcher email gives you the ability to input a specific email address and not a user.
After filling in all of the fields, click "save".
Incident Type Groups
To create incident type groups navigate to Tripshot Admin > Incidents > Incident Type Groups and click "Add Incident Type Group". Next you will want to create a name for the Incident Type and click "Save".
Recurring Incidents Manager
To create Recurring Incidents navigate to Tripshot Admin > Incidents > Recurring Incidents Manager and click "Create Recurring Incident". Next you will want to fill in the fields.
Type Group: Select all or the incident group that you previously created.
Type: Select the incident type.
Starts On: Enter the date that the recurring incident will begin.
Recurs Every: How often this incident recurs.
Ends: When the recurring incident will end.
Vehicle: Vehicle name.
Driver: Drivers Name.
Assignee: Who the incident will be assigned to.
Due Date Delay: Date the incident is due to be closed.
Description: Brief description related to the recurring incident.
Click "Save" When done.