Click '+Incident' from the panel in the top left of the Dispatch screen.
Right click on the map in the location you wish to create an incident.
A blue question mark will appear in that location.
Another option to a standard address is a 3 word address provided by what3words - click here to find out more about creating an incident with what3words.
An alert will appear above the incident tracker asking if you wish to create an incident at this location.
Click on the alert to proceed.
A window will appear asking for details about the incident: A summary of the incident itself, incident type, etc.
If you have the address of the incident, this is where you will enter it. If you have marked the location of the incident on the map, the location address will be automatically filled.
You will also be prompted to enter details regarding the individual(s) reporting this incident under Reporting Party. This is largely for record keeping, but is also useful for allowing Dispatch to easily contact the reporter if necessary.
All of this information will be passed on to the handset users assigned to the incident, so make sure that they have all the details they need.
The Delayed Job section is to allow jobs that need to be attended to at a certain time to made available beforehand to handset users (as opposed to responding to incidents as and when they come in). Set the time the job needs to happen at and proceed as normal.
Once this form has been filled in, select Create Incident.
Dispatch should now display the details of your new incident. From here you make changes or update the incident with notes as you see fit. To access this window at any time, simply click on the corresponding incident in the left hand column.
The 'Times' section at the bottom of this window lists the metrics for your users (response times, time spent in custom states, time before incident resolution, etc). This is an addon for Dispatch which is not available under the standard subscription which you can learn more about here.
See also: Incident Allocation Tracking.
You should now be able to see your incident on the map view marked by a red warning triangle.
For whatever reason, should you need to change the position of the incident location, you can click/tap and drag the incident marker to wherever you need it to be.
Alternatively, you can change the incident location by opening the incident details window and clicking 'Edit' in the Location section. From here you can update either the normal address, or the what3words address.
When you're done, click 'Update Incident'.
We'll need to assign this incident to a handset user to resolve the situation, so select the assign user button on the incident tracker panel on the left of Dispatch.
A window will appear offering several different ways to assign your new incident.
To assign an incident to a specific user, look in the Individual User and Queue User sections:
To notify groups of people to an incident, look in the All users on Channel and All users on Callsign sections:
The selected handset(s) will now alert their users to the incoming incident. Users have the option to accept or reject the incident. Accepting sets the user to 'Deployed' while rejecting sets the user to 'Busy' to inform Dispatch of their current situation.
You will now be able to easily identify in the incident tracker the username and callsign of the person who has accepted the incident. This will also be available in the incident details screen.
For more information on how to read the incident tracker, see our help article on Incident Allocation Tracking.