Helpful by default.Human when it counts.
Bring customer conversations, your knowledge base, and an AI assistant together. Give people a useful answer—and your team the context to help.
- Answer with your knowledge
- Keep people in the loop
- Remember the customer
The whole conversation
The answer. And everything around it.
Move from the queue to the conversation to the customer details. Filter by state or assignee, search messages, and see recent events without losing your place. The person behind the question stays in view.
- Chat and email in a shared inbox
- Contact, Stripe, actions, and event details
- Open, Closed, and Spam queues
Your product, in its own words
Give your AI something useful to work with.
Connect your knowledge articles and configure how the agent represents your business. Add custom tools or import an OpenAPI definition when you want the agent to work with your own systems.
- Answers grounded in configured knowledge
- Custom tools and OpenAPI import
- Agent identity and workspace configuration
Human when it matters
Make the handoff feel like a conversation.
When someone needs your team, give the conversation an owner. A confirmed handoff moves it from the AI to a teammate. Customer context and the conversation history go with it.
- Confirmed AI-to-human handoff
- Named ownership and assignee filters
- Office hours and per-conversation AI cost
Customers
Faster answers, fewer repeats.
“Snippet went in before lunch. By mid-afternoon I was watching real visits and answering our first chat.”
“We shipped Thursday and I forgot the trial follow-up. The workflow sent it anyway.”
“The assistant handled the how-do-I questions from our docs. The tricky one came to me with the full thread attached.”
“Three invoices became one. I invited our new hire and the price didn't move.”
“A chargeback came in Tuesday. The payments, emails, and activity were already in the case.”
“Signup notifications took a minute to turn on. The events were already there from analytics.”
Questions about Support.
And straight answers.
Yes. Confirmed handoff assigns the conversation to a team member. Replying from the inbox also takes ownership of the conversation.
Yes. Email conversations require the appropriate sending and receiving domain configuration so replies can be threaded correctly.
You can configure custom tools and import OpenAPI definitions. The capabilities depend on the endpoints, permissions, and behavior your team configures.
Yes. Widget settings include branding, greeting, workspace name, and AI agent identity, alongside appearance configuration.
Support supports signed customer identity and project-scoped access. Configure the widget’s security for your implementation; the Security page explains the underlying controls.
Context is a better starting point.
A conversation belongs alongside your customer relationship. Give your support team a clearer starting point and your customers less explaining to do.
Start with support