Can I run an EV-only service?
Yes. You can configure the visible service offering around electric vehicles and hide services that are outside your model.
Configure an EV category in the same role-aware app, with quick in-app administration and full control on the web. App Experience can present rides, shops and delivery, or both; add specialised integrations only after they are scoped and tested.
An electric fleet has different operational questions: vehicle eligibility, charging time, service range, and how drivers plan their shifts. Those questions matter, but software should not claim to solve them with features that have not been implemented and validated.
Waslni can provide a practical starting point through configurable service types, fares, operating areas, registration forms, vehicle information, driver-document review, and role-based administration. The same mobile app serves riders and drivers according to their role.
Battery-aware dispatch, charging-network feeds, charger referral commissions, automatic CO₂ calculations, and ESG reports are not standard capabilities. They require reliable data sources, methodology, contracts, and dedicated engineering before they can be promised.
Create an EV category with its own customer-facing name, availability, capacity, and supported pricing settings.
Define the areas where the EV service is available based on the operator’s real vehicles, charging plan, and support capacity.
Use configurable registration fields to record relevant vehicle details. Live battery telemetry is a separate integration, not a standard promise.
Publish environmental figures only when they use an agreed methodology and auditable data. Waslni does not invent savings per trip.
Riders select the available service and drivers manage assigned work through the same role-aware mobile app.
Define and review the registration information required for EV drivers and vehicles. Local inspection and approval remain external responsibilities.
Yes. You can configure the visible service offering around electric vehicles and hide services that are outside your model.
Not as a standard feature. Live battery-aware dispatch needs vehicle telemetry, permissions, reliability rules, and dedicated testing.
No charging-network integration is promised by this page. A specific provider can only be discussed after its API, commercial terms, country coverage, and support requirements are known.
Not as a verified standard capability. Any emissions statement needs a documented baseline, energy-source assumptions, distance data, and an auditable calculation method.
Yes. Operators can configure multiple ride service types, or show only the EV option when that is the entire business.
Review the service-type, registration, pricing, unified-app, and administration controls in the demo.