Chat inside the application
Available on every screen, so a question gets asked at the moment it occurs rather than being abandoned.
Support
Answer the question without switching tabs.
Support inside the product is worth far more than support beside it — because the person asking is already looking at the thing they are confused by.
A chat widget on its own is not support. What makes it useful is context: who the person is, what plan they are on, what screen they are looking at, and what they just tried to do. When that travels with the conversation, the first reply can be the right one. And when a question needs a human, the handover carries everything rather than starting with "can I take your account details?"
Off until you need it. Turning it on is a toggle — not a project, not a rebuild. See how capability arrives as you grow.
Providers
What we connect to
Available means built and running in production today. On request means we will build it for your application — it is not pre-built, and we will not imply otherwise.
Available
- Tidio
- Intercom
On request
- Zendesk
- Freshdesk
- Crisp
- HubSpot Service Hub
What you get
The part that is not just an API key
The user identified automatically
The conversation arrives with the account, the role, the plan and the recent activity attached, so nobody spends the first three messages establishing who is asking.
A first line that answers from your help centre
The assistant answers from the help centre we generate from your application, citing the article it used so a person can verify rather than trust it. No separate knowledge base to write and no second copy to keep in step — see Help centre.
Escalation that keeps the context
When it needs a human, the whole history and the account context go with it. No repeating.
Conversations become records
Support history attached to the customer, so patterns are visible and the same problem is not solved from scratch five times.
For example
What this looks like in practice
A product with non-technical users
The people using it will not read documentation. In-app chat with context is the difference between adoption and quiet abandonment.
Deflecting the repeat questions
An agent answers the eighty per cent that are documented and routes the rest to a person who can actually help.
Onboarding a new account
Proactive messages at the moments people typically get stuck, rather than a generic welcome sequence nobody reads.