Live chat software
The only live chat that ends in a shipped feature.
Live chat inside your product. Juno, the AI agent, answers from your docs and hands off to your team when it matters. Feature requests become votes on your roadmap, and support email lands in the same inbox.
Already on UserJot? It's one toggle in Settings.
Linear Integration
Create and update Linear issues from requests, and sync status back to the roadmap.
Teams already on UserJot
The feedback loop
Every "any plans to add X?" becomes a vote.
Every support tool eventually hears the same message: any plans to add X? In a normal helpdesk that becomes a ticket, the ticket gets closed, and the signal dies 01.
In UserJot, Juno searches your public feedback board the moment the question lands. If the request exists, the customer sees it as a card right in the chat, votes on it, and follows it with one confirmation 02. If it does not exist, Juno drafts it and files it with their blessing 03.
From there the normal UserJot loop takes over. The request climbs the board, lands on your roadmap, and when you ship it, everyone who asked hears about it. Support stops being a cost center that archives demand and starts being the place your roadmap gets its evidence 04.
Meet Juno
An AI agent that knows your product and knows its limits.
Juno takes the first reply on every new conversation. It answers from the websites you crawl and the files you upload, keeps the customer posted while it researches, and hands off to your team the moment a question needs a human. Tone, reply length, and formality are settings, not prompts to maintain. Pause it any time and new conversations go straight to your team.
Trained on your docs
Point Juno at your website and upload your guides. It answers from what you gave it and never invents a product fact.
Hands off like a pro
Low confidence, a safety concern, or a customer asking for a person all trigger a handoff. Juno steps aside for your team.
Speaks their language
Juno replies in the customer's language. Your team reads and answers any thread in their own, with translation built in.
Hands off to your team when it matters.
Shared inbox
A queue your team can finish.
The inbox opens on the Queue: conversations waiting on your team, oldest first. Juno-handled threads stay out of it until they need a human. Answer, resolve, and the next one loads. It works like an inbox you can actually finish.
Support email included
Forward your support address and email becomes conversations in the same queue as chat, with threading and attachments intact.
Snooze and reminders
Snooze a conversation for the team or set a personal reminder with a note. Due reminders pull the thread back into your queue.
Internal notes
Discuss context privately inside the thread before you reply. Notes stay with the conversation and are never shown to the customer.
Customer context
Every thread carries who the customer is: their activity, device, location, language, and the feedback requests linked to them.
One widget
Same widget. Now with chat.
Conversations does not add another floating bubble to your product. Messages joins feedback, roadmap, and updates in the widget you already installed, so customers get support, share ideas, and see what shipped without leaving your app.
No new install
Already running the widget? Turning on Conversations adds the Messages page to it immediately, with nothing new to deploy.
One launcher, one badge
Unread replies and fresh changelog posts share the same launcher and the same badge, so there is one place for customers to look.
Attachments and screenshots
Customers attach images and files in chat, and your team sends them back. Bug reports arrive with the evidence already attached.
Real presence
Customers see when your team is actually online, backed by operator schedules instead of a green dot that is always on.
Hi there 👋
How can we help?
Send us a message
Typically replies in a few minutes
Compared
A support tool that knows what your roadmap is.
Intercom, Crisp, and Help Scout are good at support. They stop at the resolved ticket. Conversations picks up where they stop.
| Feature | UserJot Conversations | Standalone live chat |
|---|---|---|
| Pricing | Flat, unlimited teammates | Usually per seat, sometimes per resolution |
| AI agent | Included, answers from your docs | Often a paid add-on |
| Feature requests from chat | Become votes on your public board | Closed as tickets |
| Public roadmap and changelog | ||
| Widgets in your product | One, shared with feedback | One more bubble |
| Support email in the same inbox | ||
| Notifies the customer when it ships |
Pricing
Free while in beta.
Conversations is free during the beta on every plan, including the free one. When it graduates it joins the paid plans, and beta workspaces get notice before anything changes. Like the rest of UserJot, it is never priced per seat, so your whole team can work the inbox.
Getting started
Live chat on your site this afternoon.
Install the widget
One script tag in your document head. If you already run UserJot for feedback, skip to step two.
Turn on Conversations
Flip the switch in Settings → Conversations. Chat appears in your product immediately and the inbox shows up in your dashboard.
Teach Juno and add your team
Crawl your website, upload your docs, and add operators with their schedules. Forward your support address when you are ready for email.
Full setup details in the help center and the widget docs.
Start chatting
Your users are already in your product. Talk to them there.
Turn on Conversations and your widget grows a Messages page. Juno takes the first reply, your team takes the hard ones, and feature requests turn into roadmap votes.
Live chat, AI answers, and a shared inbox, free while in beta.
No credit card · Turn it off any time
Questions
Frequently asked, plainly answered.
Setup, the AI agent, email forwarding, pricing, and how live chat connects to your feedback board.
Live chat software lets your customers message your team in real time from inside your product or website, instead of writing an email and waiting. UserJot Conversations adds a Messages page to the same widget that already handles feedback, roadmap, and changelog, so customers ask questions right where they hit the problem.
Install the UserJot widget with one script tag, then turn on Conversations in Settings. Chat appears right away, with nothing else to install. If you already run UserJot for feedback, enabling Conversations is a single toggle.
Yes. Conversations is free while in beta, on every plan including the free one. When it leaves beta it will join the paid plans, and existing workspaces get generous notice before anything changes.
Juno reads the websites you crawl and the files you upload, then answers customer questions from that knowledge with first replies in seconds. It posts a short update while it researches longer questions, matches the tone and length you configure, and replies in the language the customer writes in. When it is not confident, it hands the conversation to your team instead of guessing.
Juno hands off. The customer is told a teammate is stepping in, your team gets a push notification immediately and an email if nobody reads it, and Juno stays quiet until a human hands the conversation back. A customer can also just ask for a person and Juno will step aside.
Yes, and this is the part other live chat tools miss. When a customer asks about a feature, Juno searches your public feedback board, shows the matching request as a card in the thread, and with the customer's confirmation adds their vote or files a new request. When you ship it, they hear about it.
Yes. Forward your support address to UserJot and inbound email becomes conversations in the same queue as chat. Replies go out from the same thread, attachments work in both directions, and a customer replying to the email continues the conversation.
No. Every UserJot plan has flat pricing. Your whole team can join the inbox, and inviting one more person to help with support never changes your bill.
You set weekly schedules per operator, and customers see honest presence. When nobody is available and a conversation is waiting on your team, an automatic away reply sets expectations once per conversation. You can also show a reply-time expectation like "typically replies in a few minutes".
Yes. The widget is framework-agnostic and SPA-friendly. One script tag in your document head works the same in React, Vue, Svelte, Angular, Next.js, and anything else that runs in a browser. It is responsive on mobile browsers and inside webviews.
Yes. Set the greeting, decide whether to ask for email and name before or during a chat, choose the reply-time expectation, and control whether new conversations can be started at all. The widget picks up your workspace branding automatically.
Those are standalone support tools. UserJot puts live chat, an AI agent, and a shared inbox in the same product as your feedback board, roadmap, and changelog, in one widget and one dashboard. Support conversations turn into roadmap votes instead of dying in a ticket archive.