update
Jun 3, 2026
By Teun
PocketPing opens support chats in Telegram, Slack, and Discord
PocketPing is an open-source chat widget that lets support staff reply from Telegram, Slack, or Discord instead of a separate inbox. The project also offers a hosted HubSpot inbox, webhooks, an MCP server, and self-hosted deployment options.
PocketPing is a new open-source customer support chat widget that routes visitor conversations into messaging apps teams already use. According to the project’s Show HN post, one teammate can reply from Telegram, another from Slack, and another from Discord, with messages syncing back to the visitor in real time.
The pitch is straightforward: visitors use the widget on the website, while operators do not need to keep a separate support dashboard open. The company says each conversation can be represented as a Telegram forum topic, a Discord thread, or a Slack thread, depending on the deployment mode. Replies from any connected bridge update across the other apps and in the website widget.
⚡ New to this?
This matters because customer support tools usually force teams into yet another inbox. PocketPing tries to move those conversations into chat apps people already use, like Telegram, Slack, and Discord, while still keeping the website widget as the front end.
A webhook is a way for one app to send event data to another app automatically. MCP, or Model Context Protocol, is a standard that lets AI tools talk to external services, which is why the product can connect to assistants like Claude or Cursor.
🦞 OpenClaw angle
If you build self-hosted AI workflows, pay attention to the event flow here: PocketPing exposes webhooks for every chat event and an MCP server for AI clients. That means you can route support messages into your own automation stack, then have an agent draft replies or triage tickets from Claude or Cursor.
If you already run Slack, Discord, or Telegram as an ops layer, test whether a bridge-based support inbox fits better than a separate SaaS dashboard. For self-hosted automation, start with the bridge-server or SDK so you can keep chat data inside your own infrastructure and plug it into n8n, Make, or custom backend jobs.
PocketPing is open source and MIT-licensed, according to the post. It also offers a hosted SaaS version at pocketping.io, plus a self-hosted bridge-server that can be run in Docker, or an SDK that can be embedded in a team’s own backend. The project says all three modes use the same widget API, so teams can start with a lighter setup and move to a more customized one later.
The lite mode runs on Cloudflare Workers and KV, with no database or server to manage, according to the project description. In that setup, a free Worker relays chat messages between the widget and a Telegram group, with one forum topic per visitor. The full bridge-server expands that model to Telegram, Discord, and Slack at once, and adds attachments, edit and delete support, AI fallback, and cross-bridge sync.
PocketPing also includes webhooks for every event, which means new chats and messages can be sent to tools such as Zapier, Make, n8n, or a custom backend. The project says users can run !commands from the bridge, including on-demand screen capture out of the box, and add their own commands through a small registry.
For AI-assisted workflows, PocketPing exposes an MCP server. MCP stands for Model Context Protocol, a standard used by AI tools to connect to external systems, and the project says this lets teams triage and answer chats from Claude or Cursor.
The project compares itself with tools such as Intercom, Crisp, Chatwoot, and Tawk.to. According to the comparison table in the post, PocketPing supports reply-from-bridge workflows in Telegram, Discord, and Slack natively, while also offering cross-bridge sync and bidirectional events.
PocketPing also supports product events flowing both ways. The widget can emit events like viewed_pricing, cart_abandoned, or trial_day_13, while the server can send UI events back to the widget, such as showing a demo offer or opening chat proactively.
The project says the hosted version is free on the Cloudflare Workers tier, and the self-hosted bridge-server and SDK options are available for teams that want to run the system themselves. According to the post, the same widget can point to the hosted SaaS, a self-hosted bridge, or a custom backend without changing the client-side integration.
