Appliance repair
Example build: booking, dispatch, and parts CRM for an appliance repair shop
Appliance repair company scenario, Metro Vancouver
A small appliance repair company running on a shared calendar, a parts spreadsheet, and a group text with the techs. This is the custom CRM we would build for them: booking, dispatch, job tickets with model and serial, parts tracking, and automatic customer status updates.
Example build, not client work. We don't publish case studies until a real client gives us permission and real numbers.
The problem
Where they would be stuck
Bookings and dispatch live in a shared calendar with no history.
Parts on order sit in a spreadsheet only one person keeps up.
Customers call for status because there is no other way to check.
Techs re-ask customers for model and serial numbers on almost every visit.
The approach
What we would build and why
- 1
Structured intake capturing appliance, symptoms, and history.
- 2
Dispatch board with drag between techs and days.
- 3
Parts on order linked to jobs, with automatic flags when parts arrive.
- 4
Customer portal for status, quote approvals, and photos.
What it would do
Where the CRM would change the day
One place for bookings, dispatch, job tickets, and parts.
The customer portal answers 'any update?' before the phone rings.
Techs see model, serial, and history without re-asking the customer.
New techs onboard fast because the phone view is simple.
Under the hood
What it would be built on
Stack & shape
- Web app plus mobile view for techs
- Postgres database, owned by the client
- Twilio for SMS status updates
- Stripe for card payments