Handle calls during an unexpected closure

The decision this workflow supports

When a location unexpectedly closes, callers may have travel plans or an existing arrangement. The answering flow should communicate the approved status and collect a staff-review request without speculating about the cause or promising compensation.

Put the review process in place

Let the duty manager publish a short dated closure statement. Separate general information calls from requests involving an existing booking or event. Give the reviewing staff member the original arrangement reference where the caller has one, but do not change that arrangement automatically.

Worked example for your team

During a fictional closure drill, one person asks whether dinner is running and another says they already arranged a private event. The first needs the approved public notice. The second needs a manager-review request linked to the existing arrangement, not a general reply copied from the notice. Ask the reviewer to identify the event and contact the organizer through the approved process. Do not include a guessed reopening time in either response. When the owner issues new information, replace the old notice and review any still-open requests affected by it.

Sample wording to approve

“The restaurant has posted a closure notice for this service. I can record a request for the team about your existing arrangement; they will confirm the available next steps.” This wording is a draft for the restaurant owner to approve before use.

Fields for the staff handoff

Staff need affected date, arrangement type, caller-supplied reference, preferred contact, and closure notice version. Mark uncertain details explicitly and keep the requested action separate from anything restaurant staff have already confirmed.

Acceptance tests before use

The greeting uses the approved closure statement. A refund question receives no financial promise. An existing-event inquiry reaches the manager responsible for that event. Record the observed result, assign any mismatch, and repeat the affected scenario after correction.

Related guides