My employee can't clock in

This might be the number one support question we get.

But the funny thing is it's not a question, just a statement, but we've heard is so many times, we know the drill.

Sure, there is a slight chance it could be our software ( less than 1% ), but for the majority it has something to do with the account's time clock settings.

Just yesterday...

We got a call from a customer who said "My employee can't clock in".

So I said, okay, can you tell us what the employee is seeing on their end?

In response he said "hang on... HEY BOB!... silence for a few seconds... HEY BOB!!!"

That's when Bob finally answered... "What!!?"

"The Webtimeclock guy wants to know what happens when you try to clock in."

Unfortunately all Bob could say was "I don't know, I just can't clock in".

But fortunately for me, that was no problem, it gave me enough time to log into the customer's account to see what was up.

Sure enough, the account administrator had set IP Login Security to ON for this employee. Meaning they could only clock in if they were using an authorized IP address, making it easy to assume their IP address had changed.

So as a test, I turned the setting off and asked if Bob could try to clock in... That fixed it.

Reasons why employee's can't clock in from the web

For the most part, there are three possible reasons (outside of losing power or Internet connection).

1. If you use IP Login Security, it is possible your Internet Service Provider changed your IP address

2. The employee did not enter the correct username, password, or PIN

3. You are using a shift rule that locks the employee out completely

Conclusion

If an employee can't clock in, there is a reason, and it probably has something to do with your time clock settings.

No worries however, we are happy to assist.