[verdict][generated prompt][source: intercom.com]
Can I vibecode Intercom?
// the value is the network, the data or the infrastructure
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Intercom, run a small website inbox and knowledge base without recreating Intercom's AI or channel network. The hard boundary is messaging infrastructure, ai resolution, product tours, integrations, and enterprise operations, plus channel integrations and support operations.
confidence: high
what it is: Run a small website inbox and knowledge base without recreating Intercom's AI or channel network
Buildability index · an editorial game
- Price variable pricing · per seat weight: zero
- Time closest consolation build: one sitting weight: minus 1
- Category customer support no weight
- Moat integrations · infrastructure scale weight: minus 3
- Confidence high weight: plus 1
- What you lose 5 items weight: minus 2
- Site intercom.com (si apre in una nuova scheda) no weight
It is not close. The prompt below rebuilds a piece, not the product.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
Receive website messages into a small shared inbox, reply from one place, maintain a knowledge base, and retain searchable history without recreating Intercom's AI or channel network.
what you need
- Docker
- PostgreSQL
- public HTTPS deployment
- email or chat channel credentials
Editorial comparison targets the Essential plan and a small-team shared inbox DIY substitute. Recheck price before merge.
The prompt
The verdict is NOT REALLY, and the prompt stays anyway: it does not replace the app, it rebuilds the part that really is code. The rest is the moat.
Build a closest honest personal substitute for Intercom 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 messages into a small shared inbox, reply from one place, maintain a knowledge base, and retain searchable history without recreating Intercom's AI or channel network.
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.
Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure.
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.Prompt generated from the data on this page, not reviewed by hand yet. In English on purpose — it is the language coding agents work best in.
What you lose
- messaging infrastructure, AI resolution, product tours, integrations, and enterprise operations
- omnichannel integrations
- large-scale deliverability
- AI resolution tuning
- enterprise routing and compliance
Why people still pay
People still pay for Intercom because support software survives because missing or misrouting one customer message is expensive and every channel behaves differently. The recurring cost buys message delivery, webhooks, threading, identity, permissions, attachments, notifications, spam, search, uptime, and retention, not just the visible interface.
moat: Integrations Infrastructure scale what a moat is
channel integrations and support operations
Free alternatives
Not in the mood to build it? These already exist, they are free or open source, and we checked them one by one.
Rejected (3) — and why
- Chaskiq (si apre in una nuova scheda) — Source is available, but open abandonment and broken-production reports make it a bad non-builder recommendation.
- HubSpot Free Help Desk (si apre in una nuova scheda) — The inbox and widget are free; the knowledge base required by this row is not.
- Papercups (si apre in una nuova scheda) — The famous open-source Intercom alternative has not seen a main-repo commit since February 2024.
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- Chatwoot (opens in a new tab) — Mature open-source customer engagement and shared-inbox platform.
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.
