A customer reports insects after treatment and wants somebody back today. The wrong move is to promise another application before checking the job. A pest controller callback process starts with the complaint, then the original scope, then an inspection.
A complaint records what the customer saw. It does not confirm the pest, source or cause. Keep the report, inspection finding and treatment decision separate.
Take the pest service complaint without promising treatment
Office staff set the boundary on the first call. If they promise a free retreatment, the attending pest controller arrives with the decision already made.
Acknowledge the problem. Find the completed job. Explain that the next visit will inspect the reported activity before anybody decides whether more treatment is needed or included.
Record what the customer actually saw
Ask for facts you can put against the original job:
- What did you see?
- Where did you see it?
- When did you first notice it after the treatment?
- Has it happened once or several times?
- Do you have a photo, specimen, trap result or visible damage?
- Has access, occupancy, storage, food handling or moisture changed?
- Who can approve extra work if the finding sits outside the first scope?
Write the customer’s description as given. Small brown insects in a kitchen cupboard is useful. Confirmed stored-product pest is not, unless somebody has identified the evidence.
Record the complaint date, contact, property and original job reference. Do not open an unrelated sales enquiry when the call belongs to completed work.
If the report raises an immediate workplace, access or exposure concern, stop normal dispatch. Give it to the person responsible for the site before sending a tradesperson.
Give the office a fixed inspection-first response
Use a short script:
I have recorded what you found and where you found it. We will check the original treatment record and inspect the current activity before deciding whether another treatment is needed or included. We will confirm the next step after that inspection.
That response takes the pest service complaint seriously without making an open-ended promise.
Pull the original scope before booking a return visit
Find the accepted quote or service agreement first. Then pull the treatment record, preparation instructions, access notes, exclusions, photographs, customer messages and any promised follow-up.
Check these points:
- The target pest
- The property, flat or parts of the site covered
- The areas treated
- The agreed treatment steps
- The customer’s preparation duties
- Excluded or inaccessible areas
- Monitoring or follow-up already agreed
- The person allowed to approve work
Read the first visit notes as a job record, not a defence. Look for what was observed, where treatment took place, which areas could not be reached and what the customer was told to do next. The guide to pest controller treatment records shows how to keep that history usable.
The difference between the report and the accepted scope matters. A customer might report insects in a kitchen cupboard when the original work covered an exterior treatment and the garage. That needs inspection and a scope decision. It is not automatically unfinished work.
Confirm who can authorise work at the property
For a rented flat or managed site, record the tenant, landlord, managing agent and attending contact separately. Do not assume the person who opens the door can approve paid work.
Ask who can authorise work beyond the original area and whether there is an approval limit. Record the answer on the callback. If authority is unclear, inspect only and send the finding to the named decision-maker.
A managing agent may ask for another flat to be treated while the pest controller is already on site. That is another premises and another scope. Do not let convenience replace written authority.
Set the pest controller callback process as inspection only
Book the return as an inspection unless an authorised person has already reviewed the evidence and approved defined treatment work. The work order should tell the attending pest controller what can be done and where to stop.
Include:
- Original job reference
- Complaint date and customer’s description
- Reported pest and location
- Original target pest and treated areas
- Known exclusions and access limits
- Purpose of the visit
- Whether treatment is authorised
- Name of the person who can approve more work
- Required inspection evidence
State the boundary plainly: inspect and report; no treatment unless separately authorised. A work order template for the return visit gives the office a structured brief instead of an address and a vague note.
Use this copy-ready record:
Callback inspection work order Original job reference: [reference] Customer or site: [name and address] Complaint received: [date and time] Customer report: [pest description, location, timing and frequency] Evidence supplied: [photo, specimen, trap result, damage or none] Original target pest: [pest] Original treatment area: [areas] Original exclusions: [areas or work] Original preparation and access notes: [details] Visit purpose: Inspect reported activity and record findings Treatment authorised: [no / defined work only] Inspection boundary: [areas to inspect] Authorised contact: [name and role] Approval limit or restriction: [details] Evidence found: [complete on site] Exact location: [complete on site] Access or condition changes: [complete on site] Classification: [complete after inspection] Next action and date: [complete after decision]
The purpose line matters. It prevents an inspection booking from being treated as automatic permission for a pest treatment callback.
Check COSHH and the work area before authorising a retreatment
A UK workplace retreatment needs a current job check before treatment is put on the work order. Conditions may have changed since the first visit.
Check the proposed treatment, product, access and work area. Review the job-specific risk information and COSHH assessment. Confirm that the attending pest controller has the right instructions and can work within the approved area.
Do not copy the first visit’s check without looking at the current site. Occupancy may have changed. Stock may block access. Another trade may be working nearby. The customer may be asking for treatment in a food area that was not part of the first job.
Use the Health and Safety Executive’s COSHH guidance (opens in a new tab) for workplace controls before authorising the work. For a biocidal product, check the Health and Safety Executive’s biocides guidance (opens in a new tab) and the product authorisation for the territory where it will be used. Great Britain uses the GB Biocidal Products Regulation. Northern Ireland uses the EU Biocidal Products Regulation.
This check comes before dispatching an approved retreatment. It is not a box to complete after the product has been used.
Run the callback inspection on evidence
The pest controller is there to inspect. Not to defend the previous work. Not to accept blame before seeing the site. Not to apply more product because the customer expects it.
Start at the reported location. Then inspect the nearby source areas and routes that could explain the activity.
Separate the report from the finding
The inspection note should show two different things:
- Customer report: what the customer says happened
- Site finding: what the pest controller observed or collected
Record the exact activity location. Add photographs, specimens, trap results, droppings, damage, harbourage or entry evidence where found. A note saying the same problem remains is too weak to support another treatment.
If the reported pest cannot be confirmed, do not choose a treatment by guesswork. Set monitoring points or ask the customer to retain a specimen. Name each monitoring location and the evidence that will trigger a review.
Compare the site with the first visit
Check whether access, preparation, sanitation, moisture, food sources, storage, entry points, occupancy or nearby activity has changed.
Record facts. Avoid blame. Write access to the rear cupboard blocked by stored stock, not customer failed to cooperate. State whether the area was accessible during the first visit and whether the obstruction prevents inspection or treatment now.
Photograph conditions that affect the decision. Name every area that could not be inspected and why. The next person should not have to guess what was behind the words limited access.
Classify each finding before choosing more work
Each distinct finding from the callback inspection needs one clear classification. One visit may show activity in the original room and a different pest elsewhere. Classify both, then make a separate scope decision for each one.
| Classification | What the finding means | What to do next |
|---|---|---|
| Existing planned follow-up | The evidence fits the original pest, area and documented treatment plan | Check the accepted terms, then follow the agreed monitoring or review step |
| Incomplete original work | An included area or treatment step appears to have been missed | Record the finding, then check the accepted terms before deciding whether the correction is included |
| Customer or site action needed | Preparation, access, repair or another site action is blocking the next step | Record the action, owner and review date |
| Changed site condition | Access, moisture, occupancy, storage or another condition has changed | Decide whether the change needs a new scope |
| Different pest or new area | The evidence concerns another pest, room, flat, premises or untreated area | Stop and check whether the work needs a variation or a new quote and job record |
| No supporting evidence | The inspection cannot confirm enough evidence for treatment | Set monitoring or close the complaint with the finding recorded |
Do not use expected activity as a vague reason to dismiss the customer. Point to the original treatment plan, service terms and recorded evidence. If those records require another step, issue that step.
Give monitoring an owner and a date
Wait and see is not an instruction. A monitoring action needs a location, evidence to watch for, responsible person and review date.
Write which trap or observation point matters. Tell the customer what to retain or photograph. State who will review the result and when. If no evidence appears by the review, record whether the complaint closes or monitoring continues under a new instruction.
Decide whether further treatment is included
Match the inspection finding to the accepted quote or service agreement. Do not decide from the customer’s expectation alone.
An agreed step that was missed may be an included correction. A retreatment is included only where the accepted terms cover it. Another pest, another flat, a new room or added preparation work needs its own scope.
Keep the possible decisions separate:
- Inspection completed with no treatment
- Included correction
- Included retreatment
- Monitoring
- Customer or site action required
- Separately paid work
- Closure with no supporting evidence
If more work is included, name the pest, area and treatment boundary on a new work order. Do not send the pest controller back with a note that only says retreat.
Write a variation for work outside the first scope
Stop when the requested work moves outside the accepted scope. Describe the additional pest, flat, room, treatment, preparation, exclusions and price. Get written approval from the authorised contact before starting.
The Oak Street house example is electrical, but the control is the same. Quote Q-1847 for R. Chen at 14 Oak Street covered a bathroom exhaust fan and four LED downlights. The ceiling was lined and chasing was excluded. The quote was 1,105, the approved variation was 160, and invoice INV-1847 was 1,265. All figures are sample currency units, not pest-control rates.
Use that discipline when a callback reveals another pest or area. If the added work changes the accepted job, write a variation. If it covers another flat, premises or separately commissioned job, issue a new quote and job record. Get written approval before issuing the treatment work order.
If the customer declines the added work, record the decision. Close the inspection or leave one dated customer action. Do not leave the job sitting under an undefined callback status.
Complete and cost the approved work
Once treatment is approved, issue a work order that names the target pest, treatment area, planned work, preparation status and stop conditions.
A stop condition tells the pest controller not to drift into unapproved work. Stop if the evidence points to a different pest. Stop if the authorised area cannot be accessed. Stop if somebody asks for another flat or common area to be treated.
After the visit, record:
- Labour and travel
- Materials used
- Treatment locations and details
- Evidence and observations
- Areas not completed
- Customer instructions
- Monitoring points
- Next action and date
Put included inspection, travel, labour, materials and rework against the original job. That cost tracking shows what the first job actually took to complete. It also exposes loose scopes, missed access questions and repeated preparation problems.
Keep separately authorised work tied to its own variation and invoice line. Do not use income from new work to hide the cost of an included return visit. The shared guide to job costing for completed work explains how to assign actual costs to the job that caused them.
Send one clear callback decision
The customer should receive one written outcome after the inspection. State what was reported, what was found, how the finding was classified and what happens next.
Name any included work. Name excluded or separately priced work. If the customer must provide access, remove stock, repair an entry point or monitor a location, assign that action and give it a date.
For closure, the pest controller callback process should record that the inspection did not find enough supporting evidence for treatment. Add any monitoring result and explain whether the job is closed or waiting for a defined review. Do not write resolved unless the record shows what resolved means.