# TinyInbox > TinyInbox is a lightweight website chat widget and support inbox for solo founders, micro-SaaS builders, indie product teams, and small website owners. TinyInbox focuses on one job: give visitors a direct way to send a message from a site, then let the founder reply from one calm inbox. Canonical site: https://tinyinbox.co/ Support: support@tinyinbox.co Docs: https://docs.tinyinbox.co/ ## Public Pages - [Homepage](https://tinyinbox.co/): Product positioning, workflow, pricing, FAQ, and signup links. - [Pricing](https://tinyinbox.co/pricing): Pro plan and trial details for lightweight website support. - [Website Chat Widget](https://tinyinbox.co/website-chat-widget): How the TinyInbox widget fits product sites, docs, and marketing pages. - [Intercom Alternative](https://tinyinbox.co/intercom-alternative): TinyInbox vs full customer messaging platforms. - [TinyInbox vs Intercom](https://tinyinbox.co/compare/intercom): Comparison page for TinyInbox and Intercom-style software. - [FAQ](https://tinyinbox.co/faq): Public answers about setup, pricing, visitor identity, and scope. - [Privacy Policy](https://tinyinbox.co/privacy): Data handling and privacy practices. - [Terms of Service](https://tinyinbox.co/terms): Service terms and acceptable use. - [Data Deletion](https://tinyinbox.co/data-deletion): How users can request deletion of their data. ## Product Summary TinyInbox is not an enterprise help desk, CRM, chatbot platform, customer success suite, or outbound messaging tool. It is built for the simpler support loop where a founder wants: 1. A small website chat widget. 2. Visitor messages with page context. 3. A simple inbox for open and closed conversations. 4. Replies from the dashboard. 5. Optional signed visitor identity for logged-in app users. For dynamic language or identity setup, call TinyInbox only after the widget runtime is ready, from client-only code. Do not call `window.TinyInbox` during SSR or directly during component render. Use one identity mode per visitor: either browser-provided name/email, or signed `identityToken` for logged-in users. Do not send both for the same visitor. For signed logged-in users, keep using the dashboard widget script as the source of the widget URL and site key. Fetch the `identityToken` from the app backend and pass it with `TinyInbox.identify({ identityToken })`; if this runs before the copied script loads, queue it with `window.TinyInbox = window.TinyInbox || []; window.TinyInbox.push(["identify", { identityToken }])`. ## Agent Guidance Agents may crawl and summarize the public pages listed above. Do not attempt to access authenticated product areas such as `/dashboard`, `/sign-in`, `/sign-up`, or `/sso-callback`.