Enhanced Communication Triggers for Unassigned Jobs in Scheduler
Objective:
To improve the user experience by preventing reminder emails or communication triggers for unassigned jobs in the scheduler, as these are not confirmed bookings.
Description:
Users have expressed the need to exempt unassigned jobs in the scheduler from reminder emails or communication triggers.
These jobs are not confirmed bookings and are simply waiting for assignments.
The current system does not differentiate between assigned and unassigned jobs when sending out communications, which can lead to unnecessary emails being sent out for unconfirmed jobs.
Proposed Solution:
Implement additional conditions in the communication settings to enable communication triggers only once the job has been assigned.
This will prevent unassigned jobs from triggering reminder emails or other communications, ensuring that only relevant and necessary communications are sent out.
Utilise the existing Customer confirmed toggle to trigger communication once job is confirmed.
Benefits:
Improved user experience by preventing unnecessary communications for unassigned jobs.
Enhanced communication settings that allow for more control over when communications are triggered.
Increased efficiency by reducing the number of unnecessary emails sent out.
Original request:
Can we request that the current use of the unassigned section of the schedular be exempt from any reminder emails/triggers as these are not confirmed jobs, just sitting and waiting for bookings. We can't use the trigger section yet because we have jobs sitting unassigned that we move around.
Log in to comment and vote
Comments4
nathanc
Sep 2
I second this idea.
Create an additional Trigger on CLIENT CONFIRMED.
This would make sense when all other triggers are not suitable and would allow a user to manually fire off a notification.
Keith Azzopardi
Jul 16, 2024
Hi @Paul Humberstone
I am inserting this other request here as they are similar:
Additional Automated Communication Trigger(s)
The issues:
1. Recurring jobs that use the ‘Job Created’ trigger notify the client of the details of the job upon creation, despite the job details not necessarily being finalised, correct, or confirmed with the client. If the job schedule is then changed, the client receives a notification each time. This can be especially problematic when scheduling multiple jobs at a single location, over multiple days and then needing to change the schedule for various reasons.
2. Recurring jobs that use the ‘Job Assigned’ trigger, notify the client of the details of the job upon assigning it to a technician, despite the job details not necessarily being finalised, correct, or confirmed with the client. If the job schedule or technician are then changed, the client receives a notification each time.
3. For companies whose staff are predominately employees, the ‘Job Accepted’ trigger is not applicable.
Possible solution:
I note that the ‘Client Not Confirmed’ and ‘Client Confirmed’ statuses are currently a visual aid only.
An additional Automated Communication Trigger that enables communication only to be sent once a specific flag within the job has been checked e.g. Job Confirmed, giving us a lot more granular control over when and to who notifications are sent.
This would also enable us to uncheck the flag, move the job around on the scheduler and then when the schedule is correct, check the flag again to notify the client of any changes.
To add additional functionality, a job or jobs could be selected in the scheduler and the flag quickly toggled on and off. This functionality could also be available on the ‘Active Jobs’ and ‘Recurring Jobs’ pages.
Paul Humberstone
Nov 22, 2023
This is also relevant to Rodent Station checks and regular commercial bookings.
Paul Humberstone
Nov 22, 2023
The perfect option that also seemed the most logical, would be to be able to use the existing ‘Client Not Confirmed’ and ‘Client Confirmed’ status flags as a trigger. Automated communication would only be sent to clients that are confirmed.
To add some further context to this, we schedule regular Termite Station Baiting checks (jobs) at intervals ranging from 4 weeks to 12 weeks, depending on a number of factors such as station type and activity.
Most of these jobs are created using a recurring profile, that doesn't necessarily mean that they will be carried out on the date or time that they are created or even by the assigned user, they are created to ensure that they are included on the schedule and not missed.
Once the customer has be contacted to ensure that the date/time is suitable or that the users other jobs for that date fit in with the rest of the of the schedule e.g. the job it isn't located an unreasonable distance from the users other jobs, the job would be confirmed and the client notified.
Currently we are unable to use automated communication with these types of jobs, which are actually our largest number of jobs, as the current automated communication options are not flexible enough and we have had numerous customer complaints as jobs were moved around to suit the schedule.