The booking says treatment. The technician reaches the property and finds an unidentified sign, a locked crawlspace, and nobody authorized to approve more work. Pest control customer screening should stop that failed dispatch before the truck leaves.
Screen the job, not the caller. Turn each lead into one of four outcomes: treatment, inspection, information hold, or decline.
Set four dispatch outcomes before taking the call
Give office staff four clear booking choices. Do not let them use “service call” as a catch-all. The appointment type controls the technician, time allowance, preparation instructions, job notes, and price.
Book treatment only when the work is defined
Book a treatment visit when you know the reported problem area, the requested service fits your business, access is arranged, preparation is confirmed, and the payer is named.
Keep the customer’s report separate from your finding. “Customer reports insects beside the kitchen sink” is an observation. It is not a confirmed identification.
A treatment booking also needs a boundary. Name the rooms, units, exterior areas, or structures included. If the caller reports activity in an apartment and a shared hallway, confirm who controls each area before dispatch.
Book an inspection when important facts remain unknown
Book an inspection when the identity, source, extent, entry point, or site condition is still unknown. Do the same when concealed spaces, several units, shared areas, or neighboring structures may be involved.
An inspection is not a treatment booking with vague notes. Give it its own scope. State which areas the technician will inspect, what access the customer must provide, and what the visit does not include.
A photo can support triage. It may show a damaged package, droppings, an insect, or the room where activity occurred. It may not show what is behind the cabinet, inside the wall, or under the floor.
Put the lead on an information hold when one fact blocks dispatch
Use an information hold when one missing item prevents a workable appointment. That item might be a unit number, approval email, key arrangement, preparation confirmation, photo, purchase order, or payer name.
Name the person responsible for clearing the hold. Give that person one concrete action. For example: “Property manager to confirm access to the shared hallway and email approval for the inspection.”
Do not reserve technician time while the lead is on hold. A hold without an owner and next action is just a forgotten call note.
Decline work outside your boundary
Decline work that sits outside your services, training, licensed scope, or safe operating limits. Do not dispatch a normal treatment visit and hope the technician can make it work.
State the boundary plainly. Do not debate the customer’s diagnosis or promise that another contractor will accept the job.
Write these four outcomes beside the phone before taking the next lead. Office staff should choose one before they touch the schedule.
Ask pest inspection questions without diagnosing the pest
Good pest inspection questions locate the reported activity. They do not turn office staff into field inspectors.
Ask the customer:
- What did you see, hear, smell, or find?
- Where exactly did you notice it?
- When did it start?
- When does it usually happen?
- How often has it happened?
- Which rooms, units, exterior areas, or structures may be affected?
- Is there visible damage, droppings, nesting material, staining, or another sign?
- Can you send a clear photo of the sign and the surrounding area?
- Has anyone used a product, trap, bait, or other treatment there?
- When was that done, and what was used if known?
Record the customer’s words where they help the technician. “Scratching above the bedroom ceiling after dark” is useful. Replacing it with an unconfirmed pest name is not.
Keep three fields separate in the job record:
- Customer-reported signs.
- Office booking assumptions.
- Technician findings.
The technician’s findings should replace assumptions after the inspection. Do not leave the invoice or follow-up plan tied to a guess made during the first call.
Build a pest control customer screening record
A pest customer intake record should expose missing facts. Long call transcripts bury them.
Use separate fields for the service address, reported signs, affected area, appointment type, authority, access, preparation, site conditions, payment, and open questions. Mark an answer as unknown when it is unknown. An empty field can look like somebody checked it.
Record the state and ZIP code with the service address. The state matters when you check licensing and permitted service scope.
Use this copy-ready structure:
Caller name: Caller phone and email: Preferred contact method: Caller relationship to property: Service address: City: State: ZIP code: Property type: Occupant: Site contact: Access contact: Work approver: Change order approver: Payer and billing contact: Purchase order or work authorization required: Customer-reported signs: Exact rooms, units, shared areas, or exterior areas: Date first noticed: Timing and frequency: Photos or records supplied: Previous treatment, product, and date if known: Keys, escorts, sign-in, or entry window: Locked or restricted areas: Crawlspace, attic, roof, or ladder access: Pets, food areas, and other preparation factors: Preparation required: Person responsible for preparation: Preparation confirmation status: Known site hazards or operating restrictions: Requested appointment: Dispatch outcome: Included scope: Assumptions: Exclusions: Open questions: Owner of each open question: Next action: Technician instructions: Field findings: Further work approval route:
Cut fields that never affect a decision. Add a field when the same missing fact causes repeat failures. Keep the form short enough to use and strict enough to protect technician time.
Confirm who controls the property, work, and payment
The caller, occupant, access contact, work approver, change order approver, and payer may all be different people. Name each role.
Ask who can authorize entry into every booked area. Then ask who can approve treatment, extra work, and payment. A tenant may control the unit but not the shared hallway. A store employee may open the door but lack authority to approve work.
For apartments and managed properties, separate private units from shared spaces. Record the unit number, hallway, utility room, trash area, roof space, basement, or exterior zone involved. Do not write “whole building” unless the appointment actually covers the whole building.
For commercial sites, ask whether the customer requires a named approver, work authorization, purchase order, site sign-in, escort, or separate billing contact. These are customer requirements, not universal rules. Record the ones that apply to that account.
Stop the booking when authority is disputed. Do the same when two parties each say the other one must pay. Resolve the approval route before reserving the visit.
If the account moves into planned repeat service, carry the approved scope, payer, and billing contact into the recurring pest treatment invoice guide. The invoice should follow the agreement already in the job record.
Check access, preparation, and site conditions
A treatment can fail even when the problem is clear. The cabinet is full. Food is uncovered. The dog is loose. The technician cannot enter the attic. Check the physical job before dispatch.
Ask about keys, alarm instructions, locked rooms, crawlspaces, attics, basements, roofs, loading docks, parking limits, sign-in rules, escorts, and working-hour restrictions. Match every included area to an access plan.
Ask what customer preparation the selected service requires. Name the person who will complete it. Then record whether that person has confirmed the work will be done before arrival.
Do not treat sent instructions as confirmed preparation. If cleared cabinets, protected food, secured pets, or an empty work area are required, get a direct answer.
One common failure is simple. The office books treatment, but the technician arrives to find none of the required preparation completed. The technician must then decide whether a limited inspection is possible or whether the visit stops. Give the technician that boundary before arrival.
Record known electrical, structural, chemical, biological, access, and operating hazards. Send uncertain conditions to a qualified supervisor for review. Office staff should not decide that a damaged structure, suspected exposure, or immediate danger is safe.
Do not route an emergency or suspected exposure report as a routine pest appointment. Tell the caller to use the proper emergency or medical route. Do not give medical advice.
Add a United States licensing and workplace-safety stop
Capture the service state before assigning the job. For questions about pesticide applicator licensing, business scope, or the type of pest work your business can perform, check the pesticide applicator licensing body responsible for that state. Write down the answer in your standing compliance record and apply it to the booking gate.
Do not guess at license classes, fees, training rules, or permitted work. State rules can control whether the requested service belongs in your normal schedule, needs a differently qualified person, or must be declined.
Keep business registration and tax checks out of customer intake. Those belong in your standing business records. Use your secretary of state for business-registration questions and the IRS (opens in a new tab) for EIN and federal tax questions.
Escalate employee workplace hazards through your supervisor. Use OSHA (opens in a new tab) only for workplace-safety requirements. OSHA does not answer customer medical questions or pesticide licensing questions.
Add a visible “license or safety review required” status to the dispatch record. Do not hide the stop inside general notes.
Use a pest control lead checklist to choose the appointment
The pest control lead checklist needs to produce a decision. Run the lead through these gates in order:
- Problem: Are the reported signs and affected areas specific enough for the selected appointment?
- Appointment: Is this treatment, inspection, information hold, or decline?
- Service fit: Is the requested work inside your services, training, and licensed scope?
- Authority: Can the right people approve entry, work, extra work, and payment?
- Access: Can the technician reach every included area?
- Readiness: Has required preparation been assigned and confirmed?
- Site conditions: Have hazards and operating restrictions been recorded and reviewed?
- Payment: Is the payer named, and are any purchase-order or authorization requirements clear?
- Handoff: Can the technician tell facts from assumptions and open questions?
A failed gate needs an owner. If access is missing, name the access contact. If approval is missing, name the approver. If the service boundary is uncertain, assign the review to a qualified supervisor.
Do not let urgency bypass the gate. A customer asking for immediate treatment has not supplied authority, access, or a defined scope merely by wanting a fast appointment.
Turn qualified pest customer intake into scope before price
Choose the appointment first. Cost it second.
When the pest, source, extent, or site condition remains unknown, scope and price an inspection. State the areas to be inspected, the access required, the records or findings to be supplied, and whether treatment is excluded.
After the scope is defined, build the treatment price from your expected labor, materials, allocated overhead, and markup. Use your own cost records. Do not publish or copy a market rate. The job-pricing guide explains how to turn job cost into a selling price.
Write the quote around concrete boundaries:
- Affected rooms, units, structures, or exterior areas.
- Included inspection or treatment work.
- Customer preparation.
- Access assumptions.
- Areas and work excluded.
- Follow-up boundary.
- Approval route for extra work.
An exclusion must name the boundary. “Other work excluded” tells nobody what happens when activity is found outside the booked kitchen, unit, or storage room.
If inspection is the real first job, say so. The same discipline appears in the roof leak inspection and estimate process: inspect the uncertain condition before promising a repair scope.
Worked example: carry exclusions into the change order
Oak Street is the house electrical example, not a pest control price or rate card.
R. Chen’s Quote Q-1847 at 14 Oak Street covered a bathroom exhaust fan and four LED downlights for 1,105 sample currency units. The ceiling was lined, and chasing was excluded. Extra cable and chasing were approved on site as a 160 change order. Invoice INV-1847 was 1,265.
The control matters. The quote named the exclusion. The change was found on site. The customer approved the 160 change order before the extra work continued.
Use the same rule when a pest technician finds activity beyond the booked area. Stop. Record the finding. Reach the authorized person. Approve a change order or book another visit before expanding the work.
Do not calculate profit using the 1,265 invoice and the original job cost. The costs of the change order are not supplied, so that calculation would be false.
Give the technician a door-ready dispatch brief
The technician should not have to read a call transcript in the driveway. Put the decision at the top of the work order.
Show:
- The booked outcome and included area.
- The customer-reported signs.
- What remains unidentified or unconfirmed.
- The access contact and entry instructions.
- Preparation requirements and confirmation status.
- Known site hazards and restrictions.
- The work and change order approvers.
- The payer and any purchase-order requirement.
- Open questions and the person responsible for each.
Make the stop boundaries visible. If the booking covers one unit but the caller also reported activity in a shared hallway, say that the common area lacks authorization. If extra activity is found outside the scope, tell the technician who can approve a change order.
After the visit, replace intake assumptions with field findings. Carry the approved scope into the work order, quote, change order, and invoice. A clean closeout follows the same record discipline used in the electrician job closeout checklist.
Yes Foreman can hold the customer details, approved scope, dispatch notes, and job documents against the same job. Use it after your booking rules are set. The software should carry the decision, not make an unclear lead look ready.
Common questions
What booking outcomes should pest control customer screening produce?
Use treatment, inspection, information hold, or decline. Pick one before assigning a technician. If office staff cannot choose, the lead still has an unresolved gate.
What information should a pest control technician receive before dispatch?
Give the technician the reported signs, affected area, booked appointment, access plan, preparation status, hazards, approvers, payer, and open questions. Mark every unconfirmed detail as an assumption rather than a fact.
Can customer photos replace a pest inspection?
No. Photos can help you choose the appointment and show where the customer noticed a sign. They may not reveal the source, extent, entry point, or conditions in concealed spaces.
When should a pest control lead be declined?
Decline when the work falls outside your services, training, licensed scope, or safe operating boundary. Also decline when the customer expects excluded work and will not accept the boundary.
Pest control customer screening works when the schedule follows the record. Do not book first and ask the technician to solve authority, access, preparation, and scope at the door.
Take the next unbooked lead. Run it through the four outcomes, assign an owner to every failed gate, and reserve technician time only after the appointment can be completed.