Roadside requests and service visits Design concept
Fazaa
An Arabic roadside identity connecting the reported problem, vehicle location and assigned technician in one trackable request.
We designed Fazaa for a fictional Kuwaiti roadside provider operating from Hawally. The brief focused on helping a driver describe an observed problem, share an accessible location and understand who accepted the request. A concise request form and a detailed follow-up screen give the service its own recognizable identity.
Client in the design study
Fazaa Roadside Services
Hawally, Kuwait
Project brief
A fictional roadside provider needing structured Arabic requests and clear technician, location and visit-scope follow-up.
Design scope
- Arabic roadside identity
- Request and vehicle-review interface
- Technician tracking, approach map and visit scope
01 / The project challenge
The project challenge
Problem descriptions, location links and technician names originally lived in separate messages and calls. Acceptance could be mistaken for a guaranteed repair or immediate arrival, although diagnosis requires inspection. The team needed practical preparation details and clear visit scope, with estimated progress distinguished from a promise. Entrance and parking notes were as useful as the vehicle type.
02 / The solution we designed
The solution we designed
The request begins in the driver’s language: vehicle will not start, tyre concern or unusual noise. Vehicle, location and entrance notes are reviewed before sending. Once accepted, a separate screen shows the request reference, technician and proposed visit scope. A detailed neighborhood map provides named streets, vehicle position and a readable approach route. Inspection and agreement on additional work remain later steps after arrival.
03 / The experience
The experience
Maryam Al Rashed reports that her sedan will not start in a Jabriya parking area. She records the side-street entrance and reviews request F-024. The Fazaa team accepts and assigns Fahad Al Mutairi. A proposed inspection visit costs 12 KD, with parts and additional work reviewed after inspection. The sequence moves through Reviewed, Accepted and Technician on the way; no diagnosis is claimed before the technician reaches the vehicle.
04 / What it could do
What it could do
Plain-language reporting
Direct choices and concise notes help preparation without treating the selection as a diagnosis.
Accessible location detail
Vehicle position, area and entrance notes are reviewed together before a visit is accepted.
Assigned technician
Team and technician identity, contact actions and reference explain who is handling the request.
Clear visit scope
The proposed visit price stays separate from parts and work that require agreement after inspection.
05 / A typical journey
A typical journey
Describe the observation
Choose the visible problem and add vehicle information and useful preparation notes.
Review the location
Check vehicle position and entrance before sending the request.
Follow the team
After acceptance, technician identity, approach status and scope appear together.
Inspect and agree
Inspection starts on arrival, followed by agreement before any additional work.
06 / Inside the interface
Inside the interface
Arabic interfaces with right-to-left reading and sample workflows set in Kuwait. Open the images to explore the details.
Explore the screens.
Open any screen to explore the complete project gallery.
07 / Design direction
Design direction
Orange, charcoal and light surfaces support a compact road-and-assistance mark. Fazaa has a different structure from vehicle rental and parcel dispatch: the reported problem leads the experience. Realistic vehicle and diagnostic-tool imagery avoids dramatic scenes. The map has Arabic street labels, scale and a natural route, while the technician, contact actions and visit scope form an independently readable panel.
Discuss a similar idea
