# Build brief — a focused alternative to LiveChat > **Verdict:** Partly, if you narrow it · **Buildability:** 53/100 · **Category:** Customer Support > **Source:** https://www.canitbevibecoded.com/livechat > Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from LiveChat. Verify current pricing and capabilities before acting. ## Context **LiveChat** — Provide reliable website chat with routing, transcripts, and canned replies. It currently costs $24/mo. The core loop is buildable, but a dependable replacement becomes a substantially larger project. For LiveChat, provide reliable website chat with routing, transcripts, and canned replies. The hard boundary is global chat delivery, mobile apps, staffing tools, integrations, and support, plus channel integrations and support operations. This brief describes a focused, single-operator replacement for the part of LiveChat that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest. ## What you are building Receive website chat messages, route them into a shared inbox, reply from one place with canned replies, and retain searchable transcripts of every conversation. - Build a focused single-user workflow with real persistence, search, and export. - A responsive interface with real empty, loading, success, and error states. ## Requirements ### Functional - Docker. - PostgreSQL. - Public HTTPS deployment. ### Data and integrations - Email or chat channel credentials. Each of these needs a real account, credential, or quota. Set them up before writing feature code. ### Non-functional - Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support. - Security: server-side secrets, validated input, and no credentials in the client bundle. - Reliability: retries with backoff on external calls, and a clear failure state when a provider is down. - Portability: the operator can export their data and leave without losing it. ## Implementation brief Build a personal replacement for LiveChat in an empty repository. Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, WebSockets, and Docker Compose; do not offer alternative stacks. The core loop is: receive website chat messages, route them into a shared inbox, reply from one place with canned replies, and retain searchable transcripts of every conversation. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Implement one workspace, agents, contacts, inboxes, conversations, messages, labels, and assignment. Provide a website chat widget with reconnect, unread counts, file limits, and clear availability state. Create a shared inbox with filters, collision warnings, notes, canned replies, and searchable history. Add email notifications, browser notifications, and an immutable assignment and status log. Implement spam controls, attachment scanning hooks, retention settings, export, and contact deletion. Ship Docker Compose, backups, health checks, migrations, and a documented admin recovery flow. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out many social and messaging channels. Deliberately leave out AI agents trained on proprietary support data. Deliberately leave out enterprise workforce management, SSO, and compliance. Finish by running the tests and listing the exact commands used. ## Delivery standard - Inspect the repository first, then write a short implementation plan before writing code. - Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data. - Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations. - Include responsive layouts plus genuine empty, loading, success, validation, and failure states. - Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data. - Add structured logs around every external call and return actionable errors without leaking sensitive details. - Write unit tests for the core logic and one automated test of the main user journey. - Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations. ## Acceptance criteria - [ ] A clean install starts the app using only the README and .env.example. - [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable. - [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state. - [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control. - [ ] Tests, type checking, linting, and a production build all pass with no ignored failures. - [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified. ## Non-goals Do not build these, and do not claim to have replaced them: - Global chat delivery, mobile apps, staffing tools, integrations, and support. - Omnichannel integrations. - Large-scale deliverability. - AI resolution tuning. - Reliability at the vendor's scale is an operations problem, not a prompt. - Connectors, OAuth flows, and vendor API changes require constant upkeep. ## What you still own after launch - Run migrations, backups, restores, and dependency updates. - Test the critical journey after every model, API, or hosting change. - Monitor failures and fix the edge cases a first prompt will miss. - Maintain every third-party integration as APIs and OAuth rules change. ## Risk **Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost. Editorial confidence in this assessment: medium. No independent one-shot implementation is linked yet. ## Prior art Working open-source software you can read, fork, or borrow from before starting: - [Chatwoot](https://github.com/chatwoot/chatwoot) — Mature open-source customer engagement and shared-inbox platform --- Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/livechat