← Back to overview

One relationship. Two clear sides.

Actual screens from the working product preview. Each dealership, customer, vehicle and case shown is fictional.

THE DAY-TO-DAY

Useful for the owner.
Clear for the team.

The owner has their vehicle to hand. The service team can see what needs attention.

THE OWNER

A vehicle passport.

Vehicle information and time-based cover status when a warranty applies.

Fictional owner vehicle passport with a clear colour-coded warranty meter
Owner app · fictional vehicle
THE TEAM

Requests in focus.

Separate customer requests, their priorities and the next action.

Fictional service team's phone inbox with separate customer requests and next steps
Staff inbox · fictional cases
A SERVICE HANDOFF

The owner asks. The team can follow through.

A clear help route on one side; a desktop care desk on the other.

DEALERSHIP / CARE DESK
Fictional dealership desktop care desk showing incoming service requests and today's work
Team desktop · fictional requests
OWNER / GET HELP

A simpler way to ask.

The vehicle is already in view when the owner explains a concern.

Fictional owner's help screen with an oil warning-light concern entered but not sent as a live case
Owner help · example only
USEFUL UPDATES

One message. Both sides.

The same fictional service event on the dealership noticeboard and in the owner’s Updates.

DEALERSHIP / NOTICEBOARD
Fictional dealership noticeboard with a Fall service clinic in-app event
Team noticeboard · fictional event
OWNER / UPDATES

From the dealership.

The same event appears in the owner app. No phone alert is sent in this preview.

Fictional owner update showing the same Fall service clinic as the dealership noticeboard
Owner update · no push sent

These screenshots use fictional data. Live case submission, booking integrations, customer campaigns and push delivery require dealer-specific production setup and approval.