Sync Telegram, WhatsApp and X DMs into a single workspace. Triage by who owes a reply, run a pipeline, and automate follow-ups — self-hosted, your keys, your data.
Copies a ready-to-paste prompt — drop it into your agent and it ships. View source on GitHub ↗
Not just a unified inbox — a full workspace for turning conversations into customers.
Every chat is sorted by whose turn it is — Needs reply vs Cold — so you never drop a lead. Snooze, mark done, and a “going cold” badge for anyone you've left waiting.
Drag contacts through Lead → Contacted → Won. A real deal pipeline, or group by tag.
Visual flows: a trigger (keyword, no-reply, new chat, broadcast) chained to actions — send, tag, set status.
⌘K to fuzzy-search every chat, multi-select, and bulk-add to folders.
Company, email, phone, notes, tags — and link people to the chats they're connected to.
Saved replies with ⌘-key shortcuts, a `/` picker, emoji, and platform-aware attachments.
Read a chat on your phone and the badge clears here; open it here and it marks read on the platform. Your inbox stays honest across devices.
A true-black theme with a slick circular-reveal toggle. Light mode too.
No bot tokens to beg for. Each channel links the way you'd expect.
Phone-code login — no app to create. You own the API app, users just enter their number.
Scan a QR with your phone, exactly like WhatsApp Web. Stays linked in the background.
A one-click Chrome extension hands off your X session securely with a pairing code.
It's self-hostable and agent-ready. Paste the prompt into Claude Code or Codex — it clones, configures the env, and deploys.
Clone and deploy this unified-inbox CRM for me: `git clone https://github.com/AZK65/2-Many-DMs.git && cd 2-Many-DMs`, then `npm install`. Copy `.env.example` to `.env` and fill in DATABASE_URL, TELEGRAM_API_ID, TELEGRAM_API_HASH and APP_ENCRYPTION_KEY (`openssl rand -hex 32`). Apply the Prisma schema with `npx prisma db push`, then build and deploy using the included Dockerfile — Railway works great and the repo ships a railway.json. Run the sync worker (`npm run sync`) alongside the web server.
Need another channel, a bespoke automation, or hands-on setup & support? DM the developer on Telegram.