Pre-release Documentation for Ascent Direct Booking. Not yet approved for commercial release. View availability details
Email and reminders
Locally captured confirmation and reused reminder evidence. Not inbox delivery.
Captured mail means the local installation recorded a message. It does not prove that a customer’s inbox received it. SMS and WhatsApp are not included.
A signed-in booking captured confirmation mail locally, with one notification attempt and two attributable subjects.
New pilot result on 1.2.104
The fresh pilot stored the attempt and the captured subjects. External delivery was not sent. Queued, accepted, delivered, and bounced states were not defined by that capture.
Before you start. A stored booking. A configured mail transport is a hosting task and was not externally proved.
Limit. Capture is not delivery. This is not SMS. A failed or uncertain send must not be described as received.
Technical details
Why it matters. The business has a local record that a confirmation was generated for that visit.
Example. The customer confirms a visit and the local mail log shows the confirmation subjects. The inbox is a separate question.
Who uses it. The customer is the intended recipient. The owner can see that an attempt was recorded. The booking confirmation path.
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.
Reminder scheduling was reused for 1.2.104 because the ledger says those files were unchanged. It was not rerun.
Earlier result reused. Not rerun.
The reused result captured a reminder and recorded a Makassar clock reading of 9:30 am on 25 October 2026 for that earlier fixture. The 1.2.104 pilot did not repeat the interrupted-send case.
Before you start. The unchanged-file comparison in the 1.2.104 ledger. A real mail sender is a deployment task.
Limit. Not rerun on these bytes. Not inbox delivery. Not SMS or WhatsApp. Review-request mail is a different template and is not included.
Technical details
Why it matters. The business can have a reminder generated from the business clock, on the evidence that was reused.
Example. A visit is due and the local log shows a reminder addressed in the business timezone. That does not prove the customer’s phone received it.
Who uses it. The customer is the intended recipient. The reminder scheduler.
Status: Cited local evidence. This is not commercial acceptance. Origin: Earlier result reused for 1.2.104 because the cited files were unchanged. Not rerun. Candidate 1.2.104 is not an accepted commercial release. R11 ledger marks reminders reused and not rerun. Makassar clock evidence is the earlier R9 result cited by that ledger.
Earlier candidates previewed and reset email text. The fresh 1.2.104 ledger did not repeat template editing.
Shown on an earlier local candidate, not repeated on 1.2.104
An earlier proof previewed a heading and footer without saving, and a failed reset did not claim success. The source registry lists many template names. Only confirmation capture and reused reminders are tied to 1.2.104 evidence.
Before you start. Not repeated on 1.2.104.
Limit. A template name in source is not proof the message is sent. Sender name, From address, and reply-to were not separately passed in the 1.2.104 ledger.
Technical details
Why it matters. The business can adjust wording when that editor is the one under test, then put the tested template back.
Example. The owner changes a subject, previews it, and resets. Unverified as a fresh 1.2.104 action.
Who uses it. The business owner. The email template screen on the 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.
A deliberate test to an authorised recipient was not a 1.2.104 ledger item.
Not determined
Local capture during booking and password reset is the evidence that exists. A separate test-send control was not exercised.
Before you start. Unresolved.
Limit. Do not enter a customer’s address as a test. External delivery remains unproved.
Technical details
Why it matters. Owners want a safe test before launch. This guide does not document a button that was not checked.
Example. The owner clicks a test button. Unverified.
Who uses it. The business owner. Unknown.
Status: Not determined. Origin: Not determined. Candidate 1.2.104 is not an accepted commercial release. Not verified for this guide. Described as unresolved rather than as an available feature.
A notification centre is not established. Captured booking-confirmation email is one local record of one message. That capture does not list, filter, or manage messages, and it is not inbox delivery.
Gap. Not established.
Email template registry
An email template registry is not freshly verified. Source names and a captured confirmation do not show that the registry or the template editor was exercised on 1.2.104. Template preview and reset remain an earlier result and were not repeated.