FixHomeService.cz, Appliance Repair Booking Platform

A Prague-based appliance repair service consolidated phone intake into an online booking flow with transparent fixed pricing, two-hour response routing and a single dispatcher view.

FixHomeService.cz, Appliance Repair Booking Platform
Industry
Home Services
Country
Czech Republic
Delivered
2025
Timeline
8 weeks
Services
3 disciplines
Our role
Designed & built
Project context

The starting point.

A family-owned repair shop with 11 years of operating history in Prague. Everything ran on phone calls, a paper schedule and a single landline that rang straight to the dispatcher. The team knew the work; the funnel was the bottleneck.

The challenge

A high-trust service stuck in a phone-only funnel.

Bookings only came in by phone, weekday office hours. Customers shopping online at 9pm saw a static brochure site, no pricing, no way to book – so they bounced to the next listing on the search results page. The dispatcher carried the entire schedule in her head.

  • ~30% of out-of-hours leads abandoned before the next morning call-back.
  • No upfront pricing, so every call started with a 5 – 7 minute negotiation.
  • Dispatcher juggling three channels (phone, email, Facebook DMs) with no consolidated view.
  • SEO surface limited to a single homepage – no brand- or category-specific landing pages.
What we built

Shipped during the engagement.

Online booking flow with calendar slots

Fixed-price tariff table per appliance category

Two-hour response SLA routing logic

Consolidated dispatcher dashboard

31 brand + category SEO landing pages

LocalBusiness schema with city-level coverage

The solution

A booking engine that closes the loop in one place.

We built the entire funnel around a single source of truth: a booking flow that captures appliance brand + model, category of fault, address, and preferred two-hour window. Pricing is shown upfront from a fixed tariff. Submitted bookings appear on the dispatcher dashboard in real time and auto-route to the nearest available technician.

Engagement phases

How the 8 weeks broke down.

Discovery

Two weeks shadowing the dispatcher, mapping every common booking path and pricing edge case before writing a line of code.

Build

Booking flow, dispatcher dashboard, pricing engine and SMS notification layer shipped behind a feature flag for parallel testing with the legacy phone process.

SEO

Brand and category landing pages generated from a structured content model; LocalBusiness schema tuned per Prague district.

Launch

Phased rollout - phone retained for two weeks as fallback, then the booking flow took 100% of inbound. Training plus a printed cheat-sheet for the dispatcher.

Stack we used

Tools and platforms in this build.

  • WordPress
  • Next.js
  • Booking flow
  • Schema.org LocalBusiness
Results

What the work returned.

Measured at the 90-day post-launch mark and verified by the client team.

24/7
booking intake, was office-hours phone only
-50%
dispatcher time per booking
+28%
completed bookings (90-day cohort)
92%
two-hour SLA hit rate
31
brand/category SEO pages live
8 wks
discovery to full launch
Lessons

What we'd do differently next time.

We underweighted the dispatcher onboarding. The interface was intuitive for a buyer; for someone used to a paper schedule, the dashboard needed three rounds of in-person walkthroughs before adoption stuck. Build the training programme in week one, not week eight.

Plan your build

Have a similar problem? Let us scope it.

Tell us about your business and goals. We will reply within 3 business days with a written proposal and a fixed-fee diagnostic option.