Quick fixes, 9 p.m. friendly.
After-hours caller routed wrong, or a job that should have hit the schedule didn’t? Skim the section that matches your stack and trade, and the fix is usually under 30 seconds away.
Your service-trade software
Calls ring but no job is created in ServiceTitan
The technician never sees the call on the schedule, the homeowner got the after-hours page answered, and ServiceTitan didn't log a new job. Most often a routing or membership mismatch is silently dropping the write.
Read the fix →Housecall ProHousecall Pro shows the appointment an hour late
The job lands in Hearthbench but it lands in Housecall Pro at the wrong time, usually an hour early or an hour late. The cause is almost always a daylight-saving or timezone mismatch on the Housecall Pro account, not a Hearthbench issue.
Read the fix →JobberCalls ring but no job is created in Jobber
The Hearthbench call detail looks fine, the customer heard the after-hours greeting, but no Jobber job was created. This is almost always a routing-rule or trade/tag-config mismatch on the Jobber side.
Read the fix →Your shop’s trade
Calls ring but no job is created (plumbing)
A water-heater emergency at 9 p.m. was answered, but no job hit the schedule. Plumbing emergencies should always create a job — diagnostic or not — so the on-call tech can triage tomorrow's route.
Read the fix →HVACCalls ring but no job is created (HVAC)
A no-cool on a 95° Saturday was answered but nothing landed on the dispatch board. HVAC trips that mention temperature, infant in the home, or "stopped working" need a same-day routing rule to handle the risk of waiting until Monday.
Read the fix →ElectricianCalls ring but no job is created (electrical)
A panel failure or a chirping smoke detector was answered but nothing landed on the schedule. Electrical emergencies get escalated same-day regardless of trade hours, so the symptom has to trip the urgency tag on intake.
Read the fix →CleanerCalls ring but no job is created (cleaning)
A move-out clean, a weekly rebook, or a recurring client call was answered but no job was created. Cleaning jobs are lower-urgency but every call should still land on the calendar — the miss is a routing or schedule mismatch, not a routing-rule priority issue.
Read the fix →