field-service-intake
Commercial kitchen hood-cleaning calls: schedule access without guessing at service scope
A phone-intake workflow for restaurant exhaust-cleaning requests, access constraints, shutdown timing, and conditions that need technical review.
# Commercial kitchen hood-cleaning calls: schedule access without guessing at service scope
*October 6, 2026*
A restaurant manager may call about a routine cleaning, a failed inspection, grease found near a fan, or an exhaust system that is no longer working as expected. Those calls share a phone number, but they do not share the same next step. A receptionist can gather the scheduling facts and direct observations that a service coordinator needs. The receptionist should not decide whether the system is safe, compliant, or ready to operate.
The useful dividing line is simple: reception owns an accurate request and an accepted handoff. A qualified service or safety owner decides scope and gives technical instructions.
Start with the operating situation
Confirm the business name, service address, caller role, and a callback number. Ask whether the location is open, closed, preparing to open, or already shut down because of the reported condition. That answer affects both urgency and access, but it does not prove that an emergency exists or that normal operations are safe.
Let the caller describe why they called before working through a form. A request for periodic cleaning needs different follow-up than a report of smoke, active fire, an electrical smell, loose metal, or grease dripping near cooking equipment. If the business's approved emergency script applies, use it immediately. Do not bury an urgent observation beneath questions about invoice numbers or preferred appointment dates.
Record the caller's words. "Grease is dripping from the edge above the fryer" is useful. "Hazardous buildup" is a conclusion unless an authorized inspector or technician has already documented it.
Identify the equipment without asking for unsafe access
The service coordinator will usually need to know which kitchen and exhaust line are involved. Capture the hood location, appliances beneath it, number of hood sections if the caller knows, fan or system identifier, and the last service reference available in the account. Ask whether the caller can see an inspection sticker or prior report from an ordinary standing position.
Do not ask anyone to climb, remove filters, open electrical panels, reach into ductwork, or go onto a roof for the sake of a phone estimate. If a label cannot be read safely, mark it unknown. A missing identifier is a planning constraint, not a reason to improvise instructions.
Photos may help the qualified coordinator, but only through the company's approved channel and only when the caller can take them without approaching heat, moving equipment, electrical components, or an unsafe surface. The intake note should say what the image is meant to show and who received it. General call notes are a poor place for access codes or other protected building details.
Build the access plan around the kitchen's real schedule
Hood work can affect food preparation, staff movement, alarms, keys, roof access, and the availability of a responsible site contact. Ask for the hours when cooking stops, the earliest access time, the required completion or reopening time, and whether another contractor or landlord controls part of the route.
Capture loading restrictions, parking instructions, locked-door ownership, roof-access ownership, elevator rules, and any required check-in. Keep door codes and keys in the approved secure system. If the restaurant is inside a hotel, mall, hospital, or shared commercial building, identify both the restaurant contact and the property contact. One may approve the work while the other controls entry.
Avoid promising that a crew can finish between closing and breakfast service. The coordinator must compare the request with system size, condition, staffing, travel, and the provider's work method. Reception can say that the requested window has been recorded and is awaiting confirmation.
Keep cleaning, repair, and inspection requests separate
Callers often combine several needs. A manager may want routine cleaning, a fan repaired, a certificate sent to a landlord, and a deficiency on an earlier report reviewed. Create distinct request lines when different owners handle them. Link the records so the customer does not have to retell the story, but do not mark repair or inspection questions as resolved by booking a cleaning visit.
Ask which document the caller needs and why. Record a report number, inspection date, or landlord request if supplied. Do not state that cleaning will satisfy an insurer, fire authority, landlord, or local requirement. The service provider's authorized reviewer must decide what it can document and which service applies.
The OSHA walking-working surfaces standard is useful background for the provider's access and workplace procedures. Reception should use the company's approved access questions rather than interpreting the standard during a call.
Route conditions that do not belong in routine scheduling
The business should define the observations that trigger an urgent supervisor, technician, or emergency path. Examples for the policy owner to consider include active fire, smoke, a reported gas odor, sparking, a loose overhead component, an injury, or a caller who says the site is being evacuated. Reception follows the approved script and records the time, location, observation, and route used.
Do not tell the caller to restart a fan, remove filters, clean hot equipment, silence an alarm, or continue cooking. Do not announce that a system is safe because the symptom stopped. When a caller asks what to do with the equipment, transfer or escalate to the role authorized to answer.
For less immediate concerns, distinguish the facts carefully. "Fan did not start when staff expected" differs from "fan has failed." "Dark residue is visible on a wall" differs from a diagnosis of where it came from. Clear notes let the technician prepare without turning reception into remote troubleshooting.
Require an owner to accept the job
A booking request is not confirmed merely because reception sent a message. Record the destination queue, submission time, named or monitored owner, requested service window, and acceptance status. If nobody accepts within the company's approved interval, use the backup route.
Customer-facing status should stay precise. "Requested," "under technical review," "scheduled," and "technician dispatched" mean different things. If a site contact must approve an estimate or provide roof access, leave that dependency open rather than calling the appointment complete.
Quality reviews should sample routine bookings, multi-tenant access problems, mixed cleaning-and-repair calls, urgent observations, and jobs that failed at the door. Check whether the agent captured the operating schedule, protected entry details, separated direct observations from conclusions, and obtained real acceptance.
The final intake record should let a coordinator answer four practical questions: where is the system, what is the customer asking for, when and how can a crew enter, and what remains undecided? That is enough for reception to do useful work without pretending to scope the job.
Need a call workflow for service windows, access details, and technical escalation? Contact Virtual Assistant Call Center to discuss your intake process.