Test the commitment.

Test the last available resource and a non-conflicting request; accepting everything and blocking everything are both failures.

Trace eligibility, working time, occupied duration and resources in order before changing availability rules.

Match customer wording and staff action to the actual appointment status; a successful form submission may still require review.

Treat an inventory change and the review of existing appointments as separate tasks. New availability does not settle old commitments.

Verify the appointment status, resource release and customer message separately; one visible cancellation label does not prove the whole workflow.

Inspect the appointment record first. A missing message is not evidence that no booking was created.

Verify the actual customer route on a phone and desktop, including labels, timezone, selected service and the final commitment.

Choose one booking source of truth, preserve future commitments and switch the public route only after the new configuration passes its essential tests.

A fallback should preserve known appointments and avoid accepting uncertain capacity, not create a second uncontrolled booking source.