The client
Mobile PC Doctor is a computer repair business in Grays — another of our own.
The problem
Jobs were lost to unanswered messages, and repairs ran quietly late because nobody was watching a promised date. The website took bookings; nothing after the booking was in one place.
What we built
Three surfaces on one system. The website at mpcdoctor.com takes bookings and enquiries. A customer app lets a customer follow their repair, message the shop and pay, and the same app, role-switched, is the staff app: a Today screen of what is due, every conversation, every job. An owner dashboard at dashboard.mpcdoctor.com runs the shop on the web, and all three talk to one API at app.mpcdoctor.com. The idea underneath is a clock on everything: a response clock runs while a customer waits to hear back, a delivery clock runs from the moment a quote promises a date, and anything overdue surfaces on the Today screen and buzzes the phone. Enquiries from the web form, SMS and the app land in one inbox, and a customer who enquired on the web finds the conversation waiting when they install the app.
Results
The website, the dashboard and the API are live. The customer and staff app is in testing with the shop through TestFlight and is not in the stores yet.
