Universal WA Blaster

Local Browser Communication Automation Utility

Turn structured contact lists into personalized message queues using local source-file processing, configurable templates, pacing controls, and browser-based queue management.

🔴 IMPORTANT PLATFORM & RESPONSIBLE-USE NOTICE

This software is a local client-side browser automation utility. It is not affiliated with, endorsed by, or connected to the official Meta WhatsApp Business API. Browser automation may be restricted by platform terms and may result in warnings, limitations, suspension, or loss of access.

Users are responsible for ensuring that every communication has an appropriate lawful or consent basis, follows applicable messaging and privacy requirements, respects recipient opt-outs, and complies with the current terms of the messaging platform.

1. Launch Automation Blast Engine

The Blast function manages a browser-based queue from a message template and structured CSV contact list. The extension provides two execution modes together with personalization, contact-file, pacing, and abort controls.

🎯

Coordinate-Based X/Y Mode

This mode uses user-configured screen coordinates to perform automated mouse and keyboard interactions on the active browser window. It is intended as an alternative execution method when interface structure changes.

👻

Automatic Ghost-Typist

The standard mode loads each recipient target in the designated WhatsApp Web tab, identifies the required interface control, inserts the prepared message, and advances through the local queue.

🏷️

Dynamic Tag Engine

Reads each spreadsheet row, matches custom placeholders such as [Column A] or [Column C], and replaces them with row-specific text such as names, dates, identifiers, or study links.

📇

Bulk VCF Generator

Converts supported CSV rows into a mobile-ready .vcf contacts file for convenient import into a phone or supported contact-management application.

⏱️

Configurable Pacing Controller

Allows the operator to define the delay between queued actions so message processing can be paced according to the intended communication workflow and platform limitations.

🛑

Emergency Safety Valve

Includes an Abort Blast control that allows the operator to halt the active queue if the wrong file, recipient list, or message template was selected.

🖥️ Local Source-File Processing

Uploaded CSV source data and message templates can be processed locally in the browser rather than being uploaded to an Alivioscript processing server. Messages sent through WhatsApp still use WhatsApp's own platform infrastructure and remain subject to its policies and data handling.

2. License Model & Evaluation Limits

A Lifetime Pro License is an upfront license for the supported operational lifespan of the current product. Because the extension depends on the structure and behaviour of WhatsApp Web, interface changes by the platform can affect compatibility. Alivioscript may issue maintenance updates while the product remains supported, and any planned end-of-support period should be communicated through the product interface or applicable terms.

Free Evaluation Tier: Non-licensed users are limited by the extension's local evaluation counter. Upgrading to the Pro License removes the extension's local trial-volume restriction; it does not override recipient-consent requirements, platform rules, or external messaging limits.

3. Multi-Language CSV Data Encoding Rules

The processing engine reads structured text uploads. Follow the supported file layout and encoding rules so recipient numbers and multilingual fields are interpreted correctly.

📊 Rule A: Phone Number Placement

For the messaging engine and VCF Generator to extract the recipient number correctly, place the phone number in the final column of the supported CSV layout. Earlier columns can contain personalization fields such as names, references, or group labels.

🔤 Option B: English & Malay Lists

For simple English/Malay and numeric data, the standard CSV (Comma delimited) (*.csv) format will generally work with the extension's parser.

🈲 Option C: Chinese & Other Unicode Text

When contact data contain Chinese characters or other Unicode text, some spreadsheet export settings may produce encoding problems if the file is saved using a legacy character set.

Recommended: save the file as CSV UTF-8 (Comma delimited) (*.csv) to preserve multilingual characters.

4. Screen Focus & Multi-Device Operation

Because the tool performs browser automation, the designated desktop browser tab must remain available to the extension while an active queue is running.

Desktop Tab Control

During an active queue, automated actions may take control of the designated WhatsApp Web tab and keyboard focus. Avoid manually using that same tab until the queue has completed or has been stopped.

Separate Mobile Session

Where supported by the messaging platform's multi-device configuration, a linked mobile device may remain usable independently. Actual behaviour depends on the current platform implementation and account state.

⚡ Practical Workflow Tips

  • Dedicated Browser Profile: Consider running the extension in a separate browser profile so the automated queue does not interfere with unrelated browser work.
  • Review Before Launch: Confirm the recipient list, message template, personalization fields, and opt-out wording before starting a queue.

5. Responsible Messaging & Operational Best Practices

Use the utility for legitimate communications with recipients you are permitted to contact. Platform enforcement can change over time, so no pacing setting, contact-file format, or browser configuration can guarantee continued account access.

✅ Consent & Recipient Expectations

  • Use an appropriate contact basis: Send messages only where you have consent, an existing relationship, or another lawful and policy-compliant basis to contact the recipient.
  • Use recognizable sender information: Make it clear who is sending the message and why the recipient is receiving it.
  • Respect opt-outs: Provide a simple way to stop future messages and promptly remove recipients who opt out.

📋 Queue Quality & Review

  • Use manageable batches: Smaller queues are easier to review, monitor, and stop if a configuration error is discovered.
  • Verify personalization fields: Check sample rows before launch to ensure names, dates, references, and links map to the intended recipients.
  • Use appropriate pacing: Configure intervals according to your workflow and the current messaging-platform limits; pacing does not guarantee exemption from platform enforcement.

💡 Before Every Queue

  • Confirm that the recipient list is current and authorized for the intended communication.
  • Review the message template and links for accuracy.
  • Include a clear sender identity and, where appropriate, an opt-out instruction.
  • Keep the Abort Blast control available in case the queue needs to be stopped.