Pre-release Documentation for Ascent Direct Booking. Not yet approved for commercial release. View availability details
Every capability is listed here. A row is a catalogue record, not a promise that the capability is included.
New pilot result on 1.2.104
The site administrator designates the first business owner. A second owner designation is refused.
It does not create a second business, and it does not prove a hosted signup shop. The 1.2.104 candidate is not commercially accepted.
New pilot result on 1.2.104
The designated owner manages the business from the owner app and does not receive the WordPress administrator capability.
Specialist clinical screens are not granted by this capability. A practitioner’s own diary is a different boundary and was not the check in this row.
New pilot result on 1.2.104
New self-service installations start unpublished. Publishing opens the booking page after the readiness checks pass.
A separate pause-and-reopen control was not in the 1.2.104 ledger. Publishing is not the same as a software subscription being paid.
Previously accepted slice, carried forward
Setup progress is stored so a refresh does not pretend the business is finished.
This guide did not re-run an interrupted setup on 1.2.104.
New pilot result on 1.2.104
The business chooses IDR or GBP, and a timezone, before real catalogue and booking records lock that money context.
It does not convert historical rows into another currency. It does not collect payment. This guide does not certify every timezone in the world.
New pilot result on 1.2.104
English and Bahasa Indonesia can be used for the interface. The business’s currency and timezone stay as stored.
Right-to-left layout is not included. Not every label is translated. The pack is not a translation of clinical records.
New pilot result on 1.2.104
The edition is one WordPress installation and one database for one business.
This is not a multi-location switcher and not a WordPress-free engine. Shared multi-tenant hosting is a later architecture, not this candidate.
Not determined
A business type can be stored. This guide does not list which words each type changes.
A business type does not add clinical tools, payments, or a shop. Do not treat an unresolved preset as a feature.
Earlier result reused. Not rerun.
The owner can set appearance colours and reset them. The 1.2.104 ledger reused a narrow-screen check rather than repeating it.
Logo upload, background images, and policy text were not part of that reused colour check. This is not a reseller licence to redistribute the software.
Not determined
Logo, written policies, and embedding the booking form on another site are not given a passing 1.2.104 check in this guide.
Do not tell a customer the form can be embedded until that installation has been checked. Configurable branding is not a right to resell the plugin.
Previously accepted slice, carried forward
The owner can add and edit a bookable service, including who can perform it.
Several services in one visit were not re-verified. Archiving a service was not repeated in the 1.2.104 ledger. The whole candidate is not commercially accepted.
New pilot result on 1.2.104
An upgrade kept stored service timings and buffer values on the cloned site.
Keeping a stored buffer is not a new editor demonstration. This guide does not claim a specific buffer length as a default for every business.
Not determined
It is not determined whether a customer can book more than one service in a single visit on 1.2.104.
Do not sell combined treatments as included. Booked historical lines, where they exist, are a different fact from a new combined booking.
Not determined
It is not determined here what a customer sees after a service is archived, beyond the upgrade keeping stored timings.
Do not promise that historical booked prices survive every catalogue edit until that case is re-checked. Do not promise that archiving deletes history either.
New pilot result on 1.2.104
The owner can store a product with an image, separate from bookable services.
A product list is not an online shop. No order, delivery, or refund flow is included. Public display of products was not the check that passed.
Previously accepted slice, carried forward
The accepted services slice includes weekly hours for the business and for a practitioner.
Split-shift editing was not repeated on 1.2.104. Practitioner hours are not the same thing as a room or a second staff member being free.
New pilot result on 1.2.104
Activating the candidate on a populated clone kept the stored hours.
Preservation is not a new editor test. It does not prove a backup restore.
New pilot result on 1.2.104
The fresh pilot approved a leave record.
This single approval does not demonstrate sick leave, partial-day leave, and closures as three separate controls. Closures were shown on an earlier candidate.
Shown on an earlier local candidate, not repeated on 1.2.104
An earlier candidate found a closed day outside the short list and reopened it.
Not repeated on 1.2.104. Reopening cancels the closure block; it does not move existing appointments in the evidence cited here.
Shown on an earlier local candidate, not repeated on 1.2.104
An earlier candidate showed a split Monday and a Wednesday with no public times.
Do not describe split shifts as freshly proved on 1.2.104. A missing time can also be caused by leave, duration, or staff eligibility.
Not determined
It is not determined whether staff can save a visit outside the public booking window on 1.2.104.
Do not promise out-of-hours booking. Public rules and staff-created visits are different, and only the public side has fresh booking evidence.
Previously accepted slice, carried forward
A service can be limited to the practitioners who are allowed to perform it.
Eligibility is not a qualification check and not a clinical credential. It does not assign a room or an assistant.
New pilot result on 1.2.104
The owner invites a practitioner, can resend, and the previous link stops working when a new one is issued.
The pilot did not revoke staff 1. Invitation mail in the pilot was local capture. This does not create a login for customers.
New pilot result on 1.2.104
Revoking a practitioner blocks that person’s access. The evidence used a staff member who was not the business owner.
The 1.2.104 pass did not revoke the owner. Do not describe revocation as deletion of clinical or booking history. Pausing new work and removing login access were distinguished in the earlier proof, not re-run here.
Not determined
A practitioner viewing only their own assigned work was not re-checked in the 1.2.104 pilot notes used here.
Do not promise self-service reschedule or cancellation by a practitioner. Those were explicitly unavailable in the older pilot note and were not re-opened here.
Older clinic source only
Older source has optional team, room, and equipment ideas. They are not part of the verified standard pilot.
Not counted as a generally offered 1.2.104 feature. Not a guarantee of conflict-free multi-room scheduling.
New pilot result on 1.2.104
A signed-in customer can book a published service and the pilot stored one visit.
Local capture is not inbox delivery. This does not take payment. An interrupted command in the fixture stayed running and was not turned into a second success.
New pilot result on 1.2.104
Guest booking is off until the business opts in. On the fresh pilot the guest form rejected an invalid email and focused that field.
Do not say every guest attempt stores a booking. Do not say guest booking is on for a new business. Account sign-in remains the path that stored the fresh pilot visit.
Shown on an earlier local candidate, not repeated on 1.2.104
An earlier candidate stored guest bookings, including one with a blank optional phone.
Not repeated as a stored visit on the fresh 1.2.104 pilot. A guest record is not the same as a claimed account.
Shown on an earlier local candidate, not repeated on 1.2.104
On an earlier candidate, two concurrent bookings for one practitioner stored one visit.
This is not a promise about overlapping different services, shared rooms, or a second practitioner. A running interrupted command in the fresh fixture occupied a slot and was left as a fixture, not cleaned up into a pass.
New pilot result on 1.2.104
The fresh pilot’s customer, owner, and booking screens had no horizontal page overflow at 390 and 320 pixels.
No overflow in that check is not a promise about every future panel. It is not a native-app claim.
New pilot result on 1.2.104
The owner can mark a visit as a no-show, and the owner list shows that status.
A no-show is not a refund and not a payment event. Notification of the customer was not part of this check.
Shown on an earlier local candidate, not repeated on 1.2.104
An earlier candidate let the owner create a visit, move it, and mark it complete.
Do not describe move and complete as freshly proved on 1.2.104. Completing a visit is not a payment capture.
Shown on an earlier local candidate, not repeated on 1.2.104
An earlier candidate let the owner book a named customer and assign a practitioner.
Phone-number handling and duplicate-customer checks were not part of the fresh pilot write-up.
New pilot result on 1.2.104
A customer can finish a password reset from the locally captured reset link.
The owner does not see the new password. This check is not account erasure and not a change of the login name.
Not determined
The ledger says account claim exists in source. The fresh evidence that passed was the password reset, not a guest-to-account claim walked through in the browser.
Do not promise that every guest visit becomes an account. Guest booking itself is opt-in.
Not determined
Search, contact details, visit history, and ordinary internal notes were not given a fresh 1.2.104 demonstration in the ledger used here.
Ordinary notes are not clinical notes. This guide does not say who else can read them on 1.2.104.
Not determined
Partial anonymisation of one ordinary customer was exercised only on the later unaccepted working tree, not on frozen 1.2.104.
This is not complete erasure, not a retention policy, and not a legal certification. Clinical notes and booked prices remained in that later check.
New pilot result on 1.2.104
If a change request is decided twice, the second decision conflicts and the visit stays at the original time.
The system does not approve a request by itself. A conflict does not notify the customer in this result. Do not describe the customer’s accept button as proved on 1.2.104.
Not determined
Owner approval, decline, and a counter-proposal were proved on earlier candidates. The fresh 1.2.104 check was the conflict that keeps the original time.
A proposal is not an automatic reservation in any evidence cited here. Do not say the customer can accept a counter-offer on 1.2.104.
Not determined
Waitlist signup and notification were not re-verified on 1.2.104.
Do not say a waitlist reserves a slot, sends automatically, or is included in 1.2.104.
New pilot result on 1.2.104
The owner can keep registration questions in draft and publish a version. Saved answers from the previous version stay attached to their visits.
This is not a general-purpose form builder and not clinical consent. Editing a question does not rewrite old answers in the upgrade result. The pack does not translate every author-written question until a translation is saved.
Not determined
A registration question is not the same thing as a booking policy or a marketing opt-in. The difference was not given its own 1.2.104 check.
Do not describe a registration answer as marketing consent or as clinical consent.
New pilot result on 1.2.104
A signed-in booking captured confirmation mail locally, with one notification attempt and two attributable subjects.
Capture is not delivery. This is not SMS. A failed or uncertain send must not be described as received.
Earlier result reused. Not rerun.
Reminder scheduling was reused for 1.2.104 because the ledger says those files were unchanged. It was not rerun.
Not rerun on these bytes. Not inbox delivery. Not SMS or WhatsApp. Review-request mail is a different template and is not included.
Shown on an earlier local candidate, not repeated on 1.2.104
Earlier candidates previewed and reset email text. The fresh 1.2.104 ledger did not repeat template editing.
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.
Not determined
A deliberate test to an authorised recipient was not a 1.2.104 ledger item.
Do not enter a customer’s address as a test. External delivery remains unproved.
Older clinic source only
Older clinic source includes doctor notes. The standard 1.2.104 pilot did not re-verify it.
Not a medical-record system, not a certification, and not counted as a generally offered 1.2.104 feature. Public documentation is not permission to open a real record.
Older clinic source only
Older clinic source includes clinical photos and consent. The standard 1.2.104 pilot did not re-verify it.
Not a medical-record system, not a certification, and not counted as a generally offered 1.2.104 feature. Public documentation is not permission to open a real record.
Older clinic source only
Older clinic source includes clinical registration forms. The standard 1.2.104 pilot did not re-verify it.
Not a medical-record system, not a certification, and not counted as a generally offered 1.2.104 feature. Public documentation is not permission to open a real record.
Older clinic source only
Older clinic source includes aftercare and recommendations. The standard 1.2.104 pilot did not re-verify it.
Not a medical-record system, not a certification, and not counted as a generally offered 1.2.104 feature. Public documentation is not permission to open a real record.
Older clinic source only
Older clinic source includes treatment plans and maintenance intervals. The standard 1.2.104 pilot did not re-verify it.
Not a medical-record system, not a certification, and not counted as a generally offered 1.2.104 feature. Public documentation is not permission to open a real record.
New pilot result on 1.2.104
Visits keep a currency and a storage scale. A language switch does not rewrite them.
Recorded value is not cash received, not a deposit, and not a refund. Absence of a payments table is not proof that payment rows were preserved.
Older clinic source only
Older source has credit, commission, and consultation-waiver tools. They are not re-verified as offered 1.2.104 features.
Commission is not payroll. Credit is not a card refund. A waiver is not a payment processor.
Older clinic source only
Older source names activity, retention, and follow-up lists. Their figures were not re-defined or re-run for 1.2.104.
No accuracy claim, no forecast promise, and no performance guarantee. Profit calculation is not included.
Not included
Software subscription purchase, renewal, cancellation, and update licensing are blocked. No merchant is connected.
There is no approved monthly price in this guide. Blocked entitlement is not a free licence and not a grace-period promise. Existing booking data is not deleted by this statement.
New pilot result on 1.2.104
The candidate can be activated on a new site and again on a populated clone. Sampled appointments, prices, and answers stayed.
This is not a host backup and not a restore of private files on a production server. No payments table was present to preserve. Do not activate the review package on a live site from the local notes.
New pilot result on 1.2.104
The documented rollback for this candidate is to put back the previous frozen plugin installer. Tables are not dropped as the rollback step.
There is no partial database restore in the instructions. Host checks for private files, cache, and real mail were not run.
Shown on an earlier local candidate, not repeated on 1.2.104
Earlier candidates exported appointment rows, including amount, currency, and scale, and refused a subscriber.
The file is not a full backup and not a clinical archive. Do not send it to support with customer details still in it.
Not determined
A safe support note leaves out customer identity, medical detail, passwords, and payment data. No new support address is published here.
This local guide has no contact form and does not store what you type. Robots rules are not an access control.
Not included
This edition does not collect deposits or online appointment payments.
A stored price is not a received payment. A software subscription, which is also blocked, would not by itself take appointment money.
Not included
Google Calendar, Apple Calendar, and similar sync are not included.
The in-product diary is not an external calendar feed.
Not included
SMS is not included. WhatsApp delivery is not a working integration in this edition.
A phone number stored on a customer is not a WhatsApp conversation. Manual copying of a message is not an integration.
Not included
Product catalogue records do not include a cart, stock deduction, shipping, or refunds.
Do not infer a shop from a product photo.
Not included
A builder for arbitrary forms is not included. Registration questions are a narrower tool and are evidenced separately.
Clinical forms in older source are historical and are not this builder either.
Not included
Google review request emails are not sent.
Stored historical review rows, if an old installation has them, are not a working sender.
Not included
Dental charting and profit calculation are not included.
A service category called dental would not add a chart. Recorded appointment value is not profit.
Not included
There is no separate WordPress-free booking engine in this edition.
Hosting the plugin for a business is an operating arrangement, not a different codebase, and it was not deployed from this guide.
Not determined
Publishing is evidenced. A separate pause and reopen control was not found in the 1.2.104 ledger.
Do not describe publication as a pause switch. Date closures, where previously evidenced, close a day rather than the whole product.
Not included
Importing past treatments, invoices, and invites is not included.
Viewing history that is already stored is a different question, and it was not given a fresh 1.2.104 demonstration either.