Overview
Before an answering team confirms a home-service visit, specify which saved field represents the customer’s arrival window and what the team may say about it. A requested time, a calendar start, and a confirmed arrival window should not silently become the same promise. This is a buyer planning guide, not a claim of verified AnSer scheduling integration.
Check how your system constructs the window
Housecall Pro documents that its arrival window begins at the scheduled job or estimate time. It supports a default window and a job- or estimate-specific window. Its documentation says the text preview changes with the window when text messaging is configured. Ask your account owner to demonstrate the saved record and preview together.
Jobber documents arrival windows for jobs, including their customer-facing appointments, booking confirmations, and visit reminders. They are not available for assessments. The window is set at the job level and applies across its visits. Its arrival-window variables fall back to the start time when the default window is set to none. Confirm the feature is included in your plan and inspect your actual message template rather than assuming a window appears.
Approve the wording for incomplete information
Write separate instructions for a caller’s preference, a saved appointment, and a confirmed customer-facing window. If the answering team can only record a request, its wording should say that the scheduling team still needs to confirm. Do not turn a caller’s preferred time into a technician commitment.
Assign the person who can approve exceptions and the response to use when that person is unavailable. Capture the unresolved requirement in the handoff without inventing a narrower window to finish the call.
Test one default and one exception
Use test customer details and an approved test workflow. Keep the saved appointment, message preview, and caller script together for review.
- Default window: create a test appointment and compare the window shown in the record with the words the answering team would use.
- Specific exception: demonstrate a different approved window on a separate test job and inspect the resulting customer-facing message. For a recurring Jobber job, check the effect across its visits before approving a change.
- No window: inspect the message when no window is configured; verify that an exact start time is not unintentionally communicated as an arrival guarantee.
- Changed visit: update the approved time and verify which message the customer would receive and who owns any correction.
Check who can make a later correction
Jobber’s documentation says arrival windows can be added while creating a job in its app, but an existing job must be updated on Jobber.com to add an arrival window. Verify that the responsible role has the access needed for the correction; do not assume a field available during creation is editable through every interface later.
For any platform, ask the answering provider to demonstrate the exact permitted action and resulting record. If it cannot complete the correction, define the scheduling-team handoff. Approval of the script alone does not establish software permissions or a working integration.
