Pre-release Documentation for Ascent Direct Booking. Not yet approved for commercial release. View availability details
Daily diary
The appointment actions the pilot recorded, and the ones it left unrepeated.
The fresh pilot marked a visit as a no-show and listed it for the owner. Moving and completing a visit were proved on an earlier candidate, not repeated as a fresh 1.2.104 browser pass.
The owner can mark a visit as a no-show, and the owner list shows that status.
New pilot result on 1.2.104
Fresh-site appointment 1 was marked no-show and appeared in the owner browser list. Move and complete were not repeated in that pass.
Before you start. An existing visit. A practitioner was not shown marking a cancelled visit complete.
Limit. A no-show is not a refund and not a payment event. Notification of the customer was not part of this check.
Technical details
Why it matters. The day can record that the customer did not attend, which is different from cancelling or completing the visit.
Example. The customer does not arrive. The owner marks the visit as a no-show and sees that label in the list.
Who uses it. The business owner. The owner diary.
Status: Cited local evidence. This is not commercial acceptance. Origin: New result recorded on the 1.2.104 local pilot. This guide did not re-run that pilot. Candidate 1.2.104 is not an accepted commercial release. R11 local-pilot ledger, record dated 2026-10-24. This guide did not re-run the pilot. Candidate 1.2.104 is not an accepted commercial release.
An earlier candidate let the owner create a visit, move it, and mark it complete.
Shown on an earlier local candidate, not repeated on 1.2.104
That installer booked a named customer, moved the visit, and completed it. The 1.2.104 ledger says move and complete were not rerun and that this was not recorded as a product failure.
Before you start. Not repeated on 1.2.104.
Limit. Do not describe move and complete as freshly proved on 1.2.104. Completing a visit is not a payment capture.
Technical details
Why it matters. The diary can be corrected when that candidate’s actions are the ones in use.
Example. The owner moves a visit to a free time and later marks it complete.
Who uses it. The business owner. The owner diary on that earlier candidate.
Status: Earlier local evidence. Not a new 1.2.104 result. Origin: Shown on an earlier local candidate and not repeated on 1.2.104. Candidate 1.2.104 is not an accepted commercial release. Earlier local candidate. Not repeated in the 1.2.104 pilot ledger. This guide did not re-run it.
An earlier candidate let the owner book a named customer and assign a practitioner.
Shown on an earlier local candidate, not repeated on 1.2.104
The earlier installer created that visit with automatic practitioner assignment. The fresh 1.2.104 notes do not repeat the owner-created booking.
Before you start. Not repeated on 1.2.104.
Limit. Phone-number handling and duplicate-customer checks were not part of the fresh pilot write-up.
Technical details
Why it matters. The front desk can add a visit for someone who phoned, on the candidate where that was proved.
Example. The owner searches for a customer, picks a service and a time, and stores the visit.
Who uses it. The business owner. The owner diary on that earlier candidate.
Status: Earlier local evidence. Not a new 1.2.104 result. Origin: Shown on an earlier local candidate and not repeated on 1.2.104. Candidate 1.2.104 is not an accepted commercial release. Earlier local candidate. Not repeated in the 1.2.104 pilot ledger. This guide did not re-run it.