<h1>Prerequisites</h1><ul class="accent-bullets"><li>Wunder Mobility Backoffice Access: Permission to view and edit Vehicle details and Tasks.</li><li>Wunder Operational App: Field agents must have the service app installed on their devices.</li><li>Vehicle Category Configuration: Approach, Leave, and Deploy vehicle command chains must be configured in the Vehicle Category settings.<blockquote>Note: Contact your Customer Success Manager to assist with configuring complex command chains.</blockquote></li></ul><hr><h1>How It Works</h1>Maintenance operations rely on three separate features that you coordinate to manage your fleet efficiently. These elements function independently but are executed in parallel during a service workflow:<ol class="steps-list"><li>Tasks<ol class="steps-list"><li>These are the "To-Do" items created in the Backoffice (e.g., "Change Tires"). They inform the field agent what needs to be done.</li><li>Task creation can be manual or automated (e.g., triggered by low battery alerts).</li></ol></li><li>Service States<ol class="steps-list"><li>This influences the vehicle's visibility and availability.</li><li>Setting a vehicle to a certain service state hides it from the Consumer App to prevent rentals.</li></ol></li><li>IoT Command Configurations (Approach, Deploy, Leave):<ol class="steps-list"><li>These are pre-defined action sequences triggered by starting and ending the maintenance in the Service App.</li><li>The sequence in which the commands will be executed depends on the sequence in which you actually enable them in the Backoffice. </li></ol></li></ol><h2>The Maintenance Logic</h2>When servicing a vehicle, the operator typically performs two actions in the Backoffice: creates a task and updates the service state.In the field, the Service App simplifies the physical interaction via three key phases:<ul class="accent-bullets"><li>Approach (Start): When the agent arrives and starts the task, the app triggers the configured "Approach" commands (e.g., unlocking the vehicle).</li><li>Deploy (Finish): When the task is completed successfully, the "Deploy" action triggers the configured closing commands (e.g., locking the vehicle).<blockquote>Configuration Note: You can configure the Deploy action to also automatically update the Service State back to "Operational," ensuring the vehicle becomes revenue-generating immediately.</blockquote></li><li>Leave (Pause): If the task cannot be finished, the "Leave" action triggers closing commands (e.g., locking the vehicle). Usually you don't configure a service state change here, and therefore you have a second option besides deploying it.</li></ul><img src="https://uploads.productlane.com/978850934c382c8f3eb8de8620183e69.jpeg" data-processed-src="https://uploads.productlane.com/978850934c382c8f3eb8de8620183e69.jpeg" data-original-src="https://uploads.productlane.com/28f16ea14efc6ebd88788684f2562ca4.png"><hr><h1>Step-by-Step Guide</h1><h3>1. Planning Maintenance (Backoffice)</h3>Operators prepare the vehicle for service by managing the Task and Service State separately.<ol class="steps-list"><li>Identify the vehicle requiring service.</li><li>Create a Task describing the work (e.g., "Swap Battery").</li><li>Update the Service State manually to a non-operational status (e.g., "In Service").<blockquote>Result: The vehicle is hidden from the Consumer App.</blockquote></li></ol><h3>2. Executing Maintenance (Service App)</h3>Field agents execute the physical work using the service app to trigger IoT commands.<ol class="steps-list"><li>Locate the vehicle.</li><li>Tap "I’ve arrived - Start" (Approach).<blockquote>Action: Triggers the configured "Approach" commands (e.g., vehicle unlocks).</blockquote></li><li>Perform the service work.</li><li>Select the completion action:<ol class="steps-list"><li>Option A: Deploy (Job Done): Triggers "Deploy" commands (e.g., locks vehicle).<blockquote>Note: If configured, this step can also automatically switch the Service State to "Operational."</blockquote></li><li>Option B: Leave (Job Incomplete): Triggers "Leave" IoT commands (e.g., locks vehicle).Result: it will trigger the leave commands, and usually, you don't configure, for example, a service state change here. </li></ol></li></ol><hr><h2>Micromobility Specifics: Mass Scanning</h2>For scooter and bike fleets, agents can process multiple vehicles efficiently using the Mass Scan feature.<ol class="steps-list"><li>Open the QR Scanner in the Service App.</li><li>Switch to Mass Scan Mode.</li><li>Scan multiple vehicles in rapid succession.The scanner remains active between scans to allow quick processing of a hub.</li><li>Trigger a Batch Action:<ol class="steps-list"><li>Mass Approach: Sends the "Approach" command to all scanned vehicles simultaneously.</li><li>Mass Deploy: Sends the "Deploy" command to all scanned vehicles simultaneously.</li></ol></li></ol><hr><h1>Tips and Best Practices</h1><ul class="accent-bullets"><li>Configure "Deploy" for Availability: To maximize fleet utilization, configure your "Deploy" settings to automatically reset the Service State to Operational. This eliminates the need for a Backoffice operator to manually release the vehicle after a repair.</li><li>Use "Leave" for Incomplete Work: Train agents to use "Leave" when a repair is unfinished or waiting for parts. This secures the vehicle via IoT locking but ensures it remains hidden from customers on the map.</li><li>Batch Operations: For micromobility, group vehicles physically before scanning. Using Mass Scan on a group of vehicles significantly reduces the time spent waiting for individual lock/unlock commands.</li></ul><hr><h1>Troubleshooting</h1><h3>Commands do not trigger on Approach/Deploy</h3>Possible Cause:<ul class="accent-bullets"><li>The "Approach" or "Deploy" command chains are not configured in the Vehicle Category settings.</li><li>The vehicle is offline and cannot receive the command.</li></ul>Resolution:<ul class="accent-bullets"><li>Verify the command configuration in the Backoffice Vehicle Category settings.</li><li>Check the vehicle's last seen status.</li></ul><h3>Vehicle remains in "In Service" after Deploying</h3>Possible Cause:<ul class="accent-bullets"><li>The command configuration is set to trigger IoT commands only, without updating the <code class="inline-code-shadow bg-gray-100 border border-gray-200/60 dark:border-gray-800 font-medium dark:bg-gray-700/60 text-gray-700 dark:text-gray-200 font-mono text-md px-1 py-0.5 rounded-[0.2rem] [&amp;::before]:content-none [&amp;::after]:content-none">service_state</code>.</li><li>A separate issue (e.g., critical battery level) is preventing the state change.</li></ul>Resolution:<ul class="accent-bullets"><li>Manually update the Service State in the Backoffice.</li><li>Review the "Deploy" configuration to ensure it includes the state change logic if desired.</li></ul>

Fleet & Operations

Streamline field operations by automating vehicle state changes and commands during service tasks.

Optimizing Vehicle On-Field Maintenance Flows

Platform overview

Getting Started

Locations and branches

Damages and Task management

Service App (Beta)

Card Management (RFID)

Managing On-Demand Rentals

Radar

On-Demand vs. Pre-Booking

Additions and Insurance

Subscriptions & Multi-Benefit Packages

Pricing, Memberships & Promotions

Login Options & Sign up Fee for End Users

User Management & Profiles

Roles and Permissions 

Business accounts and corporate billing

Users & Accounts

Payment Gateways and Methods

Invoicing

Invoice PDF Structure & Customization

Revenue Protection and Payment Assurance

Payments & Invoicing

Mobile App Translation Keys: Sign Up, Rental & Booking

App Configuration & Customization

MaaS API

FreeNow Integration Overview

Credit Rating (CRIF)

Veriff Driving License Verification

Onfido Identity & Driver's License Verification

Braze Messaging integration 

AppsFlyer Integration

Zendesk Chat

Integrations & APIs

INVERS IoT Integration

Vehicle & IoT Support

Introducing Wunder Analytics (Beta)

Issues Analytics (Beta)

Data Insights

Two-Factor Authentication (2FA)

Security

Choosing the Right Sign-In Method in Wunder  (Email OTP vs Phone Login vs Password)