Getting started

Downloading the app

The app is published on the App Store (iOS) and Google Play (Android). Because each operator runs its own branded deployment, each deployment is a separate store listing under that operator's own name and icon; searching the stores for "EOSVOLT" does not find a deployment branded under a different name. Drivers therefore search for the name the operator communicates to them, which is also the name shown on the app icon after installation.

[IMAGE: App Store and Google Play listing for a branded deployment]

Signing up and logging in

There is no password anywhere in the app. Access to the email inbox is the credential, so there is nothing to forget, reset, or reuse across services:

1. The login screen asks for an email address ("Enter your e-mail") and the driver taps Next.
2. The app sends a one-time code to that address and moves to the "Confirm your e-mail" screen, which shows the address the code went to.
3. Entering the code logs the driver in. The same flow creates the account on first use and logs into it on every later use, so there is no separate registration form.

If the code does not arrive, Send code again requests a new one. A short countdown must pass before another code can be requested, which prevents a mistyped address from being flooded with emails; the countdown is also a cue to check the spam folder and verify the address shown on screen.

[IMAGE: Login screen with email entry, followed by the code confirmation screen]

Browsing without an account

The login screen offers Skip, which opens the app without an account. A driver who skips login can browse the map, open locations, and compare prices, which lets someone evaluate coverage and cost before handing over any personal data. Actions that create a financial commitment, starting a session or booking a charger, prompt for sign-up at that point with the message "Sign up to start charging, it only takes a few seconds of your time."

First-time setup

After the first login the app walks through the remaining requirements:

• Terms and Conditions: charging cannot begin until these are accepted, since the terms cover payment and liability for sessions.
• Name: a first and last name attached to the account and its invoices.
• Payment method: a card added under Payment methods. This is required before the first session because every session start places a temporary Pre-authorization hold on the payment method; with no card on file there is nothing to place the hold against, and the charger will refuse to start. See Payments and billing for the available methods.

A tour of the bottom tabs

The tab bar at the bottom of the screen is the app's main navigation. The full set of tabs the app supports:

• Map: charging Locations plotted geographically, for finding a charger near the driver's current position.
• List: the same locations as a searchable list sorted by distance, more practical than the map when the driver already knows the location's name.
• The home charging tab, labeled Home, Dedicated, or something else, depending on the deployment: the driver's own charger, its schedules, charging rules, and sharing settings.
• History: every past session with its date, location, and cost, and the entry point for invoices. Covered in Charging history and receipts.
• Inbox: the message history behind the app's push notifications, so an update about a session or booking can still be read after the notification itself was dismissed. Some deployments place this inside Profile instead of the tab bar.
• Profile: account details, payment methods, Charge keys, teams, cars, and settings, plus Edit profile for changing the name or email and deleting the account.
• Scan: opens the camera directly on the QR scanner, skipping the map entirely; scanning the code printed on a connector jumps straight to starting a session on that exact connector.

[IMAGE: Bottom tab bar showing Map, Home, History, Inbox, and Profile]

Availability: optional per deployment. The tab set itself is part of each deployment's configuration: a deployment built around a single home or workplace charger has no Map or List tab at all, and individual tabs such as the Inbox can be used depending on the business case of the individual operator.

Language

The app follows the language set on the device, or a language chosen with Select Language in the app's own settings, so a driver never has to configure it for the common case. The in-app support chat replies in the app's language regardless of the language the driver writes in.

Common questions

What does the login flow mean for account security and support load? Since there is no password, there are no password resets to support and no credential reuse across services; a driver locked out of the app is really locked out of their email, which is outside the app's scope.

Can a prospective user evaluate the app without creating an account? Yes. Skip on the login screen opens the map, locations, and prices for browsing; only starting a session or booking triggers the sign-up prompt.

Why does the app insist on a payment method before the first session rather than at payment time? The payment method is exercised at session start, not session end: a pre-authorization hold is placed when charging begins, so a valid card must already be on file for the session to start at all.

Is the set of tabs the same in every deployment? No. Which tabs appear, and what the home charging tab is called, are part of each deployment's configuration. See White-label configuration.