Part of our guide to Run your business from chat: a practical guide to chat-first operations
On this page · 6 sections
A voice note can be a good record of what a tradesperson remembers and a poor instruction for someone who was never on site. “All good, needs the other one before Friday” means something beside the job. By the time the office listens, nobody knows which part, who requested it or whether Friday is a promise. Ask the office to show three recent notes that required a callback. Use the missing details to design the new handover.
Start with the question the office asks every afternoon
Choose one job type first. An inspection, a repair and a quotation visit end with different decisions. For an inspection you may need observations and photographs. For a repair you may need a parts request and the reason the job remains open. For a quotation visit you may need an estimator and a missing measurement. One form asking every possible question makes the site team less likely to use it.
Make the handover short enough to dictate once the vehicle is parked or the job has reached a suitable stopping point. A worker who has to negotiate a long dialogue to record a simple observation will revert to a text message. Allow the office to request one missing detail afterwards. The aim is a usable first handover, with uncertainties visible to the person able to resolve them.
Dictate facts, requests and promises separately
Sample site note: “Job J17, rear unit. I saw the existing fitting and took two photos. The tenant asked whether the matching fitting could be supplied. I have not checked stock or price. The owner wants an answer by Thursday afternoon. Mia in the office to ask the supplier and call the owner once the estimator checks the options.”
The office now has an observation, a request and a deadline for a response. There is no promise that a part will arrive by Thursday. Ask the assistant to preserve that distinction. If the customer asked whether something was possible, the handover should use the same degree of certainty. Changing “asked about” to “approved” can create a job nobody authorised.
| Site input | Handover field | What the office should do |
|---|---|---|
| Existing fitting seen in rear unit | Observation, location and job reference | Attach it to the right job |
| Two photos taken | Evidence expected | Check both images arrived and are readable |
| Matching part requested | Customer preference | Ask supplier for availability and alternatives |
| Owner wants an answer Thursday | Callback due | Assign a person to respond, leaving the installation date open |
Deal with missing photos and similar addresses
Use a job reference the office can search independently of the conversation. Site names can be surprisingly alike. The office might have a job on a street and another on a nearby road with the same name. The person on site may also be talking about the tenant while the account belongs to the owner. Ask the assistant to flag conflicts before posting the note to a customer record.
Test what happens when a photo fails to upload. The draft should say that a photo was mentioned but has not arrived. A line saying “photos attached” becomes misleading when the only evidence is somebody saying they took them. Ask the office to open the attachment from the job record before assigning the estimator. A missing image discovered at the supplier counter costs more than a short check at handover.
Give unclear measurements the same treatment. If the note says “about a metre”, keep the estimate and its uncertainty together. Do not turn it into a precise cut list. If the next decision requires a confirmed measurement, name the person who must obtain it. The draft can still be useful for reserving internal time or preparing questions while that detail remains open.
Put the right person at the end of the handover
Ask one office colleague to read the draft as if tomorrow were their first day covering dispatch. Can they tell whether the next action is theirs, the estimator's or the supplier's? “Follow up” can leave three people waiting. “Mia to request availability from the supplier before the estimator approves the options” identifies both the first owner and the dependency that follows.
Have the office reply with a short receipt. For example, “J17 received; two photos readable; supplier enquiry assigned to Mia; owner callback Thursday afternoon.” The receipt shows what actually arrived. It gives the tradesperson a chance to correct a misunderstanding while the visit is still fresh. A thumbs-up alone cannot tell them whether the office saw the missing measurement.
Use a different state for a handover awaiting review and one accepted by dispatch. Audio captured, draft prepared, office accepted and customer informed are four different events. A job should not appear complete merely because the phone captured a note. When evaluating Cortex channels, test the channel your crew already uses from both ends of an ordinary site handover.
Compare a week of handovers with your usual routine
Sample a small run of similar jobs before changing the process. Count how often the office had to call the site worker, how many notes ended up on the wrong record and how many promised callbacks had no owner. Record the cause of each callback. A technical question only the tradesperson can answer is different from a missing job number.
Then trial the new brief on the same sort of work. Look at the notes that travelled cleanly and at the exceptions. If a voice note repeatedly produces the wrong reference, consider selecting the job from the existing job list before dictating. If office staff cannot distinguish a customer request from a promise, change the headings on the handover rather than making the note longer.
Give the crew the results in ordinary terms. Show a handover the office could use immediately and one where the job still stopped. Let the people on site suggest which field they could supply more reliably. The best improvement might be to photograph the fitting beside a job card or to capture the customer's preferred callback time before leaving. Software helps when it fits the habits of the people doing the work.
Related guides: Run your business from chat: a practical guide to chat-first operations · Turn voice notes into tasks an AI agent can act on · Telegram vs WhatsApp vs Slack vs Discord for working with AI agents.
Frequently asked questions
What should we do with a note covering two jobs?
Split it before posting anything to the customer record. Ask the site worker which observation belongs to which job and keep unresolved information in the review queue. The convenience of one voice message does not justify mixing two customers' records.
Can the assistant send the price straight to the customer?
Treat a price as a separate commitment. Agree who can approve it, which quote version they approve and how the approval is recorded. Start the handover trial with internal drafts while testing whether the details reach the estimator accurately.
What makes a handover successful?
A colleague who did not visit the site can find the job, identify what happened, see what remains uncertain and take the next authorised step. If they must reconstruct the conversation from scratch, the handover still needs work.



