Buyer’s checklist

Move one visit.
Keep the rest.

Your regular customer needs Thursday instead of Tuesday. A different cleaner will cover it. Try that ordinary change before choosing software for recurring jobs.

3 min read · October 1, 2026 · DavidAgents · Open the checklist

A tidy calendar is a good start. The useful test is what happens when a customer changes their plans: which visit moves, who gets the job, and what everyone is told.

Fictional example · illustration

One change in a three-visit series

Every other Tuesday, 9 AM, with Alex. Move the middle visit to Thursday and assign Sam.

Visit 01
Tue 13 Oct
9 AM Alex
Unchanged
Visit 02
Thu 29 Oct
9 AM Sam
Moved + reassigned
Visit 03
Tue 10 Nov
9 AM Alex
Unchanged

Only October 27 becomes October 29. Alex keeps the other visits.

This shows the intended result, not a product screen or a live scheduling tool. All dates are in 2026.

Use a trial with made-up details

Create one fictional customer and three visits, two weeks apart. Add a short job checklist and an ordinary note such as “Use the side entrance.” Keep real addresses, access codes and customer contact details out of the test.

Before saving a change, check the notification settings. Find out whether an update will send immediately, wait for approval or require you to send it. Use a test inbox you control if you need to check delivery.

Change the middle visit only

Move October 27 to October 29. Choose the option that affects this visit only. Assign Sam to that visit, leaving Alex on the others.

Now reopen the customer’s schedule and both workers’ schedules. Check the dates, assignments and job instructions. Look for clashes on the new day. A successful save is only part of the test.

Look at it from three sides

The customer: does the update name the changed visit and its new time clearly? The next regular visit should still make sense.
The substitute: can Sam open the details needed for this job? Check the actual worker account, including whether it exposes customer information the role does not need.
You: can you see who changed the visit, what changed, and which messages were sent? If delivery failed, is that visible?

Take this to your demo

The one-visit checklist

Use the fictional schedule in this guide. Tick each result you have checked in the software you are considering.

Only the October 27 visit moved to October 29. October 13 and November 10 kept their original times and assignments. Sam covers the changed visit only; both workers’ schedules are correct. The changed visit kept its job instructions, and the new time has no scheduling clash. Sam’s account shows the job details needed, with access appropriate to the role. The customer update clearly identifies the changed visit and new time. I know which updates send automatically, and can check what was actually sent. The record shows who made the change and when.

Checks stay on this page only. Print to keep a copy.

Fictional 2026 example: visits October 13, October 27 and November 10 at 9 AM with Alex. Move October 27 to October 29 at 9 AM with Sam. The other two visits stay unchanged.
DavidAgents · davidagents.ai/guides/one-visit-test.html

Decide what you can live with

A gap does not automatically rule a tool out. Ask the vendor to show the workaround, then decide who would handle it in your business. Try the same example with your other options so you can compare the work involved.

A general buyer’s checklist for any provider. This is not a demonstration or feature claim for AgentsFast.