The tabs you already have open, captured.
Tern Bridge is a Chrome extension. It reads the thread in front of your agent and writes it to the lead. It places a drafted reply for the agent to read and send. It never sends anything itself.
From the thread to the timeline
A content script per site watches the thread the agent has open. When it changes, the visible messages are parsed, matched to the lead by phone, handle or email and written to the timeline. Duplicates are dropped by content hash.
Priya Nair
Outcome: book consultation, due in 5 days
WhatsApp, inbound, 9:41
Hi, is Thursday still possible for the consultation? Afternoon works best.
Drafted by Tern, sent by Aisha, 9:52
Yes. I can do 2:00 or 3:30 on Thursday. Which suits you?
Call with Aisha, 6 min 12 s
Zoom Phone, recorded with consent, transcribed
Priya confirmed Thursday 3:30. She will send the passport scan tonight. Aisha will email the consultation checklist before the call.
- Priya: passport scan tonight
- Aisha: send checklist
Tern drafts. A person sends.
When a playbook step or an agent needs a reply, the draft appears in the side panel with the lead overview. If the agent picks it, the text is placed in the site's own composer and the extension stops. The agent reads it and presses the site's own send button.
What the bridge does
- Reads the open thread on a connected site and writes new messages to the right lead
- Uploads media through a signed link so it shows on the timeline
- Records a WhatsApp Web call when your policy is on and the agent confirmed consent
- Shows a drafted reply in the side panel with the lead's context
- Places the draft in the site's own composer and stops
- Saves a thread on demand with click to log
What it never does
- Presses send
- Types, clicks or navigates for a person who is not present
- Runs in a headless or cloud browser
- Shares a session or changes a browser fingerprint
- Hands an agent a bulk queue
- Runs a playbook step in Auto mode
Honest about what this means
A browser bridge has limits. The limits are the point. Here is what to expect day to day.
Capture needs the tab open
Agents keep WhatsApp Web and their inboxes open during a shift. An organisation that wants after hours capture leaves one signed in machine open. If no tab is open nothing is captured. Click to log fills the gap when the agent returns.
Sending needs a person present
Every message that leaves a bridged site is sent by a signed in person from their own account, on purpose, after reading it. When the only channel for a lead is the bridge, the engine allows Suggest and Approve only.
A courtesy limit on every site
Drafts surfaced per site per day are capped, spaced out and kept inside the lead's business hours. If an agent dismisses a draft, the playbook moves to the next step, such as a call task.
Fail closed, pause per site
The rules that describe how to read each site are signed and versioned. A site whose rules are missing or fail verification stops capturing. An administrator can pause any single site from settings.
Ready to start?
Capture starts
in the first hour.
Install the extension, open WhatsApp Web and your inboxes and connect Zoom Phone. Nothing to migrate.