Sends queued messages from a BaseReach panel directly through the user's active WhatsApp Web session, automating sequential dispatch without external servers. Developed by Michael Chin for Chrome, the extension ties Lark Base data to a browser-based messaging flow, highlights local processing and built-in rate limiting, and fits sales and support teams that need to contact leads from their own phone number while keeping credentials and message content inside the browser.

How it links Lark Base with a local WhatsApp session

BaseReach Bridge connects the BaseReach management panel inside Lark Base to the user's open WhatsApp tab, so queued texts in the panel are handed off to the browser session for sending. The extension uses the user's real account and phone number rather than a third-party API, which means messages originate from the same sender identity visible to contacts.

Message delivery behavior and account safety measures

The extension processes queued items sequentially and includes pauses between sends as a built-in rate limiter. That design sends messages one at a time with delays, a choice aimed at reducing the risk of triggering platform spam protections. The queue automation removes the need to click for each message while preserving paced delivery.

Privacy model and local processing advantages

Processing happens inside the browser and uses the user's active messaging tab, so the extension does not store WhatsApp credentials or messages on external servers. This serverless approach keeps login sessions and message content under the local browser's control, aligning the tool's operation with privacy-focused workflows.

Target workflows and platform requirements

The extension is built for sales teams, customer support, and operations staff who run Lark Base and require outbound contact via WhatsApp from their own number. It requires an active WhatsApp account and access to Lark Base with the BaseReach panel configured, and it runs on Chrome or other Chromium-based browsers.

Useful automation where local control and sender identity matter

The extension suits teams that must send messages from individual phone numbers and keep credentials local, offering automated queue dispatch tied to the user's browser session. Trade-offs include dependence on an active messaging tab and the sequential send model, which suits controlled outreach but is not designed for high-throughput broadcasting. Use it when sender identity and local processing are priorities.