Welcome to PocketPing
PocketPing is a lightweight chat widget that forwards messages to your favorite messaging apps (Telegram, Discord, Slack) and lets you reply directly from there.
The Problem
Traditional live chat tools force you to:
- Keep a dashboard tab open 24/7
- Miss messages when you're away from your computer
- Pay for expensive seats and features you don't need
The Solution
Result: Reply to customers from anywhere, even from your phone while walking your dog.
Key Features
1. Bidirectional Messaging
Not just notifications—reply directly from Telegram, Discord, or Slack. The conversation syncs in real-time.
2. Custom Events
Track user actions and trigger automations:
// Frontend: track when user clicks pricing
PocketPing.trigger('clicked_pricing', { plan: 'pro' });
// Backend: react to the event
onEvent: (event, session) => {
if (event.name === 'clicked_pricing') {
pp.sendMessage(session.id, {
content: "I see you're checking our Pro plan! Want a demo?"
});
}
}
3. AI Fallback
When you're away, AI responds using your custom instructions:
4. Lightweight Widget
The widget is ~60 KB gzipped via the CDN (or ~32 KB gzipped via the npm/ESM build) — lean compared to most hosted chat widgets:
| Widget | Size (gzipped) |
|---|---|
| Crisp | ~88KB |
| Drift | ~61KB |
| Intercom | ~80KB+ |
| PocketPing | ~60 KB (CDN) / ~32 KB (ESM) |
Minimal impact on your page load time.
Who Is This For?
| Use Case | Why PocketPing |
|---|---|
| Solo founders | Reply from your phone, AI handles off-hours |
| Small teams | No per-seat pricing, everyone uses their existing apps |
| Developers | Self-host option, full API access, custom events |
| Privacy-focused | Self-host = your data stays on your servers |
How It Works
Step 1: Add the widget (30 seconds)
<script src="https://cdn.pocketping.io/widget.js"></script>
<script>
PocketPing.init({ projectId: 'YOUR_PROJECT_ID' });
</script>
Step 2: Connect your messaging app
Choose Telegram, Discord, or Slack (or all three). When a visitor sends a message, you get a notification.
Step 3: Reply from anywhere
Reply directly from your phone. The visitor sees your response in real-time.
That's it. No complex setup, no dashboard to monitor.
Architecture Overview
PocketPing offers 4 deployment options to fit your needs:
Option 1: Serverless (Lite — Telegram)
The fastest and cheapest path: a free Cloudflare Worker with no server and no database to manage. Best for a Telegram-only chat that gives every visitor their own topic. The bot token stays server-side in the Worker (never in the browser). Deploy guide →
Option 2: Hosted (SaaS)
The easiest way - we handle everything:
Option 3: Bridge Server (Self-Hosted Standalone)
Run our standalone Go server on your infrastructure:
Option 4: SDK Integration (Self-Hosted Custom)
Embed PocketPing into your existing backend using our SDKs:
| Option | Best For | Setup Time |
|---|---|---|
| Serverless (Lite) | Free Telegram chat, no server/DB | ~1 minute |
| Hosted (SaaS) | Quick start, no infrastructure | 5 minutes |
| Bridge Server | Self-hosting without custom logic | 15 minutes |
| SDK Integration | Full control, custom workflows | 30+ minutes |
| Component | Description |
|---|---|
| Widget | Chat interface embedded on your website (~60 KB gz CDN / ~32 KB gz ESM) |
| pocketping.io | Hosted SaaS service (zero setup) |
| Bridge Server | Standalone Go binary for self-hosting |
| SDK | Libraries for Node.js, Python, Go, PHP, Ruby |
Quick Comparison
| Feature | PocketPing | Traditional Chat |
|---|---|---|
| Reply from phone | ✓ Native app | Clunky mobile web |
| Notifications | ✓ Your existing apps | Yet another app |
| AI fallback | ✓ Built-in | Premium add-on |
| Self-hosting | ✓ Free | Enterprise only |
| Widget size | ~60 KB gz (32 KB ESM) | 60-90KB |
| Per-seat pricing | None | $15-50/seat |
Next Steps
Ready to get started?
Quick Start → Get running in 5 minutes with the hosted service
Backend SDKs → Node.js, Python, Go, PHP, Ruby with built-in bridges
API Reference → Build custom integrations
Use the chat widget on this page (yes, it's PocketPing!) or open an issue on GitHub.