Messenger CRM: hundreds of accounts — one window
Desktop platform for WhatsApp, WhatsApp Business, Telegram and Max on physical Android devices: screen mirroring, unified chat and contact database, bulk messaging and auto-replies from real phones. Each account is an independent sender with its own pauses and limits — not one linked "farm."
USB phones required · License by device count · Data on your PC
Start in 3 steps
From connecting phones to your first bulk send with queue and funnel statuses.
Connect Android via USB
Enable debugging, plug in phones — the app registers devices and accounts in the database.
Configure senders and contacts
Import XLSX, set funnel statuses, bind SIM to devices and pause limits.
Launch warming and bulk send
Queue with priorities, spintax and auto-replies — each account sends from its own phone.
Scrcpy mirroring
Video stream of the selected USB device screen: tap, swipe, keyboard, drag-and-drop files to the phone.
Independent senders
Bulk send not from one "hub" — from different SIMs and device_id, with their own pauses and limits.
One chat — one account
In a channel the recipient is not switched to another account without explicit logic — less number linking.
Priority queue
Personal and urgent messages overtake warming and mass bulk send.
webwarmer2 warming
warm in/out exchange between internal and external numbers before a "live" campaign.
RegExp auto-reply
Rules by regex, contact status and shell commands — from phone notifications into the reply queue.
CRM, messenger and bulk send from live phones
Hundreds of accounts — one window
- → Chats. Dialog list with preview, unread count and virtual scroll for thousands of chats
- → Devices. Switch USB phones in a dropdown without restart
- → Send. Text, media, voice, quotes and emoji — like in the messenger
Contacts, statuses and analytics
- → Contacts. external_numbers table: XLSX import/export, filters and presets
- → Funnel. Status editor and assignment to contacts
- → Queue. All outbound in progress with jump to the right chat
Without "linking" accounts into one pile
- → Senders. Bound to internal_numbers: phone + app_type + SIM
- → Recipients. Filter by status, no duplicates or foreign chats in the channel
- → Anti-spam. Spintax, {{Name}}, drip-feed: one pending per recipient, random pauses
Rules and quick replies
- → RegExp. Message_Free_RegExp.json: regex, status filter, keygen, template
- → Trigger. Incoming from dumpsys notification → rule check → queue
- → Quick replies. Same templates in chat; on send — contact status change
Numbers before the campaign
- → webwarmer2. Sync external numbers with androidsender.com/webwarmer2
- → Balance. warm_rec / warm_out tab — incoming vs outgoing ratio
- → Limits. Warming and "real" counters in the devices table
Priorities and control
- → Priority. queue_priority: personal (2) beats bulk send and warming (5–8)
- → Statuses. pending → sending → sent / failed in messages
- → Busy. While the phone is sending — no second stream on device_id
WhatsApp, Telegram, Max
- → WhatsApp. com.whatsapp and com.whatsapp.w4b in one whatsapp channel
- → Telegram. org.telegram.messenger
- → Max. ru.oneme.app (ONEME)
Real phones, not cloud API
- → ADB. Pipeline_09 sends pending one message per device
- → USB. DevicesDetect.exe monitors connection and license
- → Local. db_devices.db and db_messenger.db on your PC
Messenger CRM vs cloud panels and a single API key
FAQ
Is this a cloud WhatsApp API?
No. You need physical Android phones with USB and ADB. Sending goes through the app UI on the phone, not through a single cloud channel.
Which messengers are supported?
WhatsApp, WhatsApp Business, Telegram and Max (ONEME) — in one interface; the whatsapp channel combines both WhatsApp packages.
How many accounts can I run?
The platform is built for hundreds of accounts: virtual chat scroll, queue, devices table and limits. The exact ceiling depends on the USB device license.
How does anti-spam logic work?
Different device_id, one pending per recipient, random pauses, spintax, warming, "own chat in channel" rule and device is_in_use — the architecture reduces templating, but nobody guarantees zero bans.
Where do incoming messages come from?
Mostly from parsing dumpsys notification on the phone plus outbound from the queue. Full chat history parsing from the app is limited — E2E is not broken.
Is internet required for the license?
Yes. DevicesDetect.exe checks the device limit online via license_checker.php.
How do I get a demo or license?
Message on WhatsApp via the button on this page — we'll arrange a demo, device count and terms.
Messenger CRM on live Android, not on one API key
Hundreds of accounts, bulk send from SIM, warming and auto-replies — in one window.
Request demo on WhatsApp