Customer support decision
Eloqra
A competent developer can replicate Eloqra's core: a small embeddable widget plus a relay that uses the Telegram Bot API; the product has no durable moats in the supplied pages, so building and self-hosting a replacement is realistic and cost-effective.
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
- Visitor types in on-site widget → frontend posts message to relay service → relay forwards message to Telegram Bot API with visitor context → operator replies in Telegram → relay receives reply via webhook and pushes it back to the visitor's widget.
What it still won’t have
- Operator Mini App inside Telegram (pre-built console described by Eloqra)
- Hosted uptime, SLA, and built-in changelog/automatic updates
- Polished brand UX, marketplace comparisons, and maintained feature roadmap
- Integrated billing per-project UI (you'd need to add admin billing yourself)
What remains hard
- Product polish and ongoing maintenance
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 self-hosted Eloqra replacement using Node.js (Express), a small PostgreSQL or Redis instance, and a static CDN-served JS widget. In scope: (1) a ~5kb embeddable widget that injects a chat bubble and sends messages to a backend API; (2) an Express relay service that creates and persists session mappings, forwards visitor messages to the Telegram Bot API, and exposes a webhook to receive replies; (3) message routing so Telegram replies are delivered to the correct visitor in real time (long-poll or WebSocket); (4) optional pre-chat name/email capture; (5) a tiny admin page to set bot token, greeting, and color; (6) error handling, input validation, rate-limiting, and unit/integration tests for API and webhook flows. Out of scope: multi-tenant billing UI, operator Mini App inside Telegram, advanced analytics, and SLA-grade deployment. Provide Dockerfiles, deploy guide (DigitalOcean/Heroku), health checks, and automated tests.
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
- 3/3 assessment runs agreed+4
- Evidence score93
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 productEloqra | Free live chat widget that goes to your Telegram
- official pricingPricing | Eloqra
- official docsFeatures | Eloqra
- open sourcechatwoot/chatwoot
- open sourcepapercups-io/papercups
Integrity checks
What held up, and what did not.
