A service-business phone intake workflow

Identify the job before offering a visit

Create a service request ticket that separates requested work, site details, access constraints, schedule preference, and dispatch review. The ticket status should say inquiry, needs review, ready to schedule, scheduled, or closed.

Build a service request ticket

Capture caller name, callback number, service address, property or equipment type, symptom in caller’s words, when it began, current condition, safety concern, prior job number, access contact, pets or site constraints, preferred window, service-area result, owner, and next action.

Reserve estimates and diagnosis for experts

An intake assistant may describe published services and gather job facts. They must not diagnose, instruct risky repairs, guarantee technician arrival, quote an unapproved price, declare warranty coverage, or mark a job dispatch-ready when required review is missing.

Gather dispatch facts safely

Repeat the symptom without translating it into a diagnosis. “Unit makes a grinding sound when starting” gives a technician better source information than an unsupported component failure label.

Handle hazards and coverage uncertainty

Reports of immediate danger use the approved emergency guidance. Out-of-area requests, uncertain equipment coverage, landlord or tenant authority questions, and unavailable appointment capacity go to named review queues.

Review dispatch readiness

Inspect tickets ready on first review, missing dispatch fields, service-area corrections, schedule changes, duplicate jobs, exception age, and callback promises met. Separate intake quality from technician diagnosis and job completion.

Field-test representative jobs

Use a routine maintenance request, an intermittent failure, a caller outside the service area, and a possible hazard. Include one tenant without clear authorization and verify that the workflow does not assume permission.