Scheduling that tells a backup from a camera inspection.
A caller with water already coming up through a floor drain and a homeowner booking a routine camera look at a line that clogs every few months are not the same appointment, but a calendar that only sees a name and a time treats them identically. Appointment scheduling for a drain cleaning business has to hold whether water is rising right now, how long a camera inspection actually takes on the truck, and whether this address has clogged before. Neuron keeps that context on the calendar itself, so an active backup does not sit behind a booked inspection, and a camera visit does not get squeezed into a slot sized for clearing a kitchen sink.
An active backup can't wait behind a booked camera visit
Water is already on the floor or coming up in a basement drain, and the next open slot on the calendar belongs to a camera inspection booked three days ago. A calendar that only sees two appointments of equal weight has no way to say which one actually has to move, so the backup waits its turn behind a visit that was never urgent to begin with.
Neuron books the visit it actually is
The AI receptionist and the booking page ask whether water is rising now or a line just needs a look, and write that onto the calendar as an urgent clog or a scheduled camera inspection — each with its own length, since a camera run down a line takes longer than clearing a stopped sink. An active backup lands in the next open slot instead of behind a routine visit nobody flagged as one.
You still send the right tech back to the right line
Neuron fills the calendar; it doesn't decide who's on the truck. You send the technician who already ran a camera down this line before to the address that clogs again, and if that visit turns up root cutting or jetting, it books as its own appointment tied to the same line record — so the next call about the same stack doesn't start from nothing.
Appointment scheduling — FAQ
Does an active backup jump ahead of a scheduled camera inspection?
Yes — booking records whether water is rising right now, so an active clog moves into the next open slot instead of waiting behind a camera visit that was already on the calendar.
Does a camera inspection get the same short slot as clearing a sink?
No — a camera inspection books its own longer block, since running the line takes more time than a routine clearing; the calendar holds that difference instead of squeezing both into the same window.
Can the same technician go back to a line that keeps clogging?
Yes — you assign the repeat call to the tech who already has history on that line, and Neuron keeps the earlier visit's notes attached instead of the third call starting over.
What happens to the schedule when a camera inspection finds more work?
Root cutting or jetting books as its own appointment tied to the same line record, so whoever takes that job arrives already knowing what the camera found.