Skip to main content
Onboarding timeline

Preparation, app launch, dashboard access and other milestones

A
Written by ATOM Support
Updated over 3 months ago

Once you've gotten in touch with the ATOM sales team and have decided to proceed with onboarding your service at ATOM, there are a few things you are required to do, before ATOM can start working on your apps:

- Fill in the ATOM Mobility customer onboarding form completely and according to all the requirements listed, then submit it to ATOM.
In this step you will also need to provide your graphics:

1) App logo (vector file, SVG format (no set dimensions needed), background must be transparent);

2) App icon (1024 x 1024 px, vector graphic file in PNG) - note that the background color must be static, it cannot include a gradient due to the fact that it is not supported on Android OS that uses overlay color and borders;

3) Splash screen for the app (shown during loading when app is opened; vector file, SVG format (no set dimensions needed), transparent background, or PNG file 1000x1000px with transparent background).

NB! Make sure to fill all the fields in the form and follow the requirements;


- Provide your Gmail account email/password. We recommend creating a separate Google account for your service. We need the login details for a short period of time while we create a project with all the necessary settings, like Google Maps, for example. Afterwards you should change the password and add a payment card to the account, so Google Maps work for you in the ATOM dashboard. Please note that Google may charge a few EUR.

NB! Please make sure that two-factor authentication is not enabled for this Gmail account, as otherwise we will not be able to log in without you having to authorize it via your phone;

- Provide to ATOM your preferred sender name (10 characters max) for your SMS verification service account in case you will be using Dexatel (account created with the assitance of ATOM). The sender name will be shown to your clients when SMS verification code is sent, e.g. ATOM. If you will use a different serrvice, e.g., Unifonic, Twilio, etc., you will need to open your own account and provide ATOM team with access to it. Note that you will need to cover OTP verification costs from your side;



- Invite admin@rideatom.com as Admin to the App Store account by this link: https://appstoreconnect.apple.com/access/users
First, you will need to create an Apple Developer account:
https://developer.apple.com/programs/enroll
Grant access to certificates, profiles & identifiers to ATOM.

NB! you will need an Apple Organization/Company account to do this, it will not be possible with an Apple Individual account;

- Invite admin@rideatom.com & devs@atommobility.com as "Admin" to Google Play Console in "Settings" > "Users & permissions" by this link: https://play.google.com/apps/publish

- Invite admin@rideatom.com & keo@atommobility.com to your chosen payment service provider account as Developer or Admin. Please ensure you have a live account. Note that you will need to cover payment processing costs from your side;

- in case you will also require optional features, such as ID/document verification and customer support chat, make sure to establish live accounts with the respective 3rd party services and afterwards invite admin@rideatom.com to these accounts with Admin permissions. Please ensure you have a live account. Note that you will need to cover ID verification costs from your side;

When you have provided all of the above information and invitations, ATOM will be able to work on your apps and onboard your service within 20 days time.

What happens afterwards?

- Your apps published for review, then they are reviewed by Google and Apple teams and in a few days time they are published live;

- ATOM provides you the dashboard access. In the dashboard you complete essential information, add your IoTs and vehicles. Detailed article on the process you'll find here: https://support.atommobility.com/en/articles/5341399-setting-up-your-atom-dashboard

- Test on your side if everything works. Check the ATOM Knowledge base for helpful information: Atom Mobility Help Center

Reach out to ATOM support in case you cannot find the answer there;

- Launch your operations!

Did this answer your question?