How to stop double-booking jobs across phone, web and crews

Why jobs get double-booked

A double booking rarely comes from one careless person. It comes from two places where jobs get written down that don’t know about each other. The office books Tuesday at 9 on the shared calendar. Meanwhile the owner, out on a job, tells a repeat customer “Tuesday morning works” and notes it in their phone.

Each booking made sense on its own. The clash only shows up Tuesday at 8:40, when the crew lead calls to ask which address comes first. Look back at your last few clashes and you’ll usually find one of these causes:

• More than one calendar. The office calendar, the owner’s phone, a paper book at the counter and each crew’s own calendar are all places a job can be booked.
• Promises made outside the schedule. A tech agrees to come back Thursday while standing in the customer’s kitchen, and nobody enters it until that night.
• Web requests treated as booked. A booking page offers a free slot because it can’t see the jobs taken by phone.
• Copies that lag behind. One app sends jobs to another calendar one way only, or only every so often, so the copy someone checks is out of date.
• Two people booking at once. The office and the owner give out the same slot within minutes of each other.
• Job lengths that are guesses. A “two-hour” repair that always takes four pushes into the next job, and the one after that.
• No room for driving. Back-to-back slots across town look free on a calendar and are impossible on the road.
• Big jobs booked as small ones. A two-day install entered as one morning leaves day two looking open.

Count every place a booking can land

Before you buy anything, spend 20 minutes finding out where bookings actually come in. Ask everyone who talks to customers, not just the office. The owner and the crew leads often book more work than anyone realizes.

Write each channel down with two answers: who takes it, and where they write it. Then count the places jobs get written down. If the number is more than one, you’ve found the reason for your double bookings.

Keep the list. It becomes your checklist for the steps below: each channel either feeds into one schedule or stops taking bookings.

• The office phone, and whoever answers it when the office is busy or closed.
• The owner’s cell phone, voicemail and personal texts.
• Your website’s request form or booking page.
• Texts and calls straight to a tech from repeat customers.
• Emails, including from property managers or builders who send several jobs at once.
• Walk-ins at a counter or showroom, and deliveries sold along with an order.
• Your subcontractors’ own schedules, if they cover some of your jobs.

What to do when a job is already double-booked

Fix today first, and the cause second. Decide which job keeps the slot using a rule you could explain to a customer. Then call the other customer yourself, early, before the crew is due. A text that arrives an hour into their window does more damage than the clash itself.

Keep the call short and specific. For example: “We booked two jobs into your slot by mistake, and that’s on us. We can have a tech there Thursday at 8 or Friday at 1. Which works better?”

• Decide who keeps the slot. A simple order works: safety calls and no-heat or no-water emergencies first, then the job confirmed first, then the job that’s hardest to move.
• Look for a fix that moves nobody. Another crew may have a gap, or one job may be short enough to fit before the other.
• Call the moved customer before their window starts. Say what happened in one sentence, apologize, and offer two specific times, not “sometime next week.”
• Put the new time on the schedule while you’re still on the phone, so it can’t clash again.
• Tell the crew the new order of the day in one message, not three. For example: “Change for Tuesday: Oak St moves to Thursday 8 am. Your day is now 1) Elm St at 8, 2) Pine Ave at 11. Reply OK.”
• Follow up once after the new visit. A short call or text shows the mistake was taken seriously. If you offer a make-good, like waiving a trip charge, offer it on the first call, not after the customer complains.
• Write down the cause in one line: which channel, who booked it, and why nobody saw the clash.

Make one schedule the only one that counts

The fix is a rule more than a tool: one schedule is the real one, and a job isn’t booked until it’s on it. Every other calendar either feeds that schedule or shows a view of it. Nobody keeps a private list of promises.

In practice, that comes down to a few habits everyone agrees to:

Even in a small shop, one person should own the schedule each day. Others can book, but someone looks over tomorrow every afternoon and catches what slipped through. If changes still travel by group text, keeping crews and the office in touch covers where job updates should live.

• Phone bookings go straight onto the schedule while the customer is still on the line. No sticky notes to enter later.
• Every confirmed job gets a confirmation to the customer with the date and arrival window, sent from the schedule. It gives the customer one time to hold you to, and it puts what they were told on record.
• Web requests arrive as requests, not confirmed jobs. The office picks the time, then the customer gets the confirmation. Our guide to adding booking to your website covers when customers should book a time and when they should request one.
• Techs and the owner check the schedule on their phones before promising a date. If they can’t, they say “the office will call you with a time today.”
• A slot being offered is marked as held. While someone checks with a customer, it shows as taken until it’s confirmed or released. On a shared calendar, that can be an event named “HOLD – customer name”.
• Each crew’s calendar is a view of the one schedule, not a separate calendar someone copies jobs into.
• Changes happen on the schedule first, then go to the crew. Never the other way round.

Booking rules that stop clashes before they start

Clashes that aren’t channel problems are usually length problems. A schedule only knows what you tell it. Give each type of job a real length and the right people, and it stops offering slots that can’t work.

Write these rules on one page and give it to everyone who books. Rules that live in one person’s head disappear the day that person is out sick.

• Real job lengths by type. Pull last month’s jobs and see how long each kind really took. Book the usual time, not the best case.
• Drive time between jobs. Leave a gap between addresses, longer across town than within one neighborhood. For example, start with 20–⁠30 minutes within a neighborhood and 45–⁠60 across town, then adjust after a week of real drive times.
• Big jobs as one job. A two-day install with two techs should block both techs on both days, under one job.
• The right person or truck. If only one tech does panel upgrades, or one truck has the lift gate, the schedule should know.
• A daily limit per crew, so a busy Monday doesn’t get overfilled by three people booking at once.
• A plan for emergency calls. Decide ahead how a no-heat or burst-pipe call gets in. Leave an open slot each day, or set a rule for which job moves and who calls that customer. Squeezing it in on top of a full day is how two jobs end up at one time.
• A cutoff for tomorrow. After a set time, for example 3 pm, changes to tomorrow’s schedule go through the person who owns the schedule that day.
• Blocked time. Time off, parts runs, training and the morning yard meeting go on the schedule, so nobody books over them.
• A hold limit. Decide how long a held slot stays held, for example until the end of the day, before it opens up again.

Which tool fits: a shared calendar, a booking page or job software

You don’t always need new software. The right tool depends on how many people book and how many crews you send out. These are the main options, from simplest to biggest. Features and prices come from each vendor’s own page when we checked in October 2026.

Whatever you pick, give it the same three-booking test. Book one job from the office phone, one from the website and one from a tech in the field, all for the same crew and time. The right setup catches the second and third before anyone says yes.

• A shared calendar with rules. For one office person and two or three crews, a Google calendar per crew can be enough. You can share a calendar so others see only when it’s busy, without the event details. The rules above do the real work here.
• A booking page that checks your calendars. Google Calendar’s appointment schedules can check for busy times before offering a slot. A free Google account gets one booking page. Checking several calendars or running more than one schedule needs an eligible paid Google Workspace or Google One plan. Co-hosts, or a schedule on a second calendar like one per crew, need an eligible Workspace plan such as Business Standard. Co-hosts’ calendars aren’t checked by default, so add each person’s calendar on purpose.
• Microsoft Bookings, if you’re on Microsoft 365. A setting, on by default, lets events on each staff member’s Microsoft 365 calendar block their booking times. Microsoft recommends leaving it on to avoid double-bookings. Staff from outside your organization, like a subcontractor, can’t share their busy times with it, so their other work won’t block their booking slots.
• Calendly and similar booking tools. A booking page can only steer around calendars it’s connected to. Calendly’s free plan connects one calendar, and its paid plans connect up to six calendars per user. Its Standard plan is $10 a seat a month billed yearly, or $12 billed monthly.
• Job scheduling apps. Field service apps like Jobber or Housecall Pro schedule jobs by tech or crew. Jobber’s scheduling page says you can assign a job to a named crew in one step. It also says its calendar shows each team member’s open slots and makes it easy to catch double bookings before assigning a job. Housecall Pro says you can check availability and put more than one tech on the same job. If your work runs like most in your trade, this is usually the right next step. Our guide to choosing scheduling software shows how to trial one with last week’s real jobs.
• A system built around your jobs. When your bookings don’t fit any of these, the schedule can be built for how you work. We weigh that path against an app in field service software: buy or build.

References: Google Calendar Help: Share your calendar (opens in a new tab) · Google Calendar Help: Create an appointment schedule (opens in a new tab) · Google Calendar Help: Compare premium features for appointment schedules (opens in a new tab) · Microsoft Learn: Add team members to Bookings (opens in a new tab) · Calendly: Pricing (opens in a new tab) · Calendly Help: Connect your calendar to Calendly (opens in a new tab) · Jobber: Scheduling software (opens in a new tab) · Housecall Pro: Scheduling software (opens in a new tab)

How double bookings show up in different trades

The causes are the same everywhere, but each trade has its own weak spot. These are examples, not rules.

• HVAC and plumbing. For example, a 6-truck HVAC company takes no-heat calls by phone and maintenance visits through a web form. A salesperson in a customer’s home sells a two-day install and promises dates before checking which two techs are free on both days.
• Landscaping. A landscaper with 4 crews runs weekly routes. After a rain day, the office and a crew lead each move the same route, to different days.
• Electrical. Only one or two people may do certain work, like panel upgrades. Book the person, not just the crew, or two jobs need the same person at 10 am.
• Furniture showrooms. Sales staff promise delivery days at the counter while the delivery crew’s day is already full. The truck and the two-person crew are the limit, not the date.
• Property managers. A tenant texts about a leak, the owner emails about the same unit, and two vendors get sent. That’s a double booking too, of one job twice, and the fix is the same: one place where requests land.
• Cafés with catering. Two large orders for the same Saturday morning come in by phone and email, and the kitchen and the one van can only handle one.

Keep a record of every booking and every change

A schedule that only shows today’s plan can’t tell you why last Tuesday went wrong. Keep a short history on each job, so you can find the cause instead of guessing. Each booking should record:

Then spend ten minutes each Friday on the week’s clashes. Count them and note the cause of each. If most come from one channel, like texts to techs, fix that channel first. If they come from job lengths, update the length for that job type.

The same history settles “but you told me Tuesday” calls in a minute. And when you grow from two crews to five, it shows which booking habits held up and which didn’t.

• Who booked it, and when.
• Where it came from: phone, website, a text to a tech, email or walk-in.
• What the customer was told, including any arrival window.
• Each change: the old time, the new time, who changed it and why.
• Whether the customer and the crew were told about the change.

When the fix is a schedule built for your business

Most owners can stop double bookings with the steps above and an off-the-shelf tool. If an app passes the three-booking test with your real jobs, buy it and set it up properly. We’d rather say that than sell a build nobody needs.

Sometimes the clash survives every tool. Bookings come from places no app connects to, or your jobs, people and trucks don’t fit its screens. Then we build scheduling and dispatch around how you already book. Phone, web and crew bookings land on one schedule by crew. Each crew sees its own day on their phones, and every change is recorded on the job.

A focused fix, like sending your website’s requests straight onto the schedule, is $750–$3,000 over 1–⁠2 weeks. One business system, like scheduling and invoicing for a crew of 5 to 10 connected to QuickBooks Online, is $6,000–$18,000 over 6–⁠10 weeks. These are our prices as of October 4, 2026. We connect to QuickBooks Online, Square, Stripe, Shopify, Google Calendar, Gmail or Outlook, and check anything else before we quote.

If you’re still weighing the two paths, job management software or a custom job tracker compares them. When you’re ready, bring your list of booking channels to a free first call. You get a fixed price in writing within 48 hours. Once the project is paid in full, you own the code we write, and every launch includes 30 days of fixes.