Once a job is allocated to a resource (job status is "Pending Dispatch"), a scheduler can dispatch the job via the job details view or from the scheduling console.
- How to Dispatch Jobs from the Job Details View
- How to Dispatch Jobs from the Scheduling Console
- Notifications Methods
How to Dispatch Jobs from the Job Details View
Once a date, time and resource have been allocated to a job, a notification can be sent to the mobile worker to inform them that they have a new job in their queue.
To send a notification either click on the "Dispatch" button (per resource) or the "Dispatch All" button at the top of the allocated resources section.
Figure 1. A job with an allocated resource pending dispatch.
Note: If there are multiple resources allocated to a job, that job's status will only update once all resources have updated their job allocation status.
For example, three resources were allocated to the same job. One has been notified, but the other two have yet to receive the job notification (the notification has not been sent). In this scenario, the job will still appear as "Pending Dispatch." Only when every resource has updated their status (i.e., both have been notified) will the job status change to "Dispatched" on the job card, in the job details, and in the job status panel.
How to Dispatch Jobs from the Scheduling Console
From the scheduling console, you can choose to notify all resources associated with a job by right-clicking on the job in the swimlanes and selecting "Notify all resources" from the context menu.
Figure 2. Notifying resources of a job from the scheduling console swimlanes.
Notifications inform the mobile user (or resource) that new jobs have been allocated to them.
There are three ways that a resource can be notified:
- Push notifications–are sent to the resource's mobile phone, if they logged into the Skedulo mobile app.
- SMS (or text messages) that sent to the resource's mobile number directly.
- A direct phone call to the resource. This is performed by the scheduler as a separate manual action away from the web app, but the result can be recorded in the web app (in the text box provided).
Figure 3. The three ways a resource can be notified: by phone, push to mobile, and SMS. The chosen method is highlighted in blue.
Figure 4. Using a phone to notify a resource.
When multiple resources allocated to a single job, they can be notified individually (using the "Dispatch" buttons) or all together (using the "Dispatch All" button).
Setting the Preferred Notification Method
Each resource should be configured with a "Preferred Notification Method." Resource preferences are defined in the resource records in the CRM. They can also be viewed and changed in the Skedulo web app, using the resource console.
If the resource has a preferred notification method set, it will automatically be selected as the notification method of the job allocation. Otherwise, you will be prompted to select the notification method to use for this job allocation.
Also, see Resource Console.
If a resource does not have their mobile phone number set (in the CRM), the scheduler will not be able to select SMS as the notification method.
The notification method can be overridden in the job allocation.
For example, Dexter has his preferred notification method set to "Push," so he will receive all his job notifications via push notifications by default. However, if Dexter does not have stable internet access to receive push notifications, as a scheduler, you may want to change his preferred notification method to SMS temporarily (click on the required icon to change it).
Mobile is not Registered
If a resource has not logged into the Skedulo mobile app, they cannot be notified via push notifications. If this is the case, a small red triangle appears above the selected method of notification–warning that registered mobile device is not reachable: "This person does not have a registered mobile device and therefore cannot receive push notifications."
Figure 5. A warning showing the mobile is not registered.