Resolve scheduling conflicts
Scheduling can be blocked for two different reasons, and the visit form tells you which one you hit.
Scheduling conflict
Property-based visits can overlap on a technician's schedule without a numeric limit. A no-property availability block, such as Tech Unavailable, remains exclusive: neither a property visit nor another availability block can overlap it. The conflict message identifies the existing visit or block. The check looks only at service time — a drive to or from the visit can cross into unavailable time without being rejected.
This pushes a visit into the next day
A visit is allowed to run past midnight, but no visit may start on the next day. This message means your change would push a later visit's start time past midnight — usually because an earlier visit grew or moved and everything after it shifted. Drive time counts too: a visit starts after the technician's previous visit ends plus the drive to get there, and when that drive is what carries the start past midnight, the message says so and shows the drive time.
When they appear
Both appear when you save the visit form. Dragging a visit on the calendar shows a conflict as a message at the top of the screen; a drag that would push a visit into the next day is refused with a general "couldn't schedule" message rather than the detailed one above, so re-check the technician, the start time, and the visit duration if a drag is rejected without explanation.
Common fixes
Move the visit to another time, assign a different technician, adjust duration, or return the visit to the backlog until the office can confirm the plan. For a visit pushed into the next day, start it earlier, shorten it, or move the later visits to another day. For multi-day or all-day edge cases, review the exact start and end time carefully.
Where to find it: Scheduling page, while dragging or editing a visit
Related guides
Last updated
Was this helpful?