Onboarding: how new users get to their first vehicle
Several checks sit between sign-up and the first trip. In Zemtu you assemble those steps per user group – strict for public operation, lean for corporate fleets.
Onboarding decides whether interested visitors become paying customers. At the same time it is the one moment where you as an operator really control who you hand a vehicle to. Those two goals pull in opposite directions – which is exactly why the process should fit your business, not the other way round.
The four steps
A complete onboarding almost always consists of the same building blocks, whether you run ten vehicles or a thousand.
- Create an account. Email, password, address confirmation. Do not ask for anything that is not strictly necessary – every extra field costs conversions.
- Verify the driving licence. Photo of front and back plus an ID document. Either you check yourself or you have it checked.
- Add a payment method. Credit card, direct debit or invoice – depending on the customer group.
- Approve. Only after approval can the account book a vehicle.
Where customers drop out
Drop-off is highest in two places: uploading documents and waiting for approval. Solve the first with clear guidance right in the app – which side, which lighting, which format. Solve the second with speed.
If two working days pass between application and approval, the spontaneous need that triggered the sign-up has long been met elsewhere. So review several times a day, or automate the step.
Every operation needs a different process
Public carsharing in a small town has different requirements than a corporate fleet or a hotel bike rental. A few examples from practice:
- Public carsharing: full verification with licence and ID, approval by your team, payment method mandatory.
- Corporate fleet: HR confirms employment, no payment method needed – billing runs through cost centres.
- Housing project: property management approves, only the driving licence is checked.
- Tourist bike rental: no licence required, but a credit card as security. Registration should take under two minutes.
How the process is configured in Zemtu
That is why onboarding in Zemtu is not a fixed sequence but a set of steps you assemble. It is defined per user group – so you can run different processes side by side.
- Define required details: which fields appear during registration and which of them are mandatory.
- Choose documents: driving licence, ID, both or neither – depending on the vehicle type.
- Set the verification route: manual review by your team or automated identity verification.
- Rule the approval: who may approve, and does it happen automatically after a successful check or always by hand?
- Payment method: mandatory, optional or not at all – for instance with internal billing.
- Group assignment: new accounts land in a group that determines rates, vehicle access and booking rules.
Because everything hangs off the user group, special cases can be modelled without complicating the standard path: your own staff, test accounts, corporate customers with a framework agreement or hotel guests each go through exactly the steps that make sense for them.
Manual or automated checks?
For small fleets with a manageable inflow, manual review is perfectly fine: someone looks at the documents and approves. It takes a few minutes per person and gives you a feel for who your customers are.
From roughly fifty new sign-ups a month, a verification service pays off. It compares selfie and ID photo, detects signs of forgery and returns a result in under a minute. How that works in detail and where it stops is covered in the article on identity verification with Stripe Identity.
Where to start
Start strict and relax later, not the other way round. A process that begins with a manual check can be automated easily once the numbers grow. The reverse – tightening the rules after an incident – costs trust with exactly the customers you already have.
More articles
The work between two bookings
Between two bookings sits the work that decides availability. How Lanterne turns it into tasks – and where the limits are.
Learn more →I LOCK IT: how a bicycle becomes a sharing bike
A bicycle has no electrical system to power a telematics unit. So the technology sits in the lock. What I LOCK IT does, when tracking is needed and what to settle before you start.
Learn more →Analysing driving behaviour: a look at INVERS Driving Analysis
Speed, harsh braking, hard cornering: what the INVERS analysis measures, what operators do with it – and what data protection requires.
Learn more →