Pre-release Documentation for Ascent Direct Booking. Not yet approved for commercial release. View availability details
Short answers for this candidate. Where a control was not proved, the answer says so.
It runs appointment booking for one business on a WordPress installation: services, people, hours, a customer booking page, and an owner app. Candidate 1.2.104 is a local pilot, not an accepted commercial release.
Appointment businesses that can work as one business on one site. A specialist clinic can read the clinical section, but those tools are older source and are not the standard pilot.
Yes, one installation can be a single business. The fresh pilot did not re-test a diary where the owner is the only bookable person.
Yes. The fresh pilot invited a practitioner, set a password from the latest link, and later blocked that access.
A WordPress installation for that business. This guide does not certify a PHP, database, or host range, and it does not authorise a live install.
The dedicated booking page is the path the pilot published. Embedding the form on another website was not re-tested.
No. The edition is one business for each installation. A second business needs its own site.
Clinical notes, photos, clinical registration, aftercare, credits, and commissions are older source. They are not counted as generally offered 1.2.104 features. Payments, calendar sync, SMS, and WhatsApp are not included at all.
A business name, the currency (IDR or GBP), the timezone, at least one service, the people who perform it, and the weekly hours. Have a backup plan before any real upgrade.
The site administrator installs and designates the first owner. A second designation is refused. After that, the owner uses the owner app without the WordPress administrator capability.
They belong in owner setup. The fresh pilot’s passed identity evidence is the published currency and timezone, not a field-by-field address check.
A business type can be stored. This guide does not list what each type renames, and a type does not add clinical tools.
Choose IDR or GBP, and the business timezone, before real services and visits exist. The fresh pilot used IDR and Asia/Makassar. Changing currency after records exist was refused on an earlier candidate.
The accepted owner-foundation slice stores setup progress. The fresh pilot did not re-test an interrupted return. Progress is not the same as publishing.
The required pages, a resolved currency and timezone, and password recovery using the current site address. Publication stays closed if that recovery link does not match.
Publishing is evidenced. A separate pause and reopen control was not in the 1.2.104 ledger. Closing one date was shown on an earlier candidate.
Logo upload was not part of the passed appearance check. Do not treat it as verified.
Saved colour, muted text, a dark treatment, and reset were reused for 1.2.104. Background images were not part of that check.
Heading colour was part of the appearance evidence. A full list of editable sentences was not re-checked. Interface language does not rewrite your own service names until you save a translation.
Policy text was not a passed 1.2.104 check. A registration question is not a policy.
Appearance preview was part of the earlier evidence reused for colour. Question preview was part of the publish flow. This guide’s journeys are written descriptions, not a live preview.
The reused reset put the tested appearance fields back. It is not described as deleting services. Two-tab reset was not repeated.
Use the booking page created at setup. Embed instructions were not re-tested, so this guide does not supply a copy-and-paste embed.
The fresh pilot found no horizontal overflow at 390 and 320 pixels on the customer, owner, and booking screens it opened, and Tab moved from the skip link.
In the owner catalogue, add the service in the business currency and choose who can perform it. That editor was accepted on 22 October 2026 and not re-run on the fresh pilot.
Category grouping was not given its own passing check in the 1.2.104 ledger. Create the service itself first.
Enter them in the service editor, in the business currency. Stored timings survived the later upgrade. A price in the other currency is refused.
It is time the visit occupies besides the customer-facing duration. Stored buffers were kept on upgrade. A fresh edit of those minutes was not the pilot check, and a free-looking start can still be too short.
Set eligibility on the service. It was part of the accepted slice. It is not a professional qualification.
That is not determined. Do not promise combined visits.
Upgrade kept stored timings and prices. An archive or hide action was not re-tested, so this guide does not promise the customer-facing result.
A catalogue stores a name, price, and image. The fresh pilot previewed an image. A cart, stock, shipping, and refunds are not included.
Create the practitioner and send an invitation. The fresh pilot resent it, rejected the old link, and set a password from the new link.
Designate yourself as owner and add the bookable practitioner record the service needs. The fresh pilot did not run a one-person diary as its only case.
The owner uses the owner app without the WordPress administrator capability. A revoked practitioner was refused the staff diary. A positive own-work view was not re-checked on 1.2.104.
Use eligibility. Shared-room or assistant rules are not part of the standard pilot.
Resend replaces the previous link. The old link was refused. Local mail capture is not proof the message left the server.
Revoke the practitioner. The fresh proof blocked staff 2 and did not describe deleting visits. It did not revoke the owner.
That screen was not re-checked in the fresh pilot notes. Self-service reschedule by a practitioner should not be promised.
The owner and a practitioner are different access levels. Revocation removes the revoked person’s staff diary. Clinical screens are not granted by ordinary owner access.
In the weekly hours editor from the accepted slice. The fresh pilot preserved stored hours and did not repeat the editor.
An earlier candidate showed a morning block and an afternoon block. It was not repeated on 1.2.104.
The fresh pilot approved a leave record. Finding and reopening a closed day was an earlier candidate.
Both exist in the accepted weekly-hours slice. A person on leave is a further limit. The fresh pilot did not redraw the combination.
The service may not fit, the eligible person may be on leave, or a buffer may occupy the gap. An empty diary is not proof that the time is bookable.
The whole duration, including stored preparation or cleanup, has to fit. Stored buffers survived upgrade.
That override was not shown in the 1.2.104 ledger. Do not promise it.
On an earlier candidate, two concurrent bookings for one practitioner stored one visit. A second decision on a change request left the visit at the original time.
In the owner app. The fresh pilot’s owner list showed the no-show and the unmoved visit. A full day-and-week demonstration was not the fresh check.
Practitioner filtering was not given a fresh 1.2.104 pass in the ledger used here.
An earlier candidate let the owner store a named visit. It was not repeated on the fresh pilot.
Eligibility chooses who can perform the service. Changing the person on an existing visit was not a fresh 1.2.104 check.
An earlier candidate moved a visit. The fresh pilot did not repeat move. Check the stored time before trying twice.
Cancellation plus a notification result was not a fresh 1.2.104 check. Confirmation capture on a new booking is a different event, and capture is not inbox delivery.
The fresh pilot recorded a no-show. Complete was proved on an earlier candidate and not repeated.
Read the stored visit. A second conflicting change decision did not move it. If mail was only captured locally, do not call it delivered.
The directory was not given a fresh 1.2.104 demonstration. Do not use older clinic screens as proof of the standard owner list.
Only if the owner opts in. The fresh pilot used the guest form to reject an invalid email and did not store a new guest visit. An earlier candidate did store guest visits.
The ledger says claim exists in source. The fresh demonstration that passed was a password reset, not a guest claim walked through on screen.
They use the latest reset link. The fresh pilot completed that reset from the captured key and signed in. The owner never sees the password.
That self-service profile edit was not a fresh 1.2.104 check. Password reset was.
They submit a request. The fresh evidence is what happens when it is decided twice, not a new customer screenshot.
The fresh pilot showed a second decision conflicting and the time staying put. Propose-and-accept was an earlier candidate and the customer reply was not re-checked.
That customer reply was not re-checked on 1.2.104. Do not say the proposed time is reserved.
Add it, preview, and publish. Draft questions stay off the live form. The upgrade clone published a new version.
Required questions are enforced for the context they target. The exact required switch was part of that question system and was not redrawn as a separate fresh click-through in this guide.
Answers stay with the visit that stored them. Who else can open them was not a fresh access matrix in the 1.2.104 rows used here.
On the upgrade clone, publishing version 7 left the existing answers unchanged. An unknown version is rejected as stale.
They are different, and neither was given its own 1.2.104 control check. A registration answer is not marketing consent.
Ordinary notes were not re-demonstrated. Clinical notes are a different, historical tool. A customer export was refused for a subscriber account on an earlier candidate.
Registration questions publish a version and keep old answers. Clinical registration, photos, and doctor notes are older source and are not the standard question editor.
Names, contact details, dates of birth, medical text, passwords, reset links, and payment data. These guide pages do not send what you type.
A signed-in booking captured confirmation mail locally. Reminder evidence was reused and not rerun. Other template names in source are not proof they are sent. Review requests are not sent.
Preview and reset were shown on an earlier candidate, not repeated on 1.2.104.
A test-send button was not a 1.2.104 ledger item. Do not use a customer’s address as a test.
They are different fields, and this guide does not have a passed 1.2.104 check that separates them. Local capture still does not prove delivery.
The reused Makassar example displayed 9:30 am on the business clock. It was not rerun for 1.2.104.
The fresh capture does not define those words. Say “captured locally” only when a local record exists, and do not call that delivered.
Look for a local capture, confirm you are not expecting SMS, and remember external delivery was not proved. The troubleshooter does not resend the message.
No. Email capture is the communication evidence. WhatsApp delivery is not a working integration.
It would pay for the booking software, not for a customer’s appointment. Purchase is blocked because no merchant is connected, and this guide states no price.
There is no live subscription to inspect. A development test double is not a bill and not a plan.
Do not retry a real card from this candidate. Entitlement checkout was not exercised. Booking publication is a separate step and does not mean the software has been paid for.
That grace or end-of-access behaviour was not exercised. The upgrade evidence is about plugin activation, not about a paid subscription lapsing.
The subscription would be your payment for the software. Appointment value stored on a visit is your business’s price. Neither one is collected by this candidate.
No.
A visit can store a currency and an amount. That is recorded value, not cash received. Credits and commission ledgers are older source and are not in the standard pilot count.
An earlier candidate refused that change. Saving the same currency again is allowed. The fresh pilot did not convert historical rows.
Check publication, the service, hours, leave, eligibility, and whether the whole duration fits. The troubleshooter lists those without changing settings.
The page may be unpublished, or the service may not be the active one you expect. Embed on another site was not re-tested.
Appointments use the business clock. A language switch does not change the timezone. The customer’s device zone can look different without changing the stored business time.
Use the latest reset or invitation link. A revoked practitioner is refused. Do not send passwords to support.
Read the stored record before repeating the action. A second conflicting decision did not move the visit.
An earlier candidate exported appointment rows with amount, currency, and scale, and refused a subscriber. It omitted schedules, question definitions, and email bodies. The fresh pilot did not repeat the download.
The pilot activated a fresh site and upgraded a populated clone. Rollback is putting back the previous plugin installer. Take a database and private-file backup from the same moment. A live host restore was not run.
Use the support route the installation already has. Include the page, the time, and the on-screen result. Remove names, contact details, medical text, and secrets. This guide does not add a support address.
No. Online appointment payments and deposits are not included. A stored price is the value recorded on the visit.
No. External calendar sync is not included.
No. They are different, and this candidate completes neither collection path. No public price is stated.
No. Use one installation for each business.
No. Clinical tools in older source are not turned on by a label, and they are not a certified medical-record system.