Published August 13, 2026
A storm can turn a tree company's ordinary phone queue into a moving map of hazards. One caller has a limb resting on a detached garage. Another cannot leave a driveway. A third sees branches tangled near service wires, while a fourth wants a quote for cleanup next month. All four may say the job is an emergency. The person answering cannot inspect the site, declare a tree safe, or promise which crew will arrive first. They can still gather the facts that let an authorized operator make that decision quickly.
Good storm intake is a discipline of separation. It distinguishes danger to people from damage to property, public access from private inconvenience, utility involvement from work the tree company can control, and a reported condition from the caller's theory about it. The resulting record should be short enough to scan during a surge and specific enough that the dispatcher does not need to restart the conversation.
Let the caller describe the scene before sorting it
Open with the service address, the caller's name, a reliable callback number, and a plain description of what they can see from a safe location. Ask whether anyone is hurt or in immediate danger. If so, follow the company's emergency script, which may direct the caller to public emergency services. A call agent should never hold someone on the line to complete a property questionnaire while an immediate threat is unfolding.
The first description often contains the best information. Preserve phrases such as “large limb across the only driveway,” “tree leaning toward the occupied bedroom,” or “branches touching a line from the pole.” Do not upgrade them into conclusions such as “tree about to fall” or “electrical line down.” The dispatcher needs observations, not an off-site diagnosis.
Ask where the caller is standing and whether they can remain away from the affected area. Do not ask them to walk beneath a suspended limb, inspect the base of a damaged tree, move branches, test a wire, climb onto a roof, or send close-up photos from an unsafe position. Images can be useful only when the caller can take them without approaching the hazard and the company has an approved, secure way to receive them.
Divide calls by operational consequence
A useful queue has more definition than “emergency” and “not emergency.” The exact labels should match the tree company's staffing and agreements, but four consequences recur after severe weather.
The first is an immediate life-safety report: a person trapped, an active fire, a tree or limb moving toward occupied space, or another condition the company's written policy treats as imminent danger. These calls follow the emergency path and should not depend on whether a crew is available.
The second is a utility conflict. The caller may mention wires, a transformer, a meter, a service drop, a streetlight, or loss of power. Record exactly what is visible and whether the utility has been contacted. Never identify a line as de-energized, advise the caller to touch nearby material, or imply that a tree crew can perform work the utility must first control. The company should define which utility-related calls it accepts, who coordinates clearance, and what its crews require before dispatch.
The third is blocked essential access or serious property exposure. Examples include a tree across the only driveway where a resident must leave for necessary care, a limb that has opened the roof to rain, or debris blocking the entrance used by emergency responders. Capture the access constraint and the caller's immediate need. Do not promise that a crew will make the route passable by a certain time; the field lead must consider travel, equipment, daylight, traffic, and site conditions.
The fourth is scheduled assessment and cleanup. Fallen material resting in a yard, pruning requests, stump work, debris hauling, and insurance estimates may matter greatly without requiring the on-call route. A calm explanation that the request has been placed in the assessment queue is more useful than labeling every storm job urgent and making the queue meaningless.
Treat wires as a boundary, not a detail
Electrical conditions deserve their own visible field in the call record. A caller focused on a damaged fence may mention near the end that a branch also touches a cable. If that fact is buried in narrative, a crew can arrive without the right clearance or coordination.
Ask neutral questions: Are any wires visible near the tree or debris? Is there sparking, arcing, smoke, or a line on the ground? Has the electric utility or public emergency service been notified? Record the answers without guessing what type of wire it is. Cable and telephone lines can resemble power infrastructure to an untrained observer, and all downed lines should be handled according to the company's safety policy.
The call handler should not tell someone that rubber boots, a wooden tool, dry weather, or distance estimated over the phone makes contact safe. Nor should they promise that the tree service will remove material before utility clearance. The correct handoff may involve a utility, municipal authority, fire department, or a specially qualified crew. The approved routing table decides; improvisation does not.
Establish access without encouraging exploration
Crews need to know whether the address is reachable and what equipment may be required. The caller can often provide useful facts from memory: a narrow gate, steep driveway, locked yard, soft ground, septic area, limited street parking, or an alley entrance. Ask whether the affected tree is in the front, rear, side yard, roadway, or a neighboring parcel.
Ownership can be unclear. A trunk may stand on one property while limbs cross another, or a fallen tree may affect a public right-of-way. Capture what the caller believes and the contact information for other known parties, but do not give a legal opinion about ownership, liability, or permission. Dispatch can identify what authorization is needed before work begins.
If the caller is away from the property, note who can provide lawful access and whether animals, tenants, gates, alarms, or building staff are involved. Never recommend leaving a home unlocked or hiding a key. The company should use its normal access and authorization procedure even when the queue is crowded.
Location details help avoid wasted trips. Confirm the municipality and postal code, not just a street name, because storms often affect several nearby towns with similar addresses. Record road closures or entry restrictions the caller reports, while making clear that the information has not been independently verified.
Keep insurance questions inside the tree company's authority
Storm callers frequently ask whether insurance will pay, whether the insurer must approve removal, or whether the company can bill a carrier directly. The answering agent should state only the tree company's approved process. They should not interpret coverage, predict reimbursement, advise the caller to file or avoid a claim, or describe a price as guaranteed.
The intake can capture the insurer's name, claim number, adjuster contact, and whether the caller has been given instructions, if the company genuinely needs those details. Avoid collecting policy documents or sensitive financial information in an ordinary message channel. A claim number does not replace the property owner's authorization, and insurance interest does not determine operational priority.
Document damage in literal terms. “Caller reports limb through shingles above rear bedroom; rain entering” gives the estimator a useful starting point. “Insurance emergency” says almost nothing. Note whether a roofer, utility, municipality, or emergency service has already responded so the dispatcher can coordinate rather than assume.
When callers demand an estimate before a visit, explain the approved assessment process. Storm work depends on variables that a phone conversation cannot settle, including rigging needs, structural loading, equipment position, disposal volume, utility controls, and crew safety. A live call answering service can capture the opportunity and urgency without inventing a scope or price.
Use a storm board that shows changes over time
A static message becomes stale quickly. A tree that was leaning at 6:00 p.m. may be down by 6:30. A blocked drive may reopen, a utility may arrive, or the caller may evacuate. Each update needs a timestamp and source rather than an overwritten description.
The storm board should show address, caller, category, observed condition, people or occupied structures exposed, wire involvement, access limits, outside agencies contacted, dispatcher ownership, and current next action. Related calls from neighbors can be linked to the same event while preserving separate contact and access information.
Duplicate reports sometimes improve the picture. One resident sees the street side; another can see the rear canopy. Merge the event, not the witnesses. Do not expose one caller's name, phone number, schedule, or statements to another caller without permission.
Positive acknowledgment matters during a surge. Sending a text or page does not prove the dispatcher received it. The account plan needs attempt intervals, backup contacts, and a point at which the agent stops cycling through individual crew members and escalates to the designated storm lead. Staff who are operating equipment or driving should not be expected to answer repeated calls.
Set expectations with ranges of process, not arrival promises
Callers deserve a truthful next step. The agent can say that the request has been documented for dispatcher review, identify any action the caller must take under the approved script, and explain how updates are communicated. They should not claim a crew is “on the way” until dispatch confirms it or give a precise arrival time that has not been accepted by field operations.
Avoid broad reassurance. “It should hold until morning” is a risk judgment the agent cannot make. “That type of tree usually survives” is equally misplaced. When the condition changes, the caller should move to a safe location and use the emergency path described in company policy.
Priority may change as information arrives. A routine cleanup can become a blocked-access call; a property-damage report can reveal wire involvement; a high-priority request can be transferred to a utility-led response. Tell callers that routing reflects current reported conditions rather than their position in a simple first-come line.
After the weather clears, review both accepted and declined work. Check whether hazards were prominent, utility facts were visible, access notes helped crews, authorization was clear, and callbacks occurred as promised. Compare the labels used by call agents with the decisions dispatchers actually made. Where they diverge, revise the questions or routing table rather than expecting agents to infer field judgment.
Storm response works when the phone team preserves reality under pressure. A careful intake cannot stabilize a tree or clear a road. It can prevent a dangerous promise, reveal a utility boundary, spare the caller from repeating a frightening account, and give the dispatcher a usable basis for the next decision.
FAQ
Can the call agent decide whether a damaged tree is safe overnight?
No. The agent should record observable conditions, screen for immediate danger under the approved procedure, and route the call to authorized responders without making an arboricultural or structural judgment.
What if the caller says a branch is touching a wire?
Treat wire involvement as a prominent routing fact. Follow the company's utility-conflict procedure, keep the caller away from the area, and never state that a line is safe or de-energized.
Should storm calls be handled strictly in the order received?
Not necessarily. Authorized dispatchers may prioritize current safety, utility controls, essential access, property exposure, crew capability, and travel conditions. The answering team supplies accurate facts and updates rather than deciding field order.