Works alongside your PMS
Cedar Desk is an operational recovery layer. The PMS remains the source of record for clinical and appointment truth.
Buyer diligence for a controlled recovery layer.
Cedar Desk works alongside the PMS to keep missed-call recovery, diary recovery, recall follow-through, manual review, and booked outcomes visible. This page explains the current posture plainly, including what is live, manual-first, pilot-only, planned, or not supported.
At a glance
Trust posture in under 30 seconds.
Seeded public preview
The public preview uses seeded demo data. It proves workflow shape, not live clinic operation.
Review stays visible
Manual review and staff takeover stay visible when Cedar Desk should not safely progress a case.
Controlled rollout
Live rollout depends on branch readiness, data path, messaging setup, and launch review.
Pilot trust pack
A buyer can inspect the current pilot posture.
The trust pack explains what Cedar Desk currently does, what is manual, what is not live yet, what data is needed, how rollout works, and how outcomes are measured.
Manual-first rollout
Live use starts with controlled manual review before any wider automation posture is expanded.
PMS boundaries
Cedar Desk keeps recovery work visible but does not replace the PMS diary or silently edit patient records.
Measured outcomes
Value reporting stays tied to booked outcomes and unresolved cases, not vanity activity.
Data ownership and responsibilities
The practice owns its practice data.
Cedar Desk may handle practice, branch, contact, PMS, diary, call, message, and patient-like operational records during a rollout. The practice remains responsible for its source systems, patient relationship, and decisions made from the source of record.
Website and demo requests
The public site collects business contact and demo-request context so Cedar Desk can respond and assess rollout fit.
Public preview
Seeded preview data is not live patient data and must not be treated as customer reporting evidence.
Live workspace use
Live use is scoped during rollout review and depends on the agreed PMS/data path and operational rules.
What stays practice-owned?
PMS records, clinical decision-making, patient relationship, opt-out handling, and final booking confirmation remain owned by the practice unless a separate reviewed agreement says otherwise.
Access, permissions, and audit trail
Support access is bounded and visible.
Workspace access is tied to account state, and paid access should come from verified Stripe events rather than redirects alone. Support links require a reason and expiry, are one-time use, and show support mode in the workspace.
Access controls
- Account access is email-based and entitlement-aware.
- Support links are clinic-specific.
- Support links require a reason and expiry.
- Support mode stays visible while active.
Audit posture
- Privileged support actions are designed to be auditable.
- Operational setup actions are kept tied to branch context.
- Manual takeover remains a first-class workflow state.
How should a buyer inspect this?
Review the account and settings surfaces during a founder-led demo, then confirm who has workspace access before live rollout.
Hosting, encryption, and backups
Hosting posture is stated plainly, without fake badges.
Cedar Desk runs the public site, server, storage, and workspace through its configured hosting/provider environment. Security and backup posture should be reviewed as part of rollout diligence rather than assumed from a certification badge.
Environment
Public and private surfaces are separated by route, account, and workspace posture.
Secrets and credentials
Integration credentials and webhook secrets are treated as setup-controlled operational material.
Backups and retention
Retention and offboarding are handled through founder-led review until broader policy materials are legally reviewed.
Manual review and operational controls
Manual review is a safety feature.
Cedar Desk keeps ready, blocked, pending, booked, and manual takeover states visible. It is designed to make booking truth explicit rather than collapsing unresolved work into activity metrics.
Review points
Urgent wording, uncertain replies, delivery issues, and blocked booking paths can remain visible for staff review.
Pause and takeover
A clinic or workflow can pause when live recovery should stop for review.
Booked outcomes
Booked in PMS, pending reply, blocked, and manual takeover are kept separate.
Integrations and subprocessors
Current capability boundaries are explicit.
| Capability | Current status | What Cedar Desk does | What remains manual or practice-owned | Evidence or route | Last reviewed |
|---|---|---|---|---|---|
| Missed-call recovery | Pilot | Turns missed demand into visible conversation and review work. | Clinic number readiness, patient judgement, and final booking truth. | Conversations preview | 8 May 2026 |
| Diary recovery | Pilot | Surfaces open chair time and candidate context for refill work. | Availability rules, offer approval, and PMS confirmation. | Diary preview | 8 May 2026 |
| Recall follow-through | Pilot | Groups recall follow-up into visible workflow state. | Consent, opt-outs, uncertain replies, and clinical escalation. | Recall preview | 8 May 2026 |
| Manual review and takeover | Live now | Labels review, blocked, and takeover states directly in the workflow. | Staff decisions and practice policies remain practice-owned. | Tasks preview | 8 May 2026 |
| Booking outcome visibility | Live now | Separates booked, pending, blocked, and manual outcomes. | The PMS remains the source of record for appointments. | Overview preview | 8 May 2026 |
| PMS write-back | Manual-first | Keeps booking follow-through visible before write-back is relied on. | Direct PMS confirmation remains manual unless evidence proves otherwise. | Settings preview | 8 May 2026 |
| Dentally data path | Pilot | Supports setup posture around a Dentally-oriented data path. | Credential approval, verification, and source-record accuracy. | Settings preview | 8 May 2026 |
| CSV fallback | Manual-first | Can keep setup moving when direct access is not ready. | Export accuracy, import review, and stale-data risk. | Settings preview | 8 May 2026 |
| Twilio messaging | Pilot | Supports controlled messaging only after number and webhook checks. | Regulatory readiness, opt-outs, clinic number ownership, and pause decisions. | Settings preview | 8 May 2026 |
| Multi-branch support | Pilot | Scopes rollout by branch readiness and operational rules. | Branch-by-branch setup, data path, and messaging readiness. | Pricing notes | 8 May 2026 |
| Clinical or emergency triage | Not supported | Does not provide clinical advice, diagnosis, or emergency triage. | Clinical decisions and urgent escalation remain with the practice. | Terms | 8 May 2026 |
| Broad enterprise IAM | Planned | Keeps the current clinic workspace model clear first. | Large enterprise identity patterns need separate review. | Contact | 8 May 2026 |
Subprocessors and vendors used where configured
Likely near-term providers include the hosting/provider environment, Stripe for billing, Twilio for SMS/telephony where enabled, Calendly for scheduling, AI providers where configured, and monitoring or alerting tools. Exact posture is confirmed during rollout review.
Incident and support posture
Problems should create visible handoffs, not false certainty.
If something is unavailable, blocked, or uncertain, the buyer and practice should see a labelled state and a recovery path. Cedar Desk should not hide unresolved setup, webhook, billing, or messaging issues behind success copy.
Support path
Existing customers use account or support contact routes for workspace, billing, or rollout questions.
Incident posture
Incidents should be reviewed with branch context and a clear explanation of what changed.
Payment posture
Checkout is verified before success is shown, and payment does not mean instant live launch.
Legal documents and updates
Supporting pages should look maintained.
Privacy
Plain-English summary of public-site and demo-request data handling.
Read privacyTerms
Website, preview, commercial, and no-instant-go-live public terms.
Read termsChangelog
Product-stewardship notes showing visible website, preview, and workflow updates.
Read changelog