Separate request types without diagnosing

Build a simple intake list: new damage inquiry, existing-customer update, scheduled-visit question and supplier or crew call. Capture the property address, callback details, the caller's description and any access concern. Record observations as reported rather than declaring the roof safe or diagnosing damage over the phone.

The phone team should use an owner-approved emergency instruction, including directing an immediate threat to the appropriate emergency service. A roofing inquiry queue is not an emergency response service.

Keep capacity visible to the answering team

Give the team a current view of service areas, inspection availability and who may authorize changes. If your crew is unavailable in a neighborhood, the answer should reflect that rather than creating a false appointment.

  • Who updates available visit windows?
  • Who receives priority review requests?
  • What may the representative promise?
  • What is the fallback if the assigned person cannot be reached?

Confirm receiving-team availability separately from phone-system forwarding.

Link repeat calls to the original request

A homeowner may call again for an update while a spouse submits a form. Search by property and contact details before opening another job. Keep separate properties separate, even when the caller owns both.

Use a short update format: what has been recorded, who owns the next step and when the team expects to update the caller. If the timing changes, record the change and the communication. Do not present an estimate target as a guaranteed arrival.

Run a short surge rehearsal

Use three fictional requests: a new roof inquiry, a customer waiting for an update and a failed transfer. Have the office process them while the scheduler is occupied. Check whether every request reaches one owner and whether the customer-facing answer matches current capacity.

After a real surge, review unassigned requests and aging estimates before judging pickup totals. A queue that looks empty because records were never created is not a resolved queue.

Confirm storm coverage before relying on it

Agree on staffing, coverage hours, volume limits and escalation responsibilities in advance. Weather alerts, answering capacity and dispatch are different capabilities; availability of one does not establish the others.

Discuss your storm call workflow with LeanLine. Ask which parts can be supported under the current plan and bring your approved routing and customer-update instructions.