Connect a number by QR, send messages from Google Sheets or HTTP, queue every request, and give operators a clean console for logs, payments, and reconnects.
A focused product surface your company can demo, onboard, and support without heavy SaaS infrastructure.
Each customer links their WhatsApp number from the browser console.
Apps Script reads contacts from the sheet and calls your API endpoint.
Operators can refresh status, view sends, and monitor queued jobs.
Every send request enters the queue first, then MIS_api releases messages one by one to reduce sudden bursts from Sheets.
Use the built-in pricing and UPI contact section for the first paying customers before adding payment gateway automation.
Simple enough for a first user, structured enough for a sales demo.
Use customer API keys for private access.
Give customers a tiny Apps Script file and a three-column sheet.
WhatsApp number with country code, for example 919876543210.
The message text that should be queued for sending.
Status written by the script after calling MIS_api.
Manual payment option for first customers.
One WhatsApp number, API access, Google Sheet sender, queue, logs, reconnect console, and support.
UPI ID
After payment, send screenshot to 91XXXXXXXXXX or sales@mis-api.example.
Set expectations clearly before your first sale.
No. MIS_api uses QR based WhatsApp Web automation for early customers and pilot workflows.
Yes. The Node server, tunnel, and WhatsApp session must remain active for sending to work.
No. Customers should send only to opted-in contacts, start slowly, and honor opt-out requests.
Create their API key, connect their WhatsApp number, and let them send from a Sheet.