ALABTY WhatsApp Automation

ALABTY WhatsApp Automation — Automated Candidate Outreach for Recruiters ALABTY WhatsApp Automation is a Chrome extension built specifically for recruiters using the ALABTY Applicant Tracking System (ATS) at recruitment.alabty.com. It closes the gap between "a candidate needs to be contacted" and "the candidate has been messaged on WhatsApp" — automatically, in the background, without a recruiter ever having to copy a phone number, open a chat, or type a templated message by hand. If you run high-volume recruitment — screening calls, interview invites, document requests, status updates — you already know how much time gets lost switching between your ATS and WhatsApp Web, searching for the right contact, and typing near-identical messages one candidate at a time. This extension removes that manual step entirely. You keep working inside ALABTY as usual; the extension watches for outbound WhatsApp notifications the ATS generates and sends them for you, one after another, while showing live progress in a simple popup. WHO THIS IS FOR This extension is built for individual recruiters and recruitment teams who are already using the ALABTY ATS platform (recruitment.alabty.com or the UAT/staging environment) to manage candidates. It is not a general-purpose WhatsApp bulk-messaging tool — it is tightly coupled to the ALABTY notification system, so messages are only ever sent for candidates the ATS itself has queued for outreach. This keeps outreach controlled, auditable, and tied back to real recruitment activity rather than open-ended bulk sending. WHAT IT DOES, IN PLAIN TERMS 1. You work in ALABTY as normal — moving candidates through stages, triggering interview invites, status updates, or document requests. 2. Each time ALABTY needs a candidate contacted on WhatsApp, it creates a "pending notification" on its backend. 3. The extension detects this activity automatically, fetches the pending notifications, and queues them. 4. One by one, it opens (or reuses) a WhatsApp Web tab, opens the correct chat by phone number, types the exact message ALABTY generated, and sends it. 5. As each message goes out, the extension reports the result (sent, failed, invalid number) back to ALABTY, so your ATS record and your WhatsApp activity never fall out of sync. 6. You can Pause, Resume, or Stop the queue at any time from the popup, and see a live count of sent, failed, and pending messages. KEY BENEFITS FOR RECRUITERS - No more manual copy-paste between ALABTY and WhatsApp Web for every single candidate. - Messages are sent in the recruiter's own logged-in WhatsApp Web session, from their own number — this is not a third-party WhatsApp Business API integration, so there's no separate messaging cost or number to manage. - Automatic detection of invalid or non-WhatsApp numbers, so failed sends are flagged back to the ATS instead of silently disappearing. - Automatic contact-saving: after a successful first message, the extension can save the candidate's name against their number in your WhatsApp contacts, so future conversations show their name instead of just a phone number. - A visible queue with Sent / Failed / Pending counters, so you always know exactly where a batch of outreach stands. - Auto-Open ATS toggle, so the extension can bring your ALABTY tab to the front automatically when it needs your attention (e.g., you're logged out). - Automatic recovery: if you're not logged into WhatsApp Web, or WhatsApp Web is still loading, the extension waits and retries rather than failing outright — nothing is lost, it just resumes once you're ready. HOW IT TECHNICALLY WORKS (UNDER THE HOOD) For teams that want to understand exactly what's running in their browser, here's a breakdown of the extension's architecture, based on its actual source: Background Service Worker (Manifest V3) The extension runs a persistent background service worker that acts as the coordinator. It maintains an in-memory + chrome.storage.local-backed state object tracking whether ALABTY is connected, whether WhatsApp is logged in, the current send queue, batch progress, and running counts of sent/failed messages. This state is published to storage on every change so the popup UI can read it live without needing a direct connection to the service worker. ATS Session Detection A lightweight content script is injected only on your ALABTY domain. It does two things: first, it watches window.history (pushState/replaceState) and popstate events so it knows immediately when you navigate within the ATS single-page app, without needing to poll constantly. Second, the background service worker uses the declared webRequest permission to passively inspect outgoing requests to your ALABTY API — specifically, it reads the Authorization: Bearer header off requests you're already making while logged in, and reuses that same token to call the ALABTY notifications API on your behalf. No separate login step, no password handling, and no credentials are ever stored by the extension outside of the short-lived bearer token already used by your own browser session. Notification Polling and Queueing Once connected, the background worker calls GET /notifications/pending/ on your ALABTY backend using that token, with automatic retry-with-backoff (up to 3 attempts) on 5xx errors or transient network failures. Returned notifications (each containing a phone number, a pre-composed message, and a candidate name) are deduplicated against the current in-memory queue by ID and appended. The worker also tracks whether the backend reports more pending items than fit in one batch, and re-polls until the queue is drained. WhatsApp Automation (content script on web.whatsapp.com) For each queued notification, the background worker opens or reuses a WhatsApp Web tab, navigates it to https://web.whatsapp.com/send?phone=<number> (WhatsApp's own official deep-link format, not a scraped URL), and waits for the tab to finish loading. It then sends a runtim…