Other services connect to your schedule. They don’t replace it.
Cloud Dental Office holds the calendar, the patient record, and the balance. Other services connect at the edges. Here is what connects today and how.
Zocdoc
New patients book through Zocdoc and land on your schedule.
Your open times on Zocdoc come from the same calendar your staff work from, the same one your website booking reads. When a time is booked or blocked in the office, it comes off Zocdoc. When a patient books on Zocdoc, the appointment comes back to your schedule with the patient attached.
Confirmation: Zocdoc bookings are confirmed automatically. Before an appointment is confirmed, the time is re-checked against your calendar; if it’s no longer open, the booking isn’t made. Unlike website requests, your staff don’t approve each Zocdoc booking first.
Built and tested against Zocdoc’s sandbox. Going live for a practice needs Zocdoc’s approval. A Zocdoc scheduling integration is in pilot with 3rd Set Smiles.
What Zocdoc can and can’t see
- Sees: the open times you publish, by provider, location, and visit type.
- Doesn’t see: your patient records, charts, or other appointments.
- Cancellations and reschedules stay in step both ways.
- If Zocdoc is down, your schedule keeps working.
Zocdoc is a separate company. Using its scheduling API is not an endorsement by Zocdoc, and we don’t claim a partnership or certification.
Your practice website
A “Book online” button that shows real open times.
Your website shows open times from your calendar. A patient picks one and sends a request. Your staff see it in Appointment Requests, match the patient, and approve it. If the booking service can’t take a request, it says so right away, so your website can fall back to email instead of losing it.
For your web developer
The availability and booking-request APIs are documented on Scheduling APIs.
Cloud Health Office
Our sister platform for claims.
Claims go out through Cloud Health Office, built by the same team. What comes back is the claim’s status, a timeline, the patient’s portion, and the payment, posted to the ledger. Your staff never see payer file formats or clearinghouse names.
More detail
Stedi
Eligibility checks, sent to the payer.
When your staff check a patient’s coverage, the request goes to the payer through Stedi, a healthcare clearinghouse, and the answer comes back to the patient’s record. Each practice gets its own Stedi account, and its key is kept in a secure vault and used only for that practice.
Being set up practice by practice for the pilot.
What your staff see
Coverage, deductibles, and maximums in plain language. Clearinghouse names and payer file formats stay out of the way.
Stedi is a separate company. Using its APIs is not an endorsement by Stedi.
Stripe
Patients pay their balance online, into your own account.
Your practice connects its own Stripe account. Patients pay on Stripe’s hosted checkout page, and the money settles in your account, not ours. The payment posts to the patient’s ledger only after Stripe confirms it. Card numbers never touch Cloud Dental Office.
Built and tested in Stripe’s test environment. The first live payments come with the pilot.
Your account, your payouts
Stripe onboards the practice directly and pays out to your bank. Turning off online payments in Cloud Dental Office doesn’t close your Stripe account.
Stripe is a separate company. Using its payment APIs is not an endorsement by Stripe.
Need something to connect that isn’t listed?
Tell us what your office uses today. Founding practices shape what gets connected next.