Case study · Concept build

Field service problem board

Industry
HVAC, cleaning and field service
Platform
Add-on for Jobber, Housecall Pro or ServiceTitan
Product type
Add-on

Introduction

An HVAC company with 18 technicians runs about 60 jobs a day on Jobber. On a normal day, Jobber handles it well. On a bad day, an urgent no-heat call, two late technicians and a missing part all happen before 10am.

Those problems live in the dispatcher's head, on sticky notes and in text messages. The problem board puts them in one place, each with an owner, without replacing Jobber.

The bad day the software cannot see

Urgent calls wait while the dispatcher works out who is qualified, nearby and actually free.

When a technician runs late, three or four customers are affected, and nobody tells them until they call to complain.

Finished jobs sometimes never get invoiced because a photo or a signature is missing. That is money already earned, sitting on the table.

What we would build

  • One problem board. Every exception in one list, sorted by urgency: unassigned calls, late jobs, missing parts, unbilled work.
  • An owner for every problem. Each item gets a person, a deadline and a record of what was done.
  • Automatic late notices. Customers affected by a delay get an updated arrival window by text.
  • Unbilled job check. Every morning, finished jobs without an invoice are flagged with what is missing.
Another screen

Inside the field service problem board.

Those problems live in the dispatcher's head, on sticky notes and in text messages. The problem board puts them in one place, each with an owner, without replacing Jobber.

  • One problem board
  • An owner for every problem
  • Automatic late notices
  • Unbilled job check

Concept screen · sample data

Technical decisions

  • Your platform stays in charge. Jobs, customers and invoices stay in Jobber, Housecall Pro or ServiceTitan. The add-on reads them and writes back only what you approve.
  • Access checked first. We confirm what your plan's API allows before agreeing a price.
  • Built for the dispatcher's screen. One wide screen, keyboard shortcuts and no clutter.
ReactJobber or ServiceTitan APIQuickBooksSMS updatesPostgres

What should change after launch

Before

  • Problems tracked on sticky notes and texts
  • Customers learn about delays when they call
  • Unbilled jobs found weeks later
  • No record of how problems were solved

After

  • Every problem on one board with an owner
  • Late notices sent automatically
  • Unbilled jobs flagged every morning
  • A weekly report on what went wrong and why

Try the demo

This part is working software with sample data. Click around.

jobber.problem-boardSample data
0 of 4 problems have an owner
No heat · 412 Pine RdUrgent call, unassigned
Job #2291 running 90 min late3 customers affected
Capacitor missing for #2304Part not in van
Job #2276 finished, not invoiced$640 waiting

What this means for hvac, cleaning and field service

You do not need to switch platforms to fix your worst days. If your field service software handles the normal work but not the exceptions, an add-on like this is the cheapest way to close the gap.

Typical timeline: 6 to 10 weeks. Price: Business system, from $10,000.

Concept build: this page shows what Myriah would build for this kind of business. Screens use sample data, the story describes a typical business rather than a named client, and numbers are targets, not results.

More case studies

06 Startups and new ventures

Two-sided booking marketplace

A first version that lets customers find, book and pay local service pros, with an admin panel to run it, launched in weeks instead of months.

Read the case study
01 Nonprofits and logistics

Fleet operations portal

One portal for every vehicle, driver, licence, inspection, ticket and fuel card, replacing six spreadsheets and a shared inbox.

Read the case study
Get a free quote