If you have an active and approved Operator Relationship with Uber, Bolt, DiDi, or another RideShare platform and you have no work-time violations in the past 10 days, then this issue could potentially be caused by how you are using Logmate.
Step One:
Ensure your TSL Holder relationship with the RideShare is in an approved state.
If it is approved, then proceed to the second step.
If it is not approved and is in a pending state, or is simply not showing, then you will need to send a request to Drive under this RideShare platform's TSL number.
Step Two:
Understand if you have any violations which could be the reason why your Driver account was suspended by the RideShare platform. Violations will show as a red icon next to your shift records in your Driver Admins. Login > Shifts > Filter for the last 30 days.
Now we go back to the start of this article: if you have an active and approved Operator Relationship with Uber, Bolt, DiDi, or another RideShare platform and you have no work-time violations in the past 10 days, then this issue could be caused by how you are using Logmate.
The Cause:
This could potentially be caused by you not ‘Locking’ your Shift at or close to the time of close. For example, if you are in the habit of not locking until you are about to create a new shift (~ >10 or >24 hrs later), this will be the main cause.
The Solution:
Our advice to all Drivers is to always Lock your Shifts as soon as you finish your work-day.