The first hot week of summer
Temperatures climb on Monday. By Tuesday lunchtime the office has taken a flood of calls: a server room at a contract client, a GP surgery, a restaurant whose kitchen is unbearable, an office where one unit is dripping, several homeowners whose units were installed by someone else. The two people answering phones write each on a pad. The service manager tries to work out who is most urgent and who is under contract. Callers ring back every hour to ask when someone is coming.
Triage by volume, not by priority
Most of the year, calls are manageable and the team knows every client. In a heatwave, the volume breaks the informal system. The information needed to prioritise (is this a contract client, is it a critical system, what is the equipment, what are the symptoms) is not collected consistently, and callbacks consume the time that should go on dispatching.
- Calls are logged on paper or in scattered emails.
- Contract status and response terms are checked from memory.
- Critical systems, such as server rooms, are not flagged in advance.
- Symptoms are vague, so engineers arrive without the likely parts.
- Callers phone repeatedly for updates.
What a bad heatwave week costs
Contract clients waiting behind one-off jobs, which damages relationships you depend on all year. Critical systems not reached in time. Engineers sent to jobs that were a tripped isolator or a blocked filter the client could have checked. And an office team exhausted by the phone, making the mistakes tired people make.
It also costs sales. Some of the callers in a heatwave are new clients who would sign a maintenance contract if the first experience went well.
The intake and triage we build
- A breakdown form on your website and a text link for callers, asking site, equipment, symptoms, photos of any error code, and whether the area is critical. Emails to your breakdown address are read by an AI model and turned into the same structured record.
- Phone calls are logged by staff into the same form, so every call ends up in one queue.
- Each call is matched to your client and site records. Contract clients, response terms and critical systems you have flagged are shown on the ticket.
- The queue is ranked by rules you set: contract terms, critical systems, vulnerable occupants and age of the call. Staff can override with a reason.
- For common symptoms, callers are sent your approved basic checks (such as confirming power and remote settings) while they wait, never anything inside the equipment.
- Callers receive status updates by text when their job is assigned and when the engineer is on the way, which cuts repeat calls.
| Moment | In a heatwave now | With intake and triage |
|---|---|---|
| Call received | Written on a pad | Structured ticket in one queue |
| Contract check | From memory | Shown on the ticket |
| Priority | Loudest caller | Your rules, with overrides recorded |
| Engineer preparation | Vague symptoms | Error codes and photos |
| Caller updates | Repeated phone calls | Texts at each stage |
A heatwave that feels manageable
The office works from one ranked list. Contract clients and critical systems are seen first because the system knows who they are. Engineers arrive with error codes and photos. Callers know where they stand without phoning. The service manager makes decisions rather than transcribing.
After the hot spell, the data shows how many calls came from contract clients, how many were simple checks and how many were new clients, which helps plan next summer's capacity and your contract offer.
Recognise these?
- Hot weather turns the office phone into the main bottleneck.
- Contract clients have waited behind one-off calls.
- Engineers arrive at breakdowns without knowing the equipment.
- Callers ring back repeatedly for updates.
- You have no record of how many calls a heatwave week brought.