Mobile App - UX / UI

Roadside Assistance Provider App

A dedicated mobile experience for tow-truck drivers and 24/7 roadside-assistance partners. The product connects the right provider to a stranded policyholder, giving professionals the time, distance, destination and service details they need to accept an assignment confidently and reach the customer faster.

RoleLead UX/UI Designer
ScopeDiscovery, service blueprint, user flows, UI system, interactive prototype
PlatformOperational mobile product
Duration14 weeks
Year2025
The brief

Designing for people and business.

The roadside-assistance operation depended on fast coordination between the insurer, its provider network and a customer waiting in a vulnerable situation. The design brief was to reduce manual dispatch work without pressuring partners to accept jobs they could not complete within a safe and realistic time.

Key constraints

  • Use while driving required minimal interaction and strong safety safeguards
  • Weak connectivity in highways and remote areas
  • Requests vary by vehicle, incident type and equipment required
  • ETAs must remain realistic and transparent to the policyholder
01

The challenge

Roadside incidents are stressful for policyholders and operationally complex for assistance teams. Providers often received incomplete requests through phone calls, had little visibility into distance or expected arrival time and could not easily signal availability. This created rejected assignments, repeated calls and uncertainty for everyone involved.

02

The solution

The app turns each request into a clear, time-sensitive job offer. Providers can set their availability, review pickup and destination details, assess distance and required equipment, accept or decline, negotiate an achievable arrival time and update the service status from dispatch to completion.

03

The impact

By making capacity and service progress visible in real time, the experience reduces coordination friction and helps assistance partners respond with greater speed and accuracy. Policyholders receive more reliable ETAs, while the insurer gains better operational feedback and a clearer view of service quality.

Approach

From complexity to clarity.

  1. 01Service Blueprint & Field Research
  2. 02Provider Journey Mapping
  3. 03Critical-Flow Prototyping
  4. 04Mobile Usability Testing
Discovery

Evidence before interface.

Methods

Ride-alongs with assistance providers, 9 contextual interviews, dispatch-call listening, support-ticket analysis and a service-blueprint workshop with operations.

Key insight

Providers did not reject work because of low interest alone. Most refusals came from missing context: they could not quickly judge distance, traffic, equipment fit or whether a current service would delay the next customer.

Opportunity

Present every operational variable before acceptance and let the provider communicate a viable ETA, creating a more reliable promise for the stranded policyholder.

Design rationale

Decisions, not decoration.

01

Availability belongs to the provider

A prominent availability control lets partners pause new assignments while completing a service, taking a break or operating at capacity, reducing avoidable refusals and dispatch attempts.

02

A complete offer in one glance

Incident type, vehicle location, destination, maximum arrival time and equipment needs are grouped into a single decision screen with clear accept and decline actions.

03

Progress that reassures everyone

Milestones such as accepted, en route, arrived and completed keep dispatch teams and policyholders informed without requiring repeated phone calls.

04

Designed for interrupted connectivity

Critical job details remain available offline, while status changes are queued and synchronized as soon as the connection returns.

Iteration

The work evolved through feedback.

Two prototype rounds were conducted with 12 roadside-assistance professionals using urban towing, highway breakdown and schedule-conflict scenarios. Testing led to larger controls, a clearer assignment countdown, confirmation before declining and a dedicated option to negotiate arrival time.

Outcome
Business metrics are confidential. The product established a clearer operational flow for assistance providers, dispatch teams, and policyholders.
Reflection & next steps

What I learned.

Operational speed does not come from removing every decision. It comes from giving people enough context to make the right decision quickly. A next phase would validate live routing, battery usage and ETA accuracy across different regions and provider profiles.

Have a project in mind?

Let's create something meaningful together.

Start a conversation