Terms
Use boundaries matter
Dchat terms should keep launch scope, AI provider responsibilities, support ownership, and acceptable automation boundaries clear.
Customer responsibilities
Customers own approved knowledge, website placement, escalation staffing, and decisions about sensitive automation.
- Knowledge
- Staffing
- Approvals
AI limitations
AI output can be useful and still require review, especially for account changes, legal questions, refunds, or safety-sensitive topics.
- Review
- Sensitive topics
- Escalation
Service evidence
Availability, compliance, and residency claims should be read from signed agreements and published evidence, not assumptions.
- Availability
- Compliance
- Residency
Keep launch promises aligned with actual configuration and signed customer agreements.