When you've just received your software from ATOM Mobility, the dashboard has multiple points to complete to ensure your customers have a good user experience in the mobile apps.
Make sure of the following during your dashboard set-up and app tests:
your IoT devices and vehicles are added, are online, send a signal at least once in 0-20min, and respond to commands (relevant for Sharing and Rental only);
vehicle shows the correct location on the map in the dashboard (Vehicles -> Map section) and the battery/fuel level is displayed correctly in the vehicle list (relevant for Sharing and Rental only);
your Drivers are added and have managed to log into the driver app and mark themselves Online in order to accept ride requests at least once (relevant to Ride-hailing only; full guide to configure the Ride-hailing platform here);
create at least one operational zone and link your vehicle classes in the zone settings (relevant for Ride-hailing);
the content for main and short tutorials has been added from your side (relevant for Sharing and Rental only; guide here);
in the vehicle model add the vehicle battery voltage range for e-cars or fuel tank capacity for petrol cars (relevant for Sharing and Rental; guide here);
in the vehicle model for scooter and e-bike define the battery level % at which the vehicle needs to stop in order to avoid vehicle completely discharging during a ride (relevant for Sharing);
the vehicle model/class images have a transparent background - it looks better in the user apps;
the app localizations are translated from your side in all the required languages - this will ensure the users will not see any untranslated localizations as the localization keys in the apps (guide here);
the additional languages are available in the app profile section - if not, inform help@atommobility.com of the languages that need to be enabled in your user apps based on translations you did previously;
the links to your service's privacy policy and terms and conditions are working well in the app and are available in all the languages of the app;
at least one email is verified in your system preferences in order to receive Alerts & Notifications messages from ATOM platform;
at least one channel for support - e-mail address or phone number or chat option - is configured in your System preferences;
configure System preference settings for Stopping the ride if the balance goes below a certain level and Automatically ending the ride if the vehicle is not moving due to being abandoned for a long time by the user (relevant for Sharing only);
the registration process is successful in the app. In regards to this, make sure your OTP service account (Dexatel, Twilio, Unifonic, or other) always has a positive balance;
the payment process works well for you from start to finish:
make sure to test how adding a card/payment method works;
if you are using the Wallet, test the top-up flow;
confirm that recurring payments work - can the user pay for a second ride from the card/payment method previously saved, or does he need to enter card details repeatedly in the app? If you are using Pay after ride flow, does the client get charged from his card/payment method at the end of the ride, or does his wallet balance simply become negative? Can a negative balance be charged from the card manually via the dashboard?
make sure all enabled payment methods work well in your apps - payment card, and if supported by your payment gateway: Apple Pay on the iOS app, Google Pay on the Android app, PayPal, Klarna, iDEAL, Bancontact, TWINT, mobile money.