Appointment booking for the dental front desk —reception work, and nothing beyond it.

Reception work only — scheduling and admin. No clinical questions, no triage.

• It does reception. It does not do dentistry

  No process asks a clinical question and none answers one. It never presents itself as a clinician and never decides what somebody needs — it books the appointment they name, exactly as a receptionist would. If a patient volunteers something clinical mid-conversation, nothing inside a process refuses it: the turn falls through to the general assistant, which answers from the content you trained it on. That is the reason to publish administrative content only.

• No price is ever given for implants, aligners or cosmetic work

  And that is deliberate. A price list holds one flat price with no per-tooth, per-stage or per-plan variant, so a figure in a chat window would be a guess a patient would hold you to. The process establishes that the question is about money, takes the contact details, and puts your treatment coordinator on it.

• Nothing about suitability is asked or answered

  Whether somebody can have an implant, whether aligners will work for them, how long treatment would take — all clinical assessments. The process gets a person to them and offers no view of its own. The "next stage of my treatment" branch books nothing at all, because deciding which appointment a stage needs is a judgement the software may not make.

• There is no recall system

  An appointment has one date and no due-date, interval or recall field, and there is no scheduled trigger in the product. "You are due your six-month check-up" cannot be represented as data and nothing here sends it. Your recall runs exactly where it runs today.

• Nothing reaches a practice-management or records system

  There is no connector to any practice-management system, patient-record system, or clinical software of any kind — not built, and not declared as coming. Appointments live in EzyConn and reach anything else through Zapier or your own signed webhook. The words PMS, EHR, HIPAA and BAA appear on this page only in this sentence, saying that none of them applies.

• What a patient types is stored as plain text

  Free-text answers land verbatim in a plain, unencrypted note on the appointment. There is no consent record, no retention rule and no age gate. That is why every question in these three processes is worded to invite a scheduling answer and nothing more — and why you should not add one that invites anything else.

• One appointment, one person, per conversation

  A parent registering a family books one appointment here and arranges the rest with reception. A patient part-way through a course of treatment moves or cancels them one at a time. And the answer about a previous practice is recorded for reception, not acted on: no notes or radiographs are requested from anybody, and no other practice is contacted.

• Identification is not verification

  Moving or cancelling an appointment is matched on a name, an email and a phone number typed into an anonymous chat window. The match is scoped to your practice, refuses to guess when more than one appointment fits, never reads back internal notes, and tells somebody who does not supply both facts nothing at all. It is still two facts a stranger could know. A practice that considers that too weak a key for a cancellation should not switch that process on.

• No calendar sync, of any kind

  Not Google Calendar, not Outlook, not Calendly. Availability is worked out only from appointments EzyConn made itself, so a time you blocked out in your own calendar is still offered to a customer.

• No system connectors

  There is no customer-record, scheduling-system, order or field-service connector in the product. Everything that leaves does so through Zapier or a signed webhook to your own endpoint.

• The confirmation is an email, never a text message

  No process sends SMS. The confirmation email is best-effort: if the queue behind it is down, a real appointment can be made without the email arriving. A cancellation sends the customer nothing at all — the chat window is their only confirmation.

• Nothing is paid for in the conversation

  There is no payment step anywhere in a process. No deposit, no card, no voucher, no balance.

• A service area is a list of postcodes, not a radius

  You give a list of postcodes or a prefix to match on, for one country. A radius is refused outright, and so is covering everywhere.