Good service call scheduling comes down to five habits: capture the same details on every call, promise an arrival window instead of an exact time, build each tech's day by area and job length with slack left in it, send the customer a day-before confirmation and an "on my way" heads-up, and close out every visit the same evening. A small shop can do all five with a whiteboard or a shared calendar. This guide shows how, with a copyable intake checklist and a worked example of one tech's day.
Take the call: what to capture every time
A lot of scheduling trouble starts at the phone. A call taken in thirty seconds with no address, no equipment details and no callback number turns into a wasted trip later. Use the same short checklist for every call, whether you take it yourself or someone else does.
Intake checklist (copy this):
- Customer name, best callback number, and email address
- Service address, plus gate codes, parking notes, and pets
- Who will be home, and whether someone 18 or older must be there
- What is wrong, in the customer's words. Ask what they see, hear, or smell.
- Equipment: type, brand, rough age, and where it is (attic, crawlspace, garage)
- Is it urgent? Water actively leaking, no heat in freezing weather, no cooling for a sick or elderly person, gas smell. Say "emergency" or "same-week" or "whenever" on the ticket.
- Is this a callback on earlier work? If yes, note the original date and tech.
- Requested arrival window, and a second choice
- Any quote you gave on the phone, with the words you used
Read the address and phone number back to the customer. Write the call down in one place, every time. The ticket can be a paper form, a spreadsheet row, or a record in software, as long as the tech reads the same fields the dispatcher filled in.
Arrival windows vs. exact times
Promise a window, not a minute. Traffic, a stuck valve on the previous job, or a missing part will move any exact time you give. A window gives you room to absorb that without breaking a promise.
How wide? Match the window to how much your day can wobble:
| Situation | Window to offer |
|---|---|
| First call of the day, tech starts at the shop or at home | 1 hour. Nothing before it can run over. |
| Mid-day calls after jobs of uncertain length | 2 hours |
| Last call of the day | 2 hours, and confirm it that morning |
| Emergency | "Within [X] hours," then call when you are 30 minutes out |
| Scheduled maintenance or installs | A start time with a 30-minute buffer |
Two hours is wide enough to be honest and narrow enough that the customer does not lose a whole morning. Test it against your own late arrivals. If your techs miss two-hour windows more than once a week, widen the window or shorten the day. Do not hide behind a four-hour window to cover for a bad schedule. Fix the plan instead.
Build the day: geography, job length, and slack
A dispatcher is solving two puzzles at once: where each job is and how long it takes. Build the day in this order.
1. Place the fixed points first. Any call with a promised window and any callback goes on the board before anything else. 2. Cluster by area. Group stops that are near each other so a tech works one side of town in the morning and the other side after lunch. Sort by neighborhood or zip code if you do not have a map handy. 3. Estimate each job honestly. Keep a short list of typical times for your top ten job types: a no-cool diagnosis, a drain clear, a water heater swap, a faucet install. Revise it every few months from what really happened. Include drive time and ten minutes to write up the job. 4. Leave slack. Plan for about 80 percent of the tech's hours, not 100. The unplanned 20 percent covers jobs that run long, a parts run, and lunch. 5. Hold an emergency slot. Keep one open hour in the late morning or early afternoon each day for urgent calls. If nobody calls, use it for a callback or to start the next day's parts pull. An emergency slot is cheaper than shoving a stranger's burst pipe into a day that is already full. 6. Put short jobs near the end. If the afternoon blows up, a 30-minute call is easier to push than a three-hour install.
Assign the right tech
The next available tech is not always the right one. Check two things before you drop a job on the board.
- Skills and licenses. Gas work, refrigerant handling, electrical, and backflow testing often require specific licenses or certifications, and the rules vary by state and city. Keep a one-page skills grid on the wall: who can do what.
- Callbacks go to the original tech. If the same problem comes back, send the person who did the first visit when you can. They know what they touched, and the customer sees that you own your work. If the original tech is out, put their notes and photos on the ticket.
The day-before confirmation and the "on my way" heads-up
Two short messages cut down on no-shows and "where are you?" calls. Send them by phone call, text, or email, whichever your customer answers.
Day before (send by early afternoon):
> Hi Maria, this is Ace Plumbing confirming your visit tomorrow between 10 and 12 at 214 Oak Street. Reply YES to confirm or call 555-0142 to change it. Please make sure someone 18 or older is home and the water heater closet is clear.
On my way (send when the tech leaves the prior job):
> Hi Maria, Dave from Ace Plumbing is on the way and should arrive in about 25 minutes. He'll call if anything changes.
The first message gives the customer a chance to cancel while you can still fill the slot. The second turns a two-hour window into a 25-minute heads-up, so nobody waits by the door all morning.
Running late and rescheduling
You will run late. What matters is when the customer hears about it.
- Tell them when you know, not when you are late. The moment a job overruns enough to push the next window, the tech or dispatcher contacts the next customer. Offer a new arrival time and a choice: keep it, or move to another day.
- Give the new window, not "soon." "We now expect to arrive between 1:30 and 2:30" is something a person can plan around.
- When the customer asks to reschedule, ask why. A conflict at work is a simple move. Price worries are a sales conversation worth having before you roll a truck.
- Write every change on the ticket. The next person who touches it should see what was promised and why it moved.
A worked example: one tech's day
Say Dana is a plumber starting at 7:30. These times and jobs are made up to show the pattern.
| Time | Stop | Notes |
|---|---|---|
| 7:30 to 8:00 | Shop: load truck, review tickets | Reads every ticket, checks parts |
| 8:30 to 9:30 | Callback: running toilet, east side | Original tech was Dana. Window: 8 to 9. |
| 9:45 to 11:15 | Water heater flush and anode check, east side | Window: 9:30 to 11:30 |
| 11:15 to 12:15 | Open emergency slot | Nothing came in, so she picks up a parts order and logs notes |
| 12:15 to 12:45 | Lunch | |
| 1:00 to 3:30 | Garbage disposal replacement, west side | Window: 12:30 to 2:30. Drive 15 minutes. |
| 3:45 to 4:30 | Drain camera inspection, west side | Short job placed late |
| 4:30 to 5:00 | Closeout | Photos, notes, invoices, tomorrow's tickets |
Notice what is built in: the east-side jobs sit together, a free slot is held for the unplanned, and 30 minutes at the end belong to paperwork. If the disposal job runs 30 minutes long, the drain camera visit moves to tomorrow morning and nothing else breaks. One customer gets one call.
End-of-day closeout
Closing a visit the same day beats any other fix for billing delays and for "what did we do there last time?" questions. Before a tech goes home:
- Mark each job done, not done, or needs a return visit.
- Attach photos of the work, the equipment data plate, and anything unusual.
- Write what was found, what was done, and what is recommended next.
- Collect payment or send the invoice (see how to get paid faster).
- Flag follow-up work: an estimate to write, a part to order, or a maintenance visit to book. If you sell recurring service, maintenance agreements keep those visits on the calendar.
Then the dispatcher looks at tomorrow's board, moves anything that fell off today, and sends the day-before confirmations.
A lighter way to run it
When the whiteboard stops keeping up, Jobsite's Home Services Suite logs every call with the customer, address, equipment, priority, and requested arrival window. Its dispatch board lets you drag visits between techs, flags overlaps, and publishes the day. Techs tap On my way, Arrived, and Complete on their phones. Appointment confirmations, a day-before reminder, and On my way and running-late notices go to customers by email, in English or Spanish. It's $49 a month with 25 worker-days included, then $1 per additional worker-day, month to month — and you can set it up on free sample data first.
FAQ
How wide should an arrival window be?
One to two hours is a sensible starting point. Use a one-hour window for the first call of the day, when nothing earlier can run over. Use two hours for later calls. If your techs keep missing the window you promise, widen it a little or plan fewer jobs per day.
How many service calls should one tech run in a day?
It depends on your trade and job mix. Build from your own job-length estimates, leave about 20 percent of the day open, and adjust after a few weeks of real data.
How do I handle emergency calls without wrecking the schedule?
Hold one open slot a day for urgent calls. When an emergency exceeds that, move the most flexible job on the board and call that customer right away with a new window and an apology. Do not quietly let jobs slide.
Do I need dispatch software?
No. A whiteboard, a shared calendar, and a standard intake form will carry a one- or two-truck shop. Software helps once you cannot see everyone's day at a glance or confirmations eat your evenings.
What should I do when a tech is running late?
Contact the next customer as soon as you know. Give a new arrival window and offer to reschedule. Customers forgive delays; they do not forgive silence.
See how Jobsite handles this in practice: Home services on the platform →
About the author
The Jobsite Editorial Team — Construction safety & OSHA compliance
The Jobsite Editorial Team writes the safety and compliance library behind Jobsite, the construction safety, OSHA compliance, and training platform for contractors. Every article starts from the primary regulatory text — the CFR section itself, not a summary of it — and is fact-checked against that source before it publishes, so what you read here is what the standard actually requires of small and mid-size contractors in the field.