If the platform notices a delay in check-in, it would send a notification to the client that the candidate hasn’t checked in. For example; A shift starts at 9:30 am, the candidate checks in at 9:40 am and the notification that the candidate hasn’t checked-in is delivered at 9:50 am. This is as a result of the notification being delayed. Notifications that a candidate hasn’t checked in usually go out on time however, the delivery of the queue could be delayed. A queue is an array of email notifications awaiting to be processed for delivery, and usually occurs for large volumes. Delays may be about an 8- 12 minute difference or sometimes more but never more than 30-45 minutes.

Notification intervals can be configured on the platform. For example: do you want the platform to notify clients that a candidate hasn’t checked in 10 minutes after the shift’s start time or after a different interval?

Please contact a member of the WOLF team if you’d like to make any adjustments to intervals.

Some notifications are grouped together: for example six candidates all start at 9:30am. The platform wouldn’t send six notifications about each check- in, it would group them and send out one notification with all the updates at 10-15 minute intervals. With that being said, the notification would show that a candidate has not yet checked-in, though they may have checked in later.

For example; If a shift starts at 9:30am, the notification would be sent out at 9:40am which would show that a particular candidate hasn’t checked in. This candidate may have checked in after the notification was sent. Therefore, if an Internal team member went to review at 9:45 or later the candidate would show as checked- in.