Customer support decision
Front
A capable developer can build and run a useful shared inbox and ticketing replacement for Front's core collaboration and routing features within a week and maintain it; Front's differentiated AI, integrations catalogue, and enterprise polish are the main things you'd lose.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.
What a replacement has to do
- Receive customer messages from one channel, store threaded conversations, display a collaborative inbox UI with internal comments and assignment, and send outbound replies.
What it still won’t have
- Front AI (Autopilot/Copilot/Smart QA/Smart CSAT) and their managed AI integrations
- 160+ built-in integrations and enterprise-grade connectors
- Enterprise features (SSO/SCIM, multi-workspace, custom roles) and vendor support
- Scale, uptime guarantees, and polished multi-tenant UI/UX
- Managed WhatsApp native channel and vendor onboarding/services
What remains hard
- Brand trust
Trusted by 9,300+ companies
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 1 seat.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal shared inbox and ticketing product using Next.js (React) for the frontend, Node.js (Express) for the API, Postgres for storage, Redis for background jobs, and Docker for deployment. Implement inbound email ingestion via webhook + SMTP/IMAP adapters (support Gmail/Office365 webhooks and generic SMTP), store threaded conversations, messages, tags, assignments, and internal comments in Postgres, provide a React inbox UI with conversation view, internal comments, agent assignment, and basic search, add outbound sending via SendGrid/Postmark, implement a simple rule engine to auto-tag/assign based on sender/subject/keywords, include user auth (JWT) and per-user seat licensing flag, and provide a small admin UI for channel configuration. Out of scope: multi-workspace enterprise RBAC/SSO/SCIM, native WhatsApp channel, advanced analytics, and managed AI assistants. Include error handling, retries for inbound/outbound delivery, background job tests, unit tests for API routes, and end-to-end tests for the inbox flow.
How we checked
How the score was reached
- Build verdict base78
- An open-source build was found+5
- 5 cited sources+3
- Price verified on pricing page+3
- Evidence score89
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.
How scoring works →Cited sources · 5
Every page the run actually retrieved.
- official productFront — official product
- official pricingFront Pricing and Plans
- official docsFront Product Tour
- open sourcechatwoot/chatwoot
- open sourcezammad/zammad
Integrity checks
What held up, and what did not.
