PocketPing is an open-source chat widget. Each teammate replies from the messaging app they already use — one on Telegram, one on Slack, one on Discord — and replies sync to the visitor across all of them. No operator dashboard required.
Bob replies from Telegram. Alice prefers Slack. Marketing watches the inbox in HubSpot. One conversation, native sync — and the visitor only ever sees the widget.
!commands from your bridge — on-demand screen capture out of the box, plus a tiny registry to add your own.MCP server → triage and answer chats straight from Claude or Cursor.Start serverless. Move to the Go bridge later. Or skip both and embed the SDK in your own backend. The widget never knows the difference.
Cloudflare Worker + KV
Zero database. Zero servers. A free Worker relays chat between your widget and a Telegram group where each visitor gets its own forum topic.
docker run · one binary
A single Go binary that bridges your widget to Telegram, Discord and Slack at once. Full features — attachments, edit/delete, AI fallback, cross-bridge sync.
Node · Python · Go · PHP · Ruby
A library you mount into your existing backend. You own the routes, the database and the deploy. We provide the handlers and the bridges.
Drop the widget on your site, point it at your endpoint, and the chat opens in the corner. Same call signature whether the endpoint is the lite Worker, the bridge-server, your own backend, or the hosted SaaS.
<script src="https://cdn.pocketping.io/widget.js"></script>
<script>
PocketPing.init({
endpoint: 'https://your-worker.workers.dev',
operatorName: 'Acme Support',
});
</script>import express from 'express';
import { PocketPing, TelegramBridge } from '@pocketping/sdk-node';
const pp = new PocketPing({
bridges: [new TelegramBridge(process.env.TG_TOKEN!, process.env.TG_CHAT!)],
});
express()
.use(express.json())
.use('/pocketping', pp.middleware())
.listen(3000);The widget speaks SSE to a Cloudflare Worker. The Worker speaks HTTP to the Telegram Bot API. State (visitor ↔ forum topic) lives in a KV namespace.
channel = the tool ingests the app into its own inbox. native = you reply where you already are. native* (Intercom Slack) = reply from Slack supported, but Intercom remains the inbox.
| Feature | PocketPing MIT · OSS | Intercom SaaS | Crisp SaaS | Chatwoot MIT · OSS | Tawk.to SaaS |
|---|---|---|---|---|---|
| Pricing | Free / OSS | $29+/seat/mo | Free / $45+/mo | Free / $19+/seat | Free |
| Self-hosted | ✓ | — | — | ✓ | — |
| Reply from Telegram | native | channel | channel | channel | add-on |
| Reply from Discord | native | — | channel | — | — |
| Reply from Slack | native | native* | add-on | channel | — |
| Cross-bridge sync | ✓ | — | — | — | — |
| Bidirectional events | ✓ | outbound only | rule-based | requested (4 yr) | — |
| Webhooks (events API) | ✓ HMAC | paid | ✓ | ✓ | ✓ HMAC |
| MCP server (AI agents) | ✓ OSS | ✓ | ✓ | community | — |
| AI fallback | BYO key | Fin AI | Hugo | Captain | AI Assist |
| AI cost per conv. | ~$0.001 | $0.99 | $0.05–0.10 | $0.02 | $0.02–0.03 |
| License | MIT | closed | closed | MIT (CE) | closed |
* Pricing snapshot from public pricing pages as of Nov 2026 — verified against each vendor's docs. AI cost per conv. = Intercom Fin AI ($0.99/outcome), Crisp Hugo ($0.05–0.10/conv), Chatwoot Captain ($20 / 1k credits), Tawk AI Assist ($29 / 1k msgs), PocketPing = direct OpenAI / Anthropic / Gemini pricing (varies by model and prompt size, GPT-4o-mini ≈ $0.0004 / resolution). Bidirectional events: Intercom Outbound fires on rule-based triggers (paid plans); Crisp triggers are declarative (fire on condition); Chatwoot's open request #2995 dates from 2021; Tawk's `onChatMessageSystem` is chat-bound only.