How Do You Document a Propane Service Callback?
How Do You Document a Propane Service Callback?
Give the return visit its own record. Reference the earlier job. Record the customer’s new report, what the returning tech found and the work done. Note any follow-up. Keep the first visit true to what happened then.
Keep the two visits distinguishable
We suggest starting the callback record with the earlier job reference. Explain why staff returned. Name who reported the concern and when. Label the customer’s words as their report. Keep the returning employee’s findings separate.
For a possible hazard, follow your established safety response. A software entry does not decide how urgent it is. It does not decide equipment use or the field steps.
Compare the available history and evidence tools
Tank Spotter lists work order history. Ask to open the first visit while you review the return job.
Its account tools list customer activity/history. Ask where the office would find the report that led to the callback.
The service catalog lists Parts/Reorder Lists. If the job needs a part, check how staff record that. Can they tell a part still needed from one used?
That catalog also lists photo/document uploads. Ask to see the return visit’s evidence apart from the first job’s files.
Decide what closes this particular return
Have the service lead say what they must review to close the callback. In a sample case, record the second visit’s outcome. Name who owns any open work. Leave an uncertain cause uncertain. The callback label should not assign blame for the first result.
Questions and answers
Does work order history mean callbacks link automatically?
Ask the product team to show how your setup relates the visits. History alone does not promise automatic callback links. It does not settle warranty or return-visit billing rules.
Book a demo with an original job and its return visit; ask the office to explain both from the records.
Related