Find answers to common questions about transcription, plans, billing, and privacy.
No results found. Try different keywords or contact us.
You don't need to do anything: if you installed from the Chrome Web Store (or the Edge store), updates arrive automatically, usually within a few hours.
Closing and reopening the browser helps complete a pending update. After an update, reload WhatsApp Web (F5) so the tab uses the new version.
You can check your version in the extension popup.
Yes, message scheduling is available! It's a Pro feature — on the Free plan you can schedule up to 3 messages per day.
How to schedule:
Sending is individual and uses WhatsApp's official chat mechanism (it is NOT bulk sending). ZapVox applies automatic safety limits (minimum interval between sends, timing variation, and hourly/daily/weekly caps) to reduce the risk of being blocked.
⚠️ Important: use it moderately. Excessive use may lead to your account being blocked by WhatsApp — that decision is exclusively Meta's and is your responsibility. Reminders (🔔 to yourself) remain free on all plans.
chrome://extensions, click "Details" on ZapVox, then "Clear site data." This removes all cached transcriptions, settings, and BYOK keys.This message comes from Chrome itself. It appears when the part of ZapVox running inside the WhatsApp Web tab tries to talk to the extension engine and finds nobody on the other end. Your account and plan have nothing to do with it.
Why it happens
How to fix it (follow the order and test after each step):
chrome://extensions and check that the toggle on the ZapVox card is blue. If it is off, turn it on and reload WhatsApp Web. There is no need to update anything by hand: if you installed from the Chrome Web Store, updates arrive automatically.chrome://extensions, remove all of them and install a single copy from the official store.chrome://settings/performance, add web.whatsapp.com to "Always keep these sites active". If you use a tab-suspender extension, add WhatsApp Web to its exceptions.Still happening? Send [email protected] a screenshot of the ZapVox card in chrome://extensions (with the version and the "Errors" button, if any) and the first line of chrome://version.
To transcribe, ZapVox needs the same audio file that WhatsApp Web plays. When WhatsApp hasn't brought that file to your computer yet, there is nothing to transcribe — and WhatsApp itself shows it.
How to spot it: instead of ▶️ you see a download icon (down arrow), or no play button at all. If you press play and it doesn't play, that's it.
What to do, in this order:
Once the ▶️ is back and it plays, ZapVox transcribes it normally.
This was fixed in version 3.10.91. If clicking a contact's name only marks the row and opens nothing, this is it.
Immediate workaround, no update needed:
It works again right away. Then update to 3.10.91 or newer (the update arrives on its own from the store; closing and reopening Chrome completes it) and you can turn the highlighted button back on if you like.
What was happening: an internal protection that stops clicks on our own buttons from leaking into WhatsApp ended up, under certain conditions, applying to the whole page — so WhatsApp stopped receiving clicks. It only affected people with the highlighted button turned on, which is why it showed up on one machine and not another. It's fixed, with tests that reproduce exactly that condition.
Updated and still happening? Write to [email protected] and we'll look into it.
This is the first thing to test when ZapVox was working and stopped — especially if reloading doesn't help.
WhatsApp Web was not designed to host extensions. When two or more of them modify the same screen at once (bulk-send tools, WhatsApp CRMs, chat organisers, translators), they trip over each other: buttons disappear, audio fails to load, transcription never completes.
A one-minute test:
chrome://extensionsDid it work? It was a conflict. Re-enable the others one at a time until you find the culprit — and tell us which one, so we can try to coexist with it.
Still failing with ZapVox alone? Then it's on us: send a console screenshot (F12 → Console) to [email protected] and we'll investigate.
When you choose "Sign in with e-mail (code)", ZapVox immediately sends an e-mail with an 8-digit code, valid for 1 hour. It comes from [email protected] with the subject "Seu código de acesso ao ZapVox: 12345678" (the body is in Portuguese, English and Spanish). If it didn't show up, try this in order:
Still nothing? Write to [email protected] with the e-mail you used and the time of the request — we check delivery on our side.
Our team is here to help. Send us a message and we'll get back to you.
Email: [email protected]