12Service & Repair · Web development
Customer portal for service requests and status
Customers logging requests and tracking them without phoning.
- Request logging by customer
- Equipment list per customer
- Status visibility
- Document and report download
The problem
Requests arrived by phone and email and were logged inconsistently. Customers had no way to see progress, so they phoned again.
What we built
We built a portal where customers raise requests against their own equipment and see status, history and documents.
Modules delivered
- Request logging by customer
- Equipment list per customer
- Status visibility
- Document and report download
- Request history
- Notification on status change
What changed
What the delivered system does differently from the process it replaced.
- Requests arrive in one consistent format
- Customers see progress without phoning
- History is available to both sides
Built with
The stack chosen for this build.
- Next.js
- TypeScript
- PostgreSQL
Why this customer is not named
Most of our customers allow the work to be described but not their name published. Where a customer has given permission, their name and testimonial appear here.
Independent accounts of our work are published by customers themselves on our Facebook reviews page.
Related case studies
Does this look like your problem?
If any of this is familiar, the first step is the same one this project started with: a free requirement study that ends in a written scope and a fixed price.