Frequently Asked Questions
Find answers to the most commonly asked questions about the WhatsApp QR Login Module for WhatsMarkSaaS.
📦 Installation & Setup
Q: What are the system requirements for the WhatsApp QR Login Module?
A: The module requires:
- WhatsMarkSaaS (latest version)
- PHP 8.1 or higher
- MySQL 8.* or higher
- Node.js 18+ for the bundled gateway service
- A valid SSL certificate and a public URL (localhost is not supported)
- A WhatsApp account on a phone (personal or business)
Q: How do I install the module?
A: Follow our detailed Installation Guide for step-by-step instructions.
Q: Can I install this module on multiple domains?
A: The license is typically for one domain. For multiple domains, you'll need to purchase additional licenses. Check the license terms on CodeCanyon for specific details.
🔌 Connection & WhatsApp
Q: Do I need WhatsApp Business API approval?
A: No. The module uses the same QR-based flow as WhatsApp Web, so it works with any WhatsApp account — personal or business — without Meta approval, paid templates, or per-message fees.
Q: Will my phone need to stay online?
A: Only briefly, for the initial scan. After that, the gateway keeps the connection alive on its own; your phone can be off, dead, or out of coverage and messages still flow. WhatsApp will eventually ask you to bring the phone back online (typically after a few weeks of inactivity).
Q: Can multiple people share one connection?
A: Yes. As long as your platform users have access to the same tenant, they all see the same chats and can reply. WhatsApp itself only sees one device, but on your side it's a true shared inbox.
Q: How many WhatsApp numbers can one workspace connect?
A: One. Each workspace links a single WhatsApp number. If you need a different number, disconnect the current one first and scan a new QR.
Q: Are messages encrypted in transit?
A: Yes — WhatsApp's end-to-end encryption is preserved. Your gateway acts as an authorised linked device (just like the WhatsApp Web client), so messages are decrypted locally on your server, stored in your database, and re-encrypted when sent.
Q: Can I migrate chats between tenants?
A: Not via the UI. The data lives in tenant-scoped tables, so a database export/import would be the only path — and you would also need to re-scan the QR on the destination tenant.
Q: What happens if I scan a QR with a number that's already linked elsewhere?
A: WhatsApp will unlink the existing device and link this one instead. The previous gateway session will report "disconnected" on its next event. Plan migrations during a maintenance window.
💬 Messaging & Inbox
Q: What message types can I send from the inbox?
A: Text, images, videos, audio files, voice notes (recorded in the browser), documents, emogis, locations, and contact cards. You can also reply, forward, react with emoji, and delete-for-everyone within WhatsApp's deletion window.
Q: Are there per-message fees?
A: No. Because the module uses the QR-based WhatsApp Web flow rather than the Cloud API, there are no per-message or per-conversation fees from Meta. Your only cost is the platform itself.
Q: Can I use message templates?
A: Yes — but they're canned replies (saved templates you can drop into the composer), not the formally-approved Cloud API templates. There's no template review process.
Q: Do CRM merge fields work?
A: Yes. Insert placeholders like or from the @ picker in the composer. They're resolved per recipient when the message is sent.
🛡️ Security & Compliance
Q: Where are my chats stored?
A: In your own database, on your own server. Nothing is sent to Corbital or any third-party service.
Q: Is this compliant with WhatsApp's Terms of Service?
A: The technical mechanism (linked-device QR flow) is the same as WhatsApp Web, but how you use it is on you. Sending unsolicited bulk messages, scraping contacts, or other behaviour that violates WhatsApp's Terms can still get your number banned. We do not provide support for ban recovery.
Q: Can I export my chat history?
A: Chats live in standard database tables, so a database export is straightforward. The UI also exposes search and per-chat browsing for audit purposes.
Note: WhatsApp is a trademark of Meta Platforms, Inc. This product is not affiliated with or endorsed by Meta. Use of automated tools must comply with WhatsApp's Terms of Service.