Pre-release Documentation for Ascent Direct Booking. Not yet approved for commercial release. View availability details
Not included
Capabilities that must stay visible as absent.
These are listed so a summary elsewhere cannot be read as a promise. A catalogue, an email template name, or an old menu is not evidence that the excluded job can be done.
This edition does not collect deposits or online appointment payments.
Not included
The product contract separates recorded appointment value from collection. The pilot had no payments table on the sampled baseline. Payment processing is an explicit exclusion.
Before you start. Not included.
Limit. A stored price is not a received payment. A software subscription, which is also blocked, would not by itself take appointment money.
Technical details
Why it matters. A business can avoid promising a checkout button that is not there.
Example. A customer is asked to pay a deposit on the booking page. That collection step is not included.
Who uses it. Nobody, in this edition. Not available.
Status: Not included. Origin: Not included. Candidate 1.2.104 is not an accepted commercial release. Excluded by the current product contract or the pilot ledger. Not a delivered feature.
Google Calendar, Apple Calendar, and similar sync are not included.
Not included
The exclusion is stated in the pilot scope and the product contract. No sync connection was exercised.
Before you start. Not included.
Limit. The in-product diary is not an external calendar feed.
Technical details
Why it matters. The business will not expect appointments to appear in an outside calendar by themselves.
Example. The owner connects a Google account. That connection is not part of this edition.
Who uses it. Nobody, in this edition. Not available.
Status: Not included. Origin: Not included. Candidate 1.2.104 is not an accepted commercial release. Excluded by the current product contract or the pilot ledger. Not a delivered feature.
SMS is not included. WhatsApp delivery is not a working integration in this edition.
Not included
The older inventory marks WhatsApp provider support as a stub. The pilot scope says a working WhatsApp integration is outside the release. No SMS sender is evidenced.
Before you start. Not included.
Limit. A phone number stored on a customer is not a WhatsApp conversation. Manual copying of a message is not an integration.
Technical details
Why it matters. The business uses email evidence only, and does not promise a chat message.
Example. The owner ticks a WhatsApp confirmation. That send is not included.
Who uses it. Nobody, for delivery. Not available as a delivered channel.
Status: Not included. Origin: Not included. Candidate 1.2.104 is not an accepted commercial release. Excluded by the current product contract or the pilot ledger. Not a delivered feature.
Product catalogue records do not include a cart, stock deduction, shipping, or refunds.
Not included
The product-image check stored a catalogue row. The contract says checkout and fulfilment are out of scope.
Before you start. Not included. Catalogue records are a different feature.
Limit. Do not infer a shop from a product photo.
Technical details
Why it matters. The business will not describe a price list as a store.
Example. A customer adds a product to a basket. That basket is not included.
Who uses it. Nobody, for shop functions. Not available.
Status: Not included. Origin: Not included. Candidate 1.2.104 is not an accepted commercial release. Excluded by the current product contract or the pilot ledger. Not a delivered feature.
A builder for arbitrary forms is not included. Registration questions are a narrower tool and are evidenced separately.
Not included
The pilot scope left a generic form builder outside the release. Registration questions have their own proved publish behaviour.
Before you start. Not included.
Limit. Clinical forms in older source are historical and are not this builder either.
Technical details
Why it matters. The business will not expect surveys, contracts, and clinical packs from the question editor.
Example. The owner tries to build a multi-page medical questionnaire in the registration editor. That is not what the evidenced tool is.
Who uses it. Nobody, for a general form builder. Not available. Use the registration-question feature only for what it actually publishes.
Status: Not included. Origin: Not included. Candidate 1.2.104 is not an accepted commercial release. Excluded by the current product contract or the pilot ledger. Not a delivered feature.
The older pilot scope says they are not sent by a schedule, a manual action, or a retry. 1.2.104 did not re-enable them in the ledger used here.
Before you start. Not included.
Limit. Stored historical review rows, if an old installation has them, are not a working sender.
Technical details
Why it matters. The business will not expect an automatic review chase.
Example. The owner looks for a button that asks the customer for a public review. Sending that message is not included.
Who uses it. Nobody, for sending. Not available as a send.
Status: Not included. Origin: Not included. Candidate 1.2.104 is not an accepted commercial release. Excluded by the current product contract or the pilot ledger. Not a delivered feature.
Dental charting and profit calculation are not included.
Not included
Both are named exclusions in the pilot scope. The profit item in the older inventory is a stub, not a result.
Before you start. Not included.
Limit. A service category called dental would not add a chart. Recorded appointment value is not profit.
Technical details
Why it matters. A dental or finance buyer can see the boundary immediately.
Example. A clinic expects a tooth chart or a profit figure. Neither is part of this edition.
Who uses it. Nobody, in this edition. Not available.
Status: Not included. Origin: Not included. Candidate 1.2.104 is not an accepted commercial release. Excluded by the current product contract or the pilot ledger. Not a delivered feature.
There is no separate WordPress-free booking engine in this edition.
Not included
The product decision says a customer may use an Ascent-hosted WordPress installation, a link, or an embed. The software itself is the plugin. Embed on another site was not re-tested end to end.
Before you start. Not included.
Limit. Hosting the plugin for a business is an operating arrangement, not a different codebase, and it was not deployed from this guide.
Technical details
Why it matters. Buyers can tell a hosted WordPress installation from a different product.
Example. A buyer asks for a booking site with no WordPress. That is not this candidate.
Who uses it. Nobody, for a second engine. Not available.
Status: Not included. Origin: Not included. Candidate 1.2.104 is not an accepted commercial release. Excluded by the current product contract or the pilot ledger. Not a delivered feature.
Publishing is evidenced. A separate pause and reopen control was not found in the 1.2.104 ledger.
Not determined
New installations start unpublished and can be published. The ledger does not record a later pause. An early decision said there was no unpublish control in the first owner slice.
Before you start. Unresolved.
Limit. Do not describe publication as a pause switch. Date closures, where previously evidenced, close a day rather than the whole product.
Technical details
Why it matters. Owners need to know whether they can close the page temporarily. This guide does not claim that switch.
Example. The owner tries to pause a live page for a holiday week. Unverified as a named control. Closing a date is a different, earlier feature.
Who uses it. The business owner. Unknown as a distinct control.
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.
Importing past treatments, invoices, and invites is not included.
Not included
The older pilot left historical treatment import unavailable. Candidate 1.2.104 did not re-open it in the ledger used here.
Before you start. Not included.
Limit. Viewing history that is already stored is a different question, and it was not given a fresh 1.2.104 demonstration either.
Technical details
Why it matters. An existing clinic will not be told that a spreadsheet of old treatments can be loaded.
Example. An owner uploads a file of past visits. That import is not part of this edition.
Who uses it. Nobody, in this edition. Not available.
Status: Not included. Origin: Not included. Candidate 1.2.104 is not an accepted commercial release. Excluded by the current product contract or the pilot ledger. Not a delivered feature.
A stored deposit marker is a different question from collecting a deposit. Online appointment payments and deposits are not included. The evidence used here does not say whether a stored marker exists on its own.