“Heating broken, please call urgently.” That is the entire enquiry. The situation is obvious to the sender. The contractor still lacks the property, asset, symptoms, availability and whether water is escaping. The first call gathers details, the second clarifies access, the third moves the appointment. This is not a communication problem. It is an incomplete intake process

A case from dispatch

A property manager reports a failed heating system at 6:40 a.m. The system recognises the registered site, asks which part of the building is affected and offers three observable conditions: no heat, fault display, or escaping liquid. Escaping liquid triggers an immediate safety instruction and alerts the standby team. A fault display prompts a photograph of the panel

At 6:43, dispatch receives the message together with the contract, asset, last service, on site contact, access note and an initial priority. A person still decides how to respond, but now decides with a complete picture

Urgency is not a feeling

A red “very urgent” button almost guarantees that many cases become red. Observable criteria are better: danger to people, active water escape, complete operational failure, number of units affected and an available workaround. The system can use these to suggest a priority

The suggestion remains open to correction. An old asset with a known warning may be less critical than the wording suggests. Every priority change receives a reason. Later, the team can test whether the rules match reality

Record the access details for each location

A campus, industrial site or housing complex needs building, entrance, floor, room and sometimes an asset identifier. A map position helps but does not replace access instructions. GPS can be inaccurate and rarely shows which gate an engineer should use

Location data from a photograph should not be accepted silently. Metadata may be absent, wrong or reveal a private place. If coordinates are needed, the form should show the detected position and ask for confirmation

Photographs must answer a question

“Please upload a photo” often produces a blurred wide shot. Specific requests deliver better evidence: the complete rating plate, a close view of the fault code, an overview of the installation. Short examples help more than long instructions. A brief video may suit some damage, but file size and privacy mean it should be requested deliberately

The original remains available while an optimised preview accelerates dispatch. Time, upload state and case association are recorded. The article on upload forms explains the security requirements for this intake

Mobile first means interruptible

A report begins in a basement, on a roof or beside a machine. Large controls, camera access and plain language are essential. So is a saved draft when a call arrives or the connection drops. Photographs already transferred should not need to be sent again

After submission, the system shows the case number, recorded priority and next step. A dangerous situation does not receive the normal response message; it receives the defined emergency route. A digital form must not create false reassurance

The internal handover in nine fields

  • unambiguous location and access route
  • affected asset or service type
  • observed symptom rather than an assumed diagnosis
  • safety indicators
  • scale and affected use
  • photo or video with a specific purpose
  • on site contact and availability
  • contract reference and preferred time window
  • initial priority with a reason

What to measure after four weeks

The useful measures are calls required before dispatch, wrongly prioritised visits, failed attendance and time to the first professional decision. A high abandonment rate may indicate too many questions. Repeated questions about the same field show that its wording does not match customer language

A good enquiry system replaces neither expertise nor an emergency service. It puts observations into a form that lets professionals reach the right decision earlier