Booking HandbookCan you serve this customer address?
First checks
- Capture the service address
Keep the place where work happens separate from billing and contact details.
- Apply one eligibility rule
Use a ZIP list, zone, radius, drive-time, or another explicit boundary.
- Check the schedule second
An eligible address can still be impossible at the requested time.
- Confirm one clear outcome
Show accepted, manual review, outside area, or remote alternative before payment.
Which configured outcome does this ZIP receive?
Use this small test to catch overlapping and missing ZIP-list rules. Standard ZIPs may continue to scheduling; review ZIPs require a person to decide; everything else is blocked from automatic confirmation.
Continue to scheduling
ZIP 10002 passes this standard-zone pre-screen. Continue with address, service, staff, and schedule checks.
- ZIP used for matching
- 10002
- Configured outcome
- Standard service
This checker normalizes U.S. ZIP+4 to five digits. It does not validate a street address, geocode a location, calculate distance or travel time, confirm staff availability, or establish taxes, licenses, safety, or product behavior.
Collecting an address does not prove that the business can serve it.
A booking form may accept any valid-looking address while the business serves only selected ZIP codes, days, services, or crews. If eligibility is checked after confirmation, staff must cancel, reprice, or manually repair an appointment the customer believed was final.
Bookable address = usable address + eligible service + allowed zone + feasible time + confirmed price
A standard-zone ZIP may continue to live availability. A border ZIP may become a request for review. An outside ZIP should stop before a firm appointment or charge is confirmed.
Follow the complete service-area workflow
A mobile appointment is not bookable merely because the customer entered an address and an employee has free time. The address must be usable, the requested service must be allowed there, the zone and price must be clear, and the schedule must leave enough time to reach it.
Decide where you serve before the calendar promises when you can arrive.
- Choose the delivery mode
Ask whether the customer wants a business location, their address, or a remote appointment before showing location-dependent times.
- Capture a usable service address
Collect street, unit or access details, city, state, ZIP, and any instructions needed to find the work site. Do not reuse a billing address silently.
- Check service eligibility
Some services, equipment, licenses, crew sizes, or prices may be available only in specific areas even when the business generally serves the address.
- Assign one zone outcome
Return standard service, manual review, outside area, or a remote or branch alternative. Avoid overlapping rules that produce two answers.
- Calculate the real booking
Only after eligibility passes should the system check the employee, duration, buffers, travel, daily capacity, and other reservations.
- Confirm the same details everywhere
The customer message, staff calendar, price, service address, delivery mode, and later changes should all describe the same appointment.
Compare the five service-area models
ZIP codes are easy to operate but imprecise. Radius, drive-time, and custom zones add detail and also add data, precedence, and failure decisions.
Exact ZIP allowlist
Useful when service rules are already operated by a stable list of U.S. ZIP codes.
- Rule
- Match the normalized five-digit ZIP to one unambiguous outcome and review the list when coverage changes.
- Watch for
- A ZIP is a convenient pre-screen, not a precise travel boundary or proof that every address inside it is reachable.
Named city or district zones
Useful when staff and customers already understand service areas by city, borough, county, or operating district.
- Rule
- Define how an address maps to a zone and what happens at borders or when place names are ambiguous.
- Watch for
- Free-text city names, abbreviations, and mailing addresses can map inconsistently without normalization.
Straight-line radius
Useful as a simple boundary around a depot or branch when travel conditions are reasonably uniform.
- Rule
- Geocode both points consistently, state the distance basis, and choose what happens exactly on the boundary.
- Watch for
- Straight-line distance does not represent roads, bridges, traffic, parking, or actual driving time.
Drive-time area
Useful when the operational promise is based on how long a worker should travel rather than miles alone.
- Rule
- Use a named routing method, direction, departure assumption, failure fallback, and freshness policy.
- Watch for
- A route estimate can change and does not guarantee that the surrounding appointment chain remains feasible.
Custom zones and route days
Useful when different ZIPs, neighborhoods, or polygons are served only on particular days, at different prices, or by different crews.
- Rule
- Keep zone eligibility, day capacity, staff eligibility, service restrictions, and price rules as separate decisions that must all pass.
- Watch for
- A flexible rule model needs clear precedence so overlapping zones cannot silently return different outcomes.
Recheck the location when the appointment changes
An accepted address can become infeasible after the customer changes the service, time, worker, or location. Unknown lookup results should enter review.
Customer changes the address
Start the location decision againRecheck address usability, service and zone eligibility, worker assignment, travel, price, and customer instructions before preserving the time.
Customer changes the service
Recheck what is allowed thereThe new service may require different equipment, staff, duration, credentials, price, or a business-location visit.
Appointment is rescheduled
Keep eligibility and feasibility separateThe address may remain inside the service area while the new time fails staff hours, route-day, capacity, or travel constraints.
Zone rules change
Review affected future bookingsDo not silently cancel, reprice, or move appointments that were accepted under an earlier boundary or service-day rule.
Staff or depot changes
Recalculate from the new originEligibility, travel, equipment, price, and arrival instructions may change when another worker or starting location takes the job.
Address or routing lookup fails
Fail into review, not a false promisePreserve the request and explain the next step instead of treating an unknown address as automatically inside or outside the area.
Watch for these software-demo red flags
Use one standard address, one border case, and one outside address through customer and staff paths. Then change the address and inspect every dependent detail.
Any address can confirm
The form collects a street and ZIP but never applies an eligibility rule before showing times, price, or payment.
ZIP means exact distance
The system treats a postal code as a precise radius or drive-time boundary without checking the actual address or route.
Overlapping zones disagree
The same address can receive two prices, crews, service days, or eligibility outcomes depending on the booking path.
Eligibility ignores the schedule
The address is inside the area, so the booking confirms even though no assigned worker can reach it between surrounding appointments.
Address changes keep old details
The booking moves, but its price, travel block, staff assignment, calendar entry, or customer message still reflects the previous address.
Use one standard ZIP, one review ZIP, and one outside ZIP.
A vendor saying it supports customer locations is only the beginning. Give every shortlisted product the same addresses and make it preserve the right outcome when the booking changes.
- Write the actual service-area rule, including one clearly accepted address, one border case, and one outside address.
- Book the same service through customer and staff paths, recording when address, eligibility, time, and price are decided.
- Change the address, service, time, and assigned worker, then inspect confirmations, calendars, travel blocks, and released holds.