Preview the chat
Enter a domain and inspect the standard Free appearance before signup.
For SaaS products
Help users reach the next successful step in your product
Add documentation, onboarding guides, plan rules, and common answers. Visitors get help on the website, while technical or account-specific cases move to your team with the full context.
Quick answer
Quick answer
Add documentation, onboarding guides, plan rules, and common answers. Visitors get help on the website, while technical or account-specific cases move to your team with the full context.
What matters
- ✓Support before and after signup
- ✓Answers from your documentation
- ✓Human handoff for technical cases
How it works
From preview to working chat
Three clear steps without hidden settings or a required payment.
Create the project
Activate the account, confirm the domain, and receive the working code.
Start replying
Connect AI, agents, and the channels available on the selected plan.
What you get
Support before and after signup
Explain the product, plans, first setup, and common workflows in one channel.
Answers from your documentation
AI uses selected help pages, FAQs, and instructions that your team controls.
Human handoff for technical cases
An agent continues when the answer requires account, billing, or incident checks.
Controlled team access
Give people access only to the projects and areas they need.
Common SaaS support scenarios
Onboarding
Guide users through project creation, first configuration, and the correct dashboard section.
Plans and limits
Explain published terms and send disputed billing questions to a person.
Documentation discovery
Find a relevant guide and turn it into a clear next step.
Bug reports
Collect the device, symptoms, and reproduction steps before routing the request.
How it works
Collect approved sources
Add documentation, pricing, setup guides, and known limitations.
Define routes
Separate general questions, technical requests, billing, and sensitive topics.
Review unanswered questions
Improve knowledge and handoff rules using real conversations.
Clear support boundaries
Useful when
- ✓users get lost in documentation or first-run setup
- ✓many questions can be answered from published rules
- ✓AI and agents need one shared history
Integration is required when
- !the answer depends on private account data
- !the chat must change a subscription, invoice, or user setting
- !incident status must be read from another system in real time
Questions about this use case
Can AI see a user's account data?+
Not unless a separate secure connection is implemented. By default it answers from the project knowledge you provide.
Can billing and technical questions be separated?+
Yes. Use rules, folders, requests, and assignment to the appropriate agent.
Can one account support several products?+
Yes. Use separate projects when products need different knowledge, teams, or settings.
Put support next to your product
Open a domain preview and review the visitor's first support step.