Someone on your site has a question right now.

Both, and that is rather the point. The chat widget on your site and the shared inbox behind it are one product. A visitor's live chat, their emails, and your team's replies all sit in the same conversation instead of two systems that never quite agree.

One script tag before the closing </body> tag. No build step and no package to install, so it works on Webflow, WordPress, Shopify, a Rails app, or a hand-edited HTML file. Most people are live in two minutes.

Email takes over. The visitor leaves an address, tiny.help emails you, and you reply from your own inbox, and your reply lands back in their chat. If they have already closed the tab, they get it by email, and whatever they write back threads into the same conversation.

Yes. The Live page lists everyone browsing your sites at that moment, not only the ones who open the chat: the page they’re reading, their city, how long they’ve been there, the browser they’re on, and any data your site passes through. It’s per site, and off until you switch it on.

Yes. @name them in a private note and the conversation pins to the top of their inbox, pushes to their phone, and emails them if they’re away. It stays pinned until someone marks it done. Nothing is routed away from anyone else: assignment adds a nudge, it never makes the inbox go quiet for the rest of the team.

Only if you switch it on, and it’s off until you do. It answers from the pages it crawled and the guides your agent wrote, and from nothing else, so it can’t invent a setting or a price. Every answer links to the page behind it. It sticks to how-to, setup, pricing and product questions and says so out loud when a question isn’t one of those, and it never touches billing, cancellations, refunds, legal or security. It stops the moment one of your people starts typing.

Yes. Switch on Book a demo for a site and visitors pick a day and a time right in the chat, in their own time zone, from your hours minus anything busy in your calendar. You both get a calendar invite, and the booking lands in the conversation. It is on every plan. How Book a demo works.

No. The assistant that answers your customers runs on our account and is included on every plan, with no per-answer fee. A Claude or ChatGPT plan is what lets your own agent do the setup: read your code, write your support guides, and upload them once you have read every word. Worth having, not required. See how setup with AI works.

Price shape, mostly. The big desks charge per seat and then again per AI resolution, at $0.49 to $0.99 an outcome, so a small team gets expensive quickly. tiny.help is $9 a month for one site and one person, or $29 for three of each, and the assistant is included rather than metered. It is deliberately smaller: their bots resolve more than ours does, and if you need workflow builders and a ticketing taxonomy, buy one of those instead. Here's the honest comparison with Intercom, including when you should stay put.

Yes. The whole desk, not a cut-down version. Two taps to add it to your home screen on iPhone or Android and it behaves like a native app, with push notifications the moment a message arrives. It updates itself when we ship.

$9 a month for the Solo plan, up to $199 for Agency, and every plan includes every feature. They differ in how many sites and people they cover. Every account starts with a 14-day free trial. See pricing for the detail.