How to schedule appointments at customer addresses

How should customers enter a UK or US address?

For a UK home visit, the customer enters their postcode and door or flat number. CalMov checks the postcode lookup and combines the result with those property details. Ask the customer to review the resolved address: a recognised postcode alone does not establish which door or flat you should visit.

For a supported US business, the customer enters a ZIP code and a full street address, including the street number and name. Include the apartment or unit where needed. A ZIP code covers an area, so entries such as '1 New York' or a ZIP code on its own do not identify a visit location reliably. The address must belong to the selected country and match the ZIP code.

The business's country setting decides which address fields appear. This guide describes the US flow where it is enabled; it does not mean every business can switch countries or accept bookings in every country. Check your business region and supported coverage before sharing the booking page.

Which services need the customer's address?

Choose the location type for each service to match how it is delivered. A service at the customer's address needs their location so coverage and travel can affect available times. An online appointment or a service at your business location follows the relevant booking steps without asking for a home address.

Test each service type you offer. A mobile treatment should check the visit address, an appointment at your premises should use that location, and an online consultation should use its online meeting setup. Service selection can change which steps are needed, so test the actual service rather than relying on one example booking.

Which address details should you collect?

Collect enough information to identify the visit location and reach it: typically address lines, town or city and postcode, plus a limited access note where genuinely needed. Use address lookup as an aid rather than assuming every result is complete. Let the customer review the selected address before the booking is confirmed.

Ask for location early enough to apply coverage and travel rules, but avoid collecting unrelated information. Explain the purpose next to the field or in accessible privacy information. For flats, rural properties or new developments, a concise access instruction may prevent delay, but do not turn a scheduling form into a store for sensitive case notes.

• Full visit address and postcode
• A contact method for appointment coordination
• Only essential parking or access information
• A customer confirmation that the address is correct
• A clear explanation of how location data is used

How do you define a service area?

Build the boundary from completed jobs, journey time and demand clusters rather than a visually neat radius. Start with the places you can serve consistently at normal prices. Test edge postcodes at typical travel times because road structure, parking and crossings can make equally distant addresses operationally different.

Create a core area for ordinary availability and optional outer areas for selected days or manual approval. This keeps broad demand from scattering the diary. Review declined postcode requests as well as accepted jobs. A repeated cluster can justify expansion when nearby demand supports a complete route rather than a single long return trip.

How does an address change available times?

A free hour is not automatically a bookable hour. The proposed service must fit after travel from the previous customer and before travel to the next confirmed address. For the first and last visits of the day, a rule about travel from and back to your base may also apply. The address therefore needs to influence availability before final confirmation.

Use a fixed travel gap when geography is compact and predictable. Use road and expected-traffic checks when distances vary or where route and time are important. In every case add operational tasks that a mapped journey does not include, such as equipment packing, parking, walking and setup.

What loads before the customer chooses a day?

CalMov can begin preparing calendar availability while the customer is still choosing their service, once the selected service and required location information are ready. For a home visit, this follows the address check. Loading calendar information earlier can reduce the wait at the dates step; it does not reserve an appointment or guarantee a time.

When the customer chooses a day, CalMov loads that day's viable times using the selected services and the applicable booking and travel rules. For home visits, the journeys around existing bookings affect which starts can fit. Changing the address or service changes the availability being requested, so a date or time seen for an earlier selection should not be treated as a promise for the new one.

Why check the locations before and after a visit?

Checking only the route into a proposed appointment can protect the new customer while compromising the next one. An address may be close to the previous visit but in the opposite direction from the following booking. Combine the incoming journey, new service, pack-down and onward journey before offering the slot.

When there is no booking before or after, apply a documented rule rather than skipping location logic unpredictably. Decide whether the first visit must be reachable from base and whether the return after the last appointment needs protection. Consistency makes availability easier to explain and test.

What does an address-based scheduling example show?

A 60-minute service appears to fit in a 90-minute calendar gap. The drive from the previous address is twenty-five minutes and the onward drive is twenty. Together with the service, the requirement is 105 minutes before packing, parking or setup. The address makes the apparently free slot impossible.

Now place the proposed customer five minutes from both neighbouring visits. The same service uses seventy minutes before operational extras and may fit safely. This example shows why a blanket decision based on service length loses useful slots nearby and risks lateness across the area. Geography must be evaluated for the specific booking sequence.

When is the appointment actually confirmed?

After selecting a viable time, the customer enters their contact details and any required booking information, then reviews the service, address, time and price. In the Pro flow, selecting a time also checks and temporarily reserves the slot while the customer completes these details. A reservation is not a completed booking; if it expires, the customer may need to select a time again.

Keep service durations, working rules and travel allowances realistic. The displayed availability uses the booking and travel checks described above; it is not a guarantee against traffic, access problems or later disruption. Check the final booking status before treating the appointment as confirmed.

For online payment, follow the booking through checkout and its return page. A 'Payment processing' or 'Pending payment' message means payment confirmation is still outstanding. Check the final booking and payment status in CalMov before treating a paid booking as complete. A customer returning from checkout is not, by itself, proof that the booking is paid.

What should you check when no address or times are found?

Start with a real, complete address inside your normal service area and a service you know is bookable. Use a future working day within your booking window. Correct one input at a time so an address problem is not confused with a closed day or a service that cannot fit.

If the address resolves but no times fit, inspect the working hours, existing appointments, service duration, travel allowance and coverage. A free-looking calendar gap may still be too short once travel is included. If a complete, supported address still fails lookup, contact the business or support rather than substituting a nearby location just to pass the check.

• Address not found: check the country, postcode or ZIP, spelling, and required door, flat or street details.
• Vague US address: replace entries such as '1 New York' with the actual street number and street name.
• No dates available: check working days, time off, minimum notice and the booking window.
• Dates appear but no times fit: check service length and the travel needed before and after existing appointments.
• Location outside coverage: confirm the business's service area rather than changing the customer address to bypass it.
• A previously shown time is unavailable: reload availability and choose another time; an earlier calendar view is not a confirmed booking.

How should address privacy and access be handled?

A customer address is personal data. Limit access to people who need it for booking and service delivery, protect accounts, and avoid exposing private booking-management URLs to search engines. Collect data that is adequate, relevant and limited to the stated purpose, then follow a documented retention and deletion approach.

Provide privacy information when data is collected and distinguish general scheduling from specialist recordkeeping. Health, care or regulated services may need separate systems and obligations beyond a booking platform. Seek appropriate professional advice for your circumstances; a scheduling guide cannot decide the lawful basis or retention period for every business.

How do you test and review address bookings?

Test a valid core postcode, an edge address, an out-of-area address, a flat, a new-build result and an incomplete entry. Place proposed visits before, between and after confirmed bookings. Confirm that the customer sees a useful explanation and that the business record preserves the agreed location without revealing it publicly.

After launch, record address corrections, failed lookups, access delays and manual reschedules. Update the smallest relevant rule. Improve field guidance when customers enter the wrong location; adjust access allowance when parking repeats; change coverage when a boundary creates unworkable routes. Review permissions and retained address data at regular intervals.

• Test the furthest routinely accepted postcode.
• Confirm both incoming and onward journey checks.
• Verify address corrections reach confirmations and the diary.
• Check access notes are not displayed publicly.
• Review who can see and export customer locations.

What belongs on an address-based booking launch checklist?

Before launch, test location entry on a phone with a core postcode, an edge postcode, an incomplete address and a location outside coverage. Confirm that the customer understands why the address is needed, can correct it and receives a useful next step when the visit cannot be offered.

Then test the operator view. The agreed address should appear with the service and time, private details should remain out of public pages, and the journeys before and after should both be protected. Record who can access exports and which retention rule applies before real customer addresses enter the system.

• Core, edge, incomplete and out-of-area addresses tested.
• Customer can review and correct the location before confirmation.
• Incoming and onward journeys checked around the proposed visit.
• Private address and access notes stay out of public pages.
• Access, retention and deletion responsibilities documented.