Enterprise
For larger teams — and a straight answer about what that means today.
EzyConn Enterprise is a commercial tier, not a different product. It raises the limits and adds terms — invoicing, a data processing agreement, a named contact. It does not yet add the access controls a mature procurement review will ask for, and we would rather tell you that on this page than in the third meeting.
- 1
- capability gated above ProfessionalAnd it is “sso”, whose own status is not built.
- 8
- controls we do not havelisted in full further down, not omitted
- 0
- certificationsno SOC 2, ISO 27001, HIPAA or PCI, and no audit under way
Available today
What you actually get.
Each of these is a mechanism in the product, not a category on a slide.
- Higher limits
- Up to 999 agent seats, 999 workspaces and 999 active integrations, with message volume agreed rather than metered at a published tier.
- Role-based access
- Permissions are checked per action on the server. Being an administrator does not bypass a permission check — that is enforced, not a convention.
- Audit logs
- Available from Professional upward. Who changed what, when.
- Workspace isolation
- Every workspace-owned record is scoped at the API, not filtered in the interface. One workspace cannot read another’s conversations, bookings or contacts.
- A record of every run
- Each process run keeps its own timeline — which step ran, what the customer answered, which rule decided what, and how it ended. You can reconstruct a conversation from months ago.
- Human handoff you control
- Which conditions escalate, which team receives it, and what the customer is told. The transcript goes with it.
- Your own provider keys
- Bring your own OpenAI, Anthropic or Google key and your traffic runs on your account, under your terms with that provider. Same for Twilio on the phone line.
- Data export and erasure
- Export on request; erasure enforced at sign-in, so a deleted account cannot authenticate.
Not available
The controls we do not have yet.
If any single line here is a hard requirement, EzyConn is not the right fit today. That is a better outcome for both of us than finding out during onboarding.
- SSO / SAML
- Reserved to this tier in our own matrix, and not built. Sign-in is email and password, with optional MFA.
- SCIM provisioning
- Not built. Seats are managed in the portal.
- Field-level masking
- Not built.
- Data residency / multi-region
- No US, EU or APAC placement option.
- Self-hosted, private cloud, air-gapped
- None. EzyConn runs on our infrastructure.
- SOC 2, ISO 27001, HIPAA, PCI
- No certification held and no audit completed.
- Uptime SLA
- We do not have the operating history to underwrite one.
- CRM / PMS / EHR / DMS / OMS connectors
- None. Data leaves through Zapier or a signed webhook.
How a larger rollout actually goes
- 01Pick the processesFrom the 24 published ones. Your industry has three; most workspaces start with one.
- 02Configure them with your dataHours, timezone, services, durations, prices, coverage. No engineering.
- 03Connect the channelsWebsite first. Then the phone line, WhatsApp, Slack or Teams as you want them.
- 04Run one locationWatch the run timelines. Adjust the wording and the rules.
- 05Add the restEach additional workspace is configuration, not a rebuild — the process shapes are shared.
Enterprise limits
- Agent seats
- 999
- Workspaces
- 999
- Active integrations
- 999
- AI credits / month
- 200,000
- Messages / month
- By agreement
- Storage
- 10 GB
These come from the same generated matrix as the pricing page.
The gap list is the point.
If one of the controls above is a hard requirement, EzyConn is not the right tool yet and a call will not change that. If none of them are, the limits and the terms are worth a conversation.