Appointment scheduling for physio, dietetics and podiatry —front-desk work, and it asks nothing about anybody’s health.

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

• No clinical question is asked, and none is answered

  It never presents itself as a clinician and never decides what a person needs. It takes the appointment they name. 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. Publish administrative content only.

• The "when suits" question carries no urgent option, on purpose

  It is a scheduling preference and it is worded to stay one: the next appointment you have, a particular day, or flexible. There is no emergency and no urgent choice, because those words invite a judgement about somebody’s condition that the product is not allowed to make.

• Insurance and cost are never touched

  There is no payer or clearinghouse connector, no coverage record and no patient-cost calculation in the product. "Am I covered?" and "what will this cost me?" are never answered, because a wrong yes produces a bill nobody agreed to.

• It never asks why

  A cancellation reason is a clinical fact more often than not, the note field on an appointment is plain unencrypted text, and there is no consent record — so the question is not asked at all rather than asked and thrown away.

• No named clinician, and no course of sessions

  There is one diary for the practice and no per-clinician calendar, so "with Sarah" is never offered. And one appointment is booked per conversation — a course of six sessions is six separate conversations, because an appointment has no series or recurrence.

• Nothing reaches a patient-record system

  There is no connector to any patient-record, practice-management or clinical system — not built, not planned. The words EHR, PMS, HIPAA and BAA appear on this page only in this sentence, saying that none of them applies. Appointments leave through Zapier or your own signed webhook.

• The team is named to the patient, not delivered to a queue

  A routed enquiry tells the patient which desk picks it up and writes that on the conversation. There are no teams or queues in the product to deliver it into, so whoever picks the conversation up sees which desk it was meant for.

• Identification is not verification

  Moving or cancelling is matched on a name, an email and a phone number typed into an anonymous chat window — scoped to your clinic, refusing to guess between two matches, and telling somebody who gets it wrong nothing at all. It is still two facts a stranger could know.

• 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.