“Elevator down. Call customer back.”

A vague message creates more work for everyone.

No technician wants to wake up at 1:30 a.m. to a message that says, “Elevator down at Main Tower. Call customer back.”

Now they have to call again for the address, find out which car is involved, ask what the elevator is doing, and track down an onsite contact.

A useful dispatch message includes

• Location: building address and elevator or car identification.
• Problem: what the caller observed, in plain language.
• Contact: caller name, callback number, and onsite contact.
• Access: any approved entry instructions your procedure requires.

Run the “no callback needed” test

Give a recent dispatch message to a technician who did not take the original call. Ask whether they know where to go, which elevator is involved, what was reported, who is onsite, and how to gain access. If they have to call the customer for basic information before leaving, the intake process needs another field or a clearer question.

Field note. Put dispatch details in the same order every time: location, elevator, problem, contact, access, and next action. A predictable message is easier to scan when someone has just been awakened. It also makes missing information easier for the dispatcher to spot before the message is sent.

The answering team should fit your workflow, not force your technicians to work around someone else’s script.