The Double-Booking Conflict warning message displays if a job is being created that matches an existing job. The items creating a potential conflict are listed in the first sentence of the warning (e.g. matching consumer, customer, client, location, etc.). Note: For Face-to-Face jobs only, if the agency is not using the Consumer field, the conflict warning can still invoke if the newly-created job matches customer, client, location, language, start date/time.
The user has the option of clicking on View Potential Conflict which opens a new tab displaying the existing job (potential conflict), clicking Continue and ignoring the warning, or clicking Cancel to start over with job creation.
Double-booking Conflict Warning is invoked
The Consumer field is enabled and the consumer is double-booked on jobs with any service type.
Face to Face or In Person Jobs: Matching customer, client, location, sublocation, language, start date/time. Note that a booking at same location with same language does not trigger the warning if the sublocation is enabled and is different.
Examples of when the Double-Booking Conflict Warning is not invoked
- Individual service locations have their own ID in the database. If there is more than one service location that contains identical information, these are not seen as the same location by the database. The double-booking warning will not be triggered in this case. For example, these two addresses are seen as different service locations:
- Remote jobs with the same customer, client, language, start date/time if the jobs do not have consumers listed (Consumer Enable flag disabled on the customer's configurations).
- If there is an existing set of recurring jobs and the user creates a standalone job separate from the recurring series that does not conflict for a different start date using the same customer, location, language and consumer. Then the user creates a set of recurring jobs from this standalone job where one of those jobs matches one of the jobs in the existing recurring series. No double-booking conflict warning displays.
- If a job is created and saved that does not trigger the double-booking conflict, then the job is edited to the same date, time, location, consumer, etc., the warning is not invoked.
- If the consumer has more than one consumer profile in the system. For example, John Smith and John L. Smith are the same person with two different profiles created. The warning is not invoked as the system sees them as two different consumers.
- Double-Booking an Interpreter is a separate functionality and does not invoke the Job double-booking conflict warning message.