Customer support · checked 2026-10-19

Can I vibecode Eloqra?

YES· one-shottable

A chat relay is small: a script tag that draws a bubble, a server that stores each message and a Telegram bot that forwards it and maps your reply back to the right visitor. An agent builds that in one sitting on SQLite and grammY, and Intergram shows the pattern is old and works. What you skip is the polish around it: the Mini App inbox, visitor context, reminders and one inbox across sites. The one hard requirement is a server the open internet can reach, because the widget has to talk to something.

$4.99/moprice

$60you'd save a year

one sittingbuild time

—people replaced it

Before you start

What you need on hand.

DifficultyIntermediate · Some system setup or keys.

TimeOne to two hours for the first version

Claude Code, Codex or CursorAny of them can run the prompt.
Node.js 22better-sqlite3 compiles a native module, so build tools must be installed.
A Telegram bot tokenMessage @BotFather, create a bot and copy the token; it is free.
A public HTTPS addressA Cloudflare Tunnel or a small VPS; visitors' browsers must be able to reach the widget and the socket.

Before you buildEloqra's free plan already covers one site with the full chat experience. Paying only starts with a second site, so a replacement saves $4.99 a month per extra site and costs you a server.

1. Install one agent: Claude Code, Codex, Cursor.
2. Make an empty folder and open it in the agent.
3. Paste the prompt below, press enter, and answer its questions as it builds.

The prompt

Build me a self-hosted chat bubble that forwards visitor messages to my Telegram, to replace
Eloqra. Requirements:

- Node.js 22 + TypeScript: a Fastify server with @fastify/websocket and grammY. `npm start`
  serves http://localhost:4900 with /widget.js, /ws and /admin.
- Widget: one vanilla-JS file under 8 KB, added with
  `<script src="https://HOST/widget.js" data-site="SITE_ID" async></script>`. A floating bubble
  opens a panel; a random visitor id in localStorage reopens the same conversation on return;
  the socket reconnects with backoff.
- Storage: better-sqlite3 in ./data/chat.db: sites (id, name, allowed origins), visitors,
  conversations (open or resolved) and messages. Save every message before forwarding it.
- Telegram: BOT_TOKEN and OWNER_CHAT_ID in .env, long polling so no webhook certificate is
  needed. A new conversation arrives as one message with the site, page URL, browser and device
  (parsed from the User-Agent); later messages are prefixed with the visitor's name.
- Replying: use Telegram's Reply on a forwarded message and the answer appears in that visitor's
  panel at once. `/resolve` as a reply closes the conversation; the visitor's next message opens
  a new one. A message that is not a reply gets a one-line hint back.
- Safety: accept sockets only from a site's allowed origins, rate-limit 20 messages a minute per
  visitor, cap messages at 2,000 characters and escape everything rendered in the panel.
- Admin: /admin behind ADMIN_PASSWORD (signed cookie) to create sites, copy the snippet and read
  transcripts.
- Single owner. No accounts, no telemetry, local-first: the only outbound calls go to Telegram.
- Out of scope: email fallback, file uploads, typing indicators, several operators, translations.
- README: the BotFather steps, exposing the server through a Cloudflare Tunnel or a small VPS
  with Caddy, and a warning that the bubble only works while the server is reachable.

Opens your agent with the prompt filled in, you press enter. Or copy it and paste it into an empty folder.

Share on X

Max MiskowSponsoredAI agents, automations and MVPs, built for your company.Visit site ›

Then keep going

Next prompts, same folder.

The first prompt builds the core. Run these one at a time in the same folder to grow it into your own Eloqra.

Add unanswered-chat reminders to the chat relay in this folder. Requirements:

- If a visitor message gets no reply within REMINDER_MINUTES (default 10, set in .env), send one
  reminder to Telegram quoting the first 80 characters; a reply or `/resolve` cancels it.
- Respect online hours from OPEN_FROM, OPEN_TO and TIMEZONE in .env. Outside them, show the
  visitor "We're offline, leave your email" and save the email with the conversation.
- Persist pending reminders in SQLite so a restart does not lose them.
- Update the README.

Switch the chat relay in this folder to a Telegram forum group. Requirements:

- Add TELEGRAM_GROUP_ID to .env for a supergroup with Topics turned on; create one topic per
  conversation, named after the visitor and the site.
- Anything typed in a topic goes to that visitor; closing the topic marks the conversation
  resolved, and a new visitor message reopens a fresh topic.
- Keep the private-chat mode working when TELEGRAM_GROUP_ID is empty.
- Update the README with the steps to make the bot an admin with the Manage Topics right.

Add an optional pre-chat form to the chat relay in this folder. Requirements:

- Per site, a switch for asking name and email before the first message, each with a required flag.
- Validate the email, add a hidden honeypot field and reject submissions that fill it.
- Store the answers on the visitor, show them in the first Telegram message and in /admin.
- Skip the form for returning visitors who already answered.
- Update the README.

What you lose

The operator Mini App with an inbox, resolve and reopen, so you can answer from one screen inside Telegram
Visitor context cards with page, device and country on every conversation
Unanswered-chat reminders, online hours and a settings page for the widget's look and wording
One combined inbox across several sites
Someone else keeping the endpoint up: if your server is down, the bubble goes silent

Why people still pay

Most don't: the first project is free, so only a second or third site costs $4.99 a month. The reason to pay is that it runs without a server of your own, with no tunnel, bot process or database to look after.

Moatexecution polish

Do the math

Eloqra or your own copy?

Over

Your usage

Count my time3h ×$/h

Eloqra, 1 yr$60

Your own copy, 1 yr$40running + build session

You keep$20pays for itself in 3 months

Estimate · A free tunnel to a machine that stays on costs nothing; a small VPS is the steadier choice at around $5. Telegram's bot API is free. The build is token usage on your agent plan.

Leaving Eloqra

Take your data, then cancel.

1 · Take your data out of Eloqra

1The docs describe no bulk export of conversations: the dashboard keeps them on its Resolved tab, so copy anything you need from there.
2Every message also lives in your Telegram chat with the bot: Telegram Desktop can export a chat's history from the chat menu.
3Widget settings (greeting, accent colour, hours, copy) have no export; note them down or take screenshots.

2 · Cancel Eloqra

1Free plan: nothing to cancel. To stop, remove the script tag from your site and delete the project in Settings.
2Pro: open Settings, then Billing, and choose Manage Billing. The Stripe customer portal lets you update the card, download invoices, switch the billing period, lower the number of slots or cancel.
3When Pro ends, your oldest projects up to the free allowance stay active and the rest are marked inactive.

Deleting a project is permanent and removes its widget settings and Telegram link; conversations leave your inbox too.
Disconnecting Telegram takes effect at once with no confirmation, and the widget keeps working with replies only in the dashboard.
The Terms page says the service is free during early access, while the pricing page lists Pro; check what you are billed before relying on either.
The pricing and terms pages state no refund policy.

Checked 2026-10-19 against Eloqra's docs: 1, 2, 3, 4

The escape hatch

Don't feel like building it? These are already free.

ChatwootOpen sourceSupport desk with a website live-chat widget and a Telegram inbox; MIT community edition with some paid features.★ 38k · active Oct 2026 · docker to self-host
WebVisit ↗ChaskiqOpen sourceRails live chat and support platform with an embeddable messenger for your site.★ 3.6k · active Jun 2026 · self-host, real ops
WebVisit ↗TiledeskOpen sourceMIT-licensed live chat and chatbot platform with a website widget; Docker Compose or Helm to self-host.★ 323 · active Oct 2026 · docker to self-host
WebVisit ↗

All 4 free alternatives to Eloqra ›

The numbers

Eloqra pricing

Plan	Monthly	Annual, per month	What you get
Free	$0	$0	1 project, chat widget on every page, messages forwarded to Telegram, operator Mini App, visitor context (page, device, country), optional pre-chat form, widget in 10 languages.
Pro	$4.99	$4.17	One extra project slot per purchase (1 to 20 at a time); each project has its own widget, settings and Telegram link. No per-seat or per-message charge.

Free tier: One project; every further site needs a paid slot.
Billing: Monthly or annual per project slot, paid through Stripe; cancel or lower the quantity in the Stripe portal. If Pro ends, the oldest projects up to the free allowance stay active and the rest turn inactive. The pricing page lists no trial or refund terms.
Hidden costs: None found: the price is per site, not per person or message. The Terms page still describes the service as free during early access, so the plan table may change.
Source: eloqra.app

Also on the list

Intercom$39/mo · Customer supportKINDA

Help Scout$30/mo · Customer supportKINDA

Chatbase$40/mo · Customer supportYES

Questions

Eloqra, briefly

Not answered here? Tell us and we'll add it.

Ask a question ›

Free covers one project forever: the chat widget on every page, Telegram forwarding, the operator Mini App and a pre-chat form.

Yes. An AI coding agent such as Claude Code, Codex or Cursor can build a usable personal version in one session with the prompt on this page, running on your own machine.

About $4.99 a month on the Pro (per extra project) plan, $59.88 a year (checked 2026-10-19).

The operator Mini App with an inbox, resolve and reopen, so you can answer from one screen inside Telegram; Visitor context cards with page, device and country on every conversation; Unanswered-chat reminders, online hours and a settings page for the widget's look and wording; One combined inbox across several sites; Someone else keeping the endpoint up: if your server is down, the bubble goes silent. If any of those matter to you, keep paying.