We just recently rolled our Drive to a small test group and have some considerable growing pains. We have not used GPS tracking for mileage before so this is certainly going to take some time for everyone to get used to. Below are some of my current pain points. Does anyone have experience with these issues in Drive and have any advice or solutions? Thanks!
Hi, we have had errors on the journeys claimed and according to support it is a bug that randomly uses KMs instead of miles?! No workaround has been offered, we have been told it is being worked on by developer team to correct at some point but that it only affects Android users! Surely with 2.5Bn devices out there that is quite a lot of the customer base.
I am wondering if you were able to resolve any of the issues that you experienced during your initial implementation? We are considering Drive here, and the pains you identified would definitely discourage our employees. Any advise or lessons learned is appreciated.