1. Intended use
ChatRobot is intended as a workspace-owned sales and support layer for published website knowledge, visitor conversations, and routed handoff into systems the customer already operates.
Service terms
Launch ChatRobot only when the operating owner is ready to control the workflow.
These terms describe the intended operating boundary for the product: customer-owned knowledge, operator-controlled routing, verified launch gates, and responsible public deployment.
Operator responsibility
Connector-first routing
Launch verification
6 min
from website URL to first agent
4 routes
email, webhook, HubSpot, Zendesk
1 script
to launch the widget on a live site
Knowledge pages
42 indexed
Ready routes
3 configured
Credit mode
Starter / Venice
Widget conversation
Business accounts can use invoice billing and get priority support.
Please have sales follow up.
Routed action: Lead Capture -> CRM Webhook
Latest handoff
Lead captured
Ops Director at Northline Parts
Source used
Billing FAQ + Pricing article
Delivery
Webhook accepted in 241 ms
2. Customer responsibility
The workspace owner is responsible for the accuracy of uploaded knowledge, the allowed actions enabled on each agent, the connector destinations configured, and the legality of the public deployment.
3. Provider dependencies
AI responses, mail delivery, billing, and routed actions depend on configured third-party providers. The product should not be treated as production-ready until those providers are verified end to end.
4. Launch gating
A workspace should only be exposed to production traffic after readiness checks, connector proofs, allowed origin rules, billing state, and operational monitoring are confirmed.
5. Acceptable use
Customers should not use the service to publish deceptive responses, route abusive or unlawful traffic, or expose end users to unsupported flows that the workspace operator does not monitor.
6. Suspension and access control
Operators can suspend workspaces, revoke invites, restrict admin access, and rotate API or widget credentials when a deployment no longer meets the required operating standard.
7. Customer paperwork
If a customer requires a data processing addendum, the operator should provide the current agreement before launch approval.
Ready