Conversation context,
where your team needs it.

The business problem

Customer discussions held in individual messaging accounts can be difficult for colleagues to review alongside CRM records. The solution aims to reduce manual copying and make prior communication available before the next follow-up. These are intended benefits; no quantified performance or business outcome is claimed.

Two complementary components

The backend pairs agent WhatsApp Web sessions through QR codes, observes incoming and outgoing one-to-one messages, stores them locally, and maintains a contact transcript. It searches Bigin Contacts by phone and creates or updates a note titled “WhatsApp Conversation.” Unmatched contacts remain local; no CRM contact is automatically created.

The Chrome companion adds a chat button beside a Bigin phone field. It opens WhatsApp Web and stores the selected phone, lead name, and record path in browser-local storage. The reviewed extension does not transmit that mapping to the backend. The browser companion and the server capture service are therefore separate flows in the inspected source.

Functional scope

Source-observed features include multiple local agents, QR pairing, session controls, incoming/outgoing capture, local search, transcript metadata, and Bigin note synchronization. Groups and status broadcasts are excluded. Local first-assignment ownership is separate from Bigin ownership.

Media downloads are kept locally and referenced by filename in transcripts; media upload to CRM is not established. Capturing an outgoing message does not establish an automated message-sending feature.

Technical design

The backend uses Node.js, Express, whatsapp-web.js, SQLite, text transcripts, and Bigin contact/note APIs. WhatsApp sessions use LocalAuth. The extension uses Manifest V3 with a service worker and a content script. The public website and demo are static HTML, CSS, and JavaScript; they require no backend and make no CRM calls.

GitHub Pages hosts the presentation website only. Running persistent WhatsApp sessions, SQLite storage, and CRM synchronization requires a separate server environment.

Evidence and current maturity

The backend baseline is repository commit eece8ad. The likely newer extension candidate was modified on 18 June; both supplied copies declare version 1.0. Its local lead mapping is more developed than the May copy, but timestamps alone cannot establish an authoritative production release.

This review inspected source. It did not pair live accounts, execute Bigin writes, verify production protections, or run acceptance/load tests. The extension requires permission review and live validation before distribution. Employee creation, update, and removal from Bigin remains an unresolved requirement, with API and authorization verification pending.

Evaluation and roadmap

Evaluation should prove contact matching, note creation/update, duplicate-message handling, multi-agent attribution, token renewal, reconnect behavior, failure recovery, and backup restore. Employee reconciliation must use a complete authoritative inventory; missing contact owners cannot establish employee deletion.

The next product milestones are a validated backend release, reviewed extension packaging, employee synchronization, and a documented deployment. The interactive example on this site uses fictional data and illustrates the intended workflow rather than a live integration.

Source references

Backend source baseline. Extension findings derive from two owner-supplied folders inspected on 20 October 2026. Detailed internal specifications and release blockers are maintained separately in Notion.