Use this route when a team needs help with knowledge ingest, connector testing, widget install, or readiness checks before first traffic.
Support and trust
Use one route for product questions, launch support, and operational issues.
Before customers depend on ChatRobot, they should know where billing, setup, incident, and privacy questions will go and what information to include.
Launch support
Incident details
Billing follow-up
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
Operating model
What the product actually manages.
Use this route for plan questions, Stripe customer issues, missing credits, or subscription state mismatches.
Include the workspace name, affected agent, approximate timestamp, connector involved, and whether the issue is blocking live traffic.
Use this route for questions about conversation retention, uploaded knowledge, processors, or workspace-level data handling expectations.
If a public status page is not configured, customers should use the support route for active incident updates.
1. Primary contact channel
Email [email protected] with the workspace name, contact details, and the affected public URL or widget origin.
2. For launch blockers
Include the readiness blocker, connector test result, or smoke-check output so the issue can be triaged without asking the team to repeat setup steps.
3. For incident response
Include timestamps, affected connectors or models, and whether public visitor traffic should be paused while the issue is reviewed.
4. For privacy or legal requests
Privacy requests should go to [email protected], and the operator should provide the current subprocessor list on request.
Ready