Product overview
Features, platforms, channels, trial and licensing without marketing ambiguity.
Procurement preparation
Build a verifiable document package for your environment
Base materials describe the product and architecture, while contractual commitments, SLA and security requirements are prepared after discovery.
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
Architecture map
Local data, push gateway, external APIs and operational owners.
Pilot plan
Verification criteria, constraints, roles and expected outcomes.
How it works
Send requirements
Do not include passwords, tokens or business secrets in the initial form.
Clarify boundaries
We mark existing capabilities and items requiring development or a separate agreement.
Agree on documents
The final package is tied to the actual delivery and responsible parties.
Self-hosted
What to know upfront
Conversations, files, users and settings stay on your server.
- EasyChat does not claim unverified certifications, registers or compliance levels.
- Commercial proposal and SLA are prepared individually.
- Public documentation remains the source for base technical requirements.
Frequently asked questions
Can we get a standard overview?
Yes. After a request, we identify the required scope and current material version.
Is there a standard SLA?
No universal promise exists; SLA depends on infrastructure and agreed support.
Can customization be included?
Yes, after a separate requirements and support-boundary estimate.
Next step
Request materialsVerify EasyChat with your own workflow
Start free. Move to a license only after the widget, operator panel and phone work together in your environment.