Pilot with acceptance criteria
Channels, roles, integrations and verifiable acceptance checks are agreed before work begins.
Enterprise route
Deploy a unified customer request workspace in your infrastructure
Start with a limited pilot, verify channels, data storage and operations, then scale the system deliberately.
Free start: 300 delivered operator push targets. The web chat keeps working after the limit; FCM, WebPush and SMS become available with a license.
What you get
Technical boundaries
The team documents what stays local and which external APIs are actually required.
Operations plan
Owners are assigned for backups, cron, updates, monitoring and escalation.
How it works
Describe the environment
Share CMS, channel count, operators and infrastructure constraints.
Agree on a pilot
Select one working scenario and a measurable verification set.
Receive a rollout plan
After the pilot, define rollout scope, documentation and support.
Self-hosted
What to know upfront
Conversations, files, users and settings stay on your server.
- SLA, implementation schedule and services are not automatically part of the base license and require a separate agreement.
- Production access and secrets follow least-privilege rules.
- Procurement documents reflect the real configuration without unverified certificates or claims.
Frequently asked questions
Can we run a pilot before full rollout?
Yes. This is the recommended way to verify integrations and operations.
Is it on-premise?
EasyChat runs on the customer's server; the exact boundary depends on CMS and infrastructure.
Is an SLA included?
Support and SLA terms are discussed separately and exist only after a signed agreement.
Next step
Discuss a pilotVerify EasyChat with your own workflow
Start free. Move to a license only after the widget, operator panel and phone work together in your environment.