Driver invite and onboarding
Invite drivers into the app with the right fleet context while keeping admin permissions out of the driver experience.
Fleet is a direct conversation because vehicle count, drivers, reporting scope, onboarding, and support need to be scoped properly before a team goes live.
Driver invites, assigned vehicles, exception review, report delivery, audit history, and IRD-aware trip records, exports, and accountant handoff stay dashboard-owned so the mobile app does not become admin software.
Bring drivers in without giving them fleet admin access.
Keep personal and fleet records separated.
Focus on missing tags, reporting gaps, and records that need attention.
Share scoped accountant or manager reports without exposing the whole account.
Invite drivers into the app with the right fleet context while keeping admin permissions out of the driver experience.
Assign vehicles and keep personal, business, and fleet records separated before reporting begins.
Surface missing tags, unreviewed trips, unusual sessions, and report gaps before month-end pressure.
Deliver scoped reports for accountant or manager review without exposing the driver's whole account.
Keep a record of report delivery, review states, driver status, and admin decisions for follow-up.
Fleet remains contact-sales so support, branding, vehicle count, driver count, and reporting cadence are agreed directly.
Use VoltMate for charging, trips, tagging, Sentry context, and the work needed to keep records clean.
Use the dashboard for fleet setup, driver status, report delivery, and the exceptions that need follow-up.
Driver app access is scoped to fleet work. Personal vehicles, personal subscriptions, AI access, automations, and fleet admin permissions remain separate decisions. Fleet conversations for New Zealand scope NZD charging costs, kilometres, drivers, reporting cadence, branding, support, and IRD record expectations.
We will scope the right setup instead of forcing fleets into a one-size-fits-all public plan.