See who’s visiting each site and what they need to know before they arrive. Start with the Field service app, then set up reminders and repeat bookings around your team’s rules.
Show next week’s visits and flag the decisions I need to make
Example setup: read the visit list and site instructions, then prepare a draft for the office to check. Read Jobs 1Here is the draft for next week. Check travel time and access windows before confirming the visits.
Draft Schedule 1A collection of proposals submitted to various clients.
Every strategy we build connects the work to the people who actually see it. We are not generalists who happen to work here — we are the people who do the work.
The method is the same whoever the client is: research, structured planning, and real-time correction, with both the experience and the number it moves in mind.
drag to rotate · click a doc to trace its links · double-click to open
Open the calendar to see the visit time, service and assigned technician. We used the Field service app to book the fictional inspections shown below.

Choose a date and technician, then add the site instructions. A note about access belongs with the job, where the person attending can find it.
Create another job for the follow-up and give it a priority. The original visit stays in the customer’s history, ready for whoever goes back.
What happened last time? Keep the notes, checklist and materials used with the visit so the next person can read them before arriving.
Choose who approves the next visit and when a reminder should go out. Those automations need their own setup; installing the app doesn’t switch them on. The agent panel above shows an example.
Work through the visit-planning guide, then decide whether renewals or report preparation would help next. You can compare current plans once you know what you need.
Take a few sites with known visit dates, access instructions and assigned technicians.
Book the visits and see whether the calendar and job records give the office what it needs.
Start with a reminder or repeat booking, agree the rules and test it before using it with customers.
Yes, by booking each visit in the Field service app. A finished job won’t automatically create next month’s or next quarter’s appointment. For that, you’ll need an agent or flow set up with the interval, an approver and a way to catch missed bookings.
The calendar shows visits and technician assignments. It doesn’t calculate routes, account for live traffic or match jobs to licences. Check travel time and site access yourself, or have an additional workflow set up and tested before using it for dispatch.
Yes, once the channel and sending rules are set up. Decide what the message says, when it goes out, who can approve it and where replies go. The Field service app won’t start messaging customers when you install it.
Book a separate job and choose its priority and technician. The previous visit stays in the customer’s history. If you move an appointment, also check who needs telling and whether another calendar needs updating; those connections need to be set up separately.
Saved schedules and job packets can be read offline on a device that has already loaded them. You need a connection to make changes; offline edits aren’t queued for later. Try it on your technicians’ phones and at a site with poor reception before relying on it during a round.
First decide where each record belongs: customers, appointments, contracts and visit notes. Then check the connection or import options for the tools you actually use. There isn’t a ready-made connection to every pest control system, so establish what will work before moving records.
The app stores the notes, checklists and materials used on a job. Turning those into a customer report needs your report format and someone to check it. Your qualified staff still need to confirm the treatment details, required records and any local reporting requirements.
Use the pricing link on this page to see current plans. Work out which apps, agent tasks and communication channels you need first. A workflow illustrated here doesn’t mean a bespoke implementation is included in a particular plan.
Ready to deploy
3 ready
We use cookies to enhance your user experience.
For a complete overview of all cookies used, please see our Cookie Policy.
Customize cookies
Choose which cookies you allow. Essential cookies cannot be disabled.