Why does EzyConn publish what it cannot do?

Because the alternative is that you find out after you have paid. Most of what goes wrong in a software purchase is an assumption nobody checked. This page is the list of assumptions we would otherwise be relying on you not to check.

Does EzyConn integrate with my CRM or practice-management system?

No. EzyConn has no CRM, practice-management, dealer-management, EHR, order-management or field-service connector, and no external calendar sync. Data leaves through Zapier or a signed webhook, both of which are live.

Can EzyConn handle medical questions or emergencies?

No. For dental, healthcare and aesthetics EzyConn does reception work only: scheduling, changes and routing. It does not assess symptoms, advise, triage or handle emergencies, and there is no crisis protocol in the product.

Is EzyConn SOC 2 or HIPAA certified?

No. EzyConn holds no SOC 2, ISO 27001, HIPAA or PCI certification, and SSO/SAML is not built. If a certification is a hard requirement for you today, EzyConn is not the right fit yet.

Scope

What EzyConn does not do.

Name: EzyConn
Brand: EzyConn

Every vendor publishes a list of what their product does. This is the other list. It exists because the thing that kills a software purchase is almost never a missing feature — it is an assumption nobody checked until after the invoice.

24 processes are published with their real status, and 15 of them carry a named limit rather than being described as finished. The same standard applies here.

Systems we do not connect to

EzyConn keeps its own diary. It does not read or write anyone else’s. Everything that needs to leave goes through Zapier or a signed webhook.

No CRM connector: HubSpot, Salesforce and Zendesk are declared in the product’s own integration catalogue and marked coming soon. They are not built.
No practice-, dealer- or order-management system: No PMS, EHR, DMS or OMS integration of any kind. An appointment EzyConn takes lives in EzyConn until something you build moves it.
No external calendar sync: Not Google Calendar, not Outlook, not Calendly. Availability is worked out only from bookings EzyConn made itself — so nothing stops your team double-booking a slot through their own calendar.
No field-service platform: Jobs do not flow to an FSM board.

Things the conversation cannot do

The agent answers, qualifies and books. It does not sell, and it does not decide anything clinical.

No stock or inventory: There is no column anywhere that could hold a quantity, a size, a variant or a SKU. EzyConn can quote a price from your list; it cannot tell anyone what is on the shelf, or in which shop.
No payments or deposits: Money never changes hands inside a conversation. There is no payment step.
No clinical questions, triage or emergencies: For dental, healthcare and aesthetics, EzyConn does reception work: scheduling, changes and routing. It does not assess symptoms, advise, triage, prioritise by urgency, or page anybody. There is no emergency protocol, and we are not going to imply there is one.
No vehicle data: A VIN, registration, make, model or mileage can only arrive as free text in a note. Nothing decodes it, and there is no recall or parts lookup.
No structured health or identity data: A date of birth or an insurance policy has no field to live in. Free-text answers are stored as written, unencrypted, with no consent record — which is exactly why the health verticals are administrative only.

Limits inside things that do work

These are the reductions worth knowing before you set EzyConn up, not after.

A postcode, not a street address: A dispatched job carries the postcode that passed the coverage check. The process never asks for the door number, so a van cannot be routed from the booking alone.
Three services per workspace: The service list replaces three fixed slots rather than growing. A business offering more than three is asked to choose between them.
A postcode list or prefix — never a radius: Service area is a list of postcodes or a set of prefixes, in one country per workspace. “Everywhere within 20 miles” cannot be expressed.
Urgency is recorded, not acted on: “Emergency” is written onto the appointment for whoever works it. There is no dispatch queue, no priority and no SLA — an emergency and a routine job are offered the same times in the same order.
One diary, not one per person: Bookings are made against the workspace. There is no per-staff calendar, so “with Jo” is never offered.
One appointment at a time: No recurring bookings, no series, no course of six sessions.
Confirmations by email only: A booking sends a confirmation email, best-effort. A cancellation sends the customer nothing. No process sends an SMS.
No workflow builder: You choose a published process and configure it with your own hours, services, prices and coverage. There is no drag-and-drop canvas, and we removed the one that looked like there was.
Two automation triggers: Automations fire on a new conversation or a new message. Scheduled, sentiment-based and intent-based triggers are named in the product but nothing runs them.

What the safety gate is, and is not

Every message to the website widget passes a deterministic check before anything else happens — no model call, about half a millisecond, on by default, and it cannot be switched off.

It protects the website widget only: WhatsApp, Telegram, Slack, Teams, email and the phone line do not run it. That is a real gap and we would rather you heard it from us.
It refuses; it does not resolve: It declines to answer and points to the ordinary urgent channels. It summons nobody, does not know what country the caller is in, and is not a crisis protocol.
It does not catch everything: It recognises a good share of unseen phrasings, not all of them, and the classifier reads English. We do not publish a recall figure, because a number would invite you to treat it as a guarantee.
It is not compliance: It is a safety floor. It is not clinical governance, and it will not survive somebody deliberately working around it.

Company and platform

We are new. These are the things a procurement review will ask for, and the honest answers.

No SOC 2, ISO 27001, HIPAA or PCI certification: None held, and no audit completed. We are not going to print the logos.
No SSO, SAML or SCIM: Reserved to the Enterprise tier in our own plan matrix and not built. Sign-in is email and password with optional MFA.
No data residency or regional hosting: No US, EU or APAC placement option, and no multi-region deployment.
No self-hosted, private-cloud or air-gapped option: EzyConn runs on our infrastructure. There is no on-premise build.
No uptime SLA: We do not have the operational history to underwrite one, so we do not offer one.
No customers we can name: No logos, no case studies, no testimonials, no user counts. When we have permission, you will see real names.
No native mobile SDKs: There is a mobile app for you and your team. There is no iOS or Android SDK for embedding EzyConn in your own app.

If none of that is a dealbreaker, the rest works.

Answers on seven channels including your phone line, deterministic rules instead of guesswork, and a real appointment at the end of it.

See the 24 processes Pricing

Why does EzyConn publish what it cannot do?: Because the alternative is that you find out after you have paid. Most of what goes wrong in a software purchase is an assumption nobody checked. This page is the list of assumptions we would otherwise be relying on you not to check.
Does EzyConn integrate with my CRM or practice-management system?: No. EzyConn has no CRM, practice-management, dealer-management, EHR, order-management or field-service connector, and no external calendar sync. Data leaves through Zapier or a signed webhook, both of which are live.
Can EzyConn handle medical questions or emergencies?: No. For dental, healthcare and aesthetics EzyConn does reception work only: scheduling, changes and routing. It does not assess symptoms, advise, triage or handle emergencies, and there is no crisis protocol in the product.
Is EzyConn SOC 2 or HIPAA certified?: No. EzyConn holds no SOC 2, ISO 27001, HIPAA or PCI certification, and SSO/SAML is not built. If a certification is a hard requirement for you today, EzyConn is not the right fit yet.