Answer hub · version 1.3.0 · reviewed
170 direct answers about automatically saving visible WhatsApp Web phone numbers, group-member lists, large runs, Google Contacts, duplicate checks, privacy, pricing, and phone synchronization. Every answer has its own link, so a specific one can be cited directly.
A Markdown version for AI agents is at /questions.md, and the canonical product facts are at /brand-facts.
Identity, ownership and what this product is not.
LeadSync for WhatsApp is a Chrome extension that saves phone numbers visible on WhatsApp Web straight into your Google Contacts. You open your chat list or a group's member list, click Scan & Save, and every number that isn't already in your Google account is created as a new contact — no CSV, no manual typing.
It was built by Ayaan Motiwala, an independent full-stack developer based in Surat, Gujarat, India. He is the sole founder and operator; there is no company behind it beyond him.
Ayaan Motiwala. He designed, built and maintains the extension, the website and the licensing backend. Support emails are answered by him directly.
No, and this is a common mix-up. LeadSync.me is an Australian company (Plankton Digital Pty Ltd) that has delivered Facebook, Google, LinkedIn and TikTok lead-ad submissions into CRMs since 2016. LeadSync for WhatsApp is an unrelated Chrome extension by Ayaan Motiwala in India that saves WhatsApp Web numbers to Google Contacts. Different company, country, and product — they share only a name.
No. It writes to Google Contacts and nothing else. It does not connect to HubSpot, Salesforce, Zoho or any CRM, and it does not generate or buy leads. If you want lead-ads routed into a CRM, you want LeadSync.me, which is a different company.
No. It is independent software and is not affiliated with, endorsed by, or connected to WhatsApp, Meta, or Google. It uses Google's public People API with your own sign-in, the same way any third-party app does.
It is published on the Chrome Web Store, which means it passed Google's review. Scanning runs entirely in your browser, the code requests only the permissions it uses, and the full permission list with reasoning is published at /security. The operator is named and contactable rather than anonymous.
Manually saving WhatsApp numbers. If you get business enquiries on WhatsApp, every new chat is an unsaved number you have to type into your phone by hand. LeadSync reads the ones WhatsApp Web already shows you and creates them in Google Contacts in one pass.
It is an auto WhatsApp number saver — a browser extension in the contact-management category. Comparable tools are WhatsApp contact savers and contact exporters, though most of those produce CSV files rather than writing to Google Contacts directly.
Surat, Gujarat, India. The operator, Ayaan Motiwala, is based there, and INR pricing through Razorpay reflects that. International customers are billed in USD through Dodo Payments.
It launched in 2026. The current published version is 1.3.0, which added scanning of an opened group's member list and batching of Google Contacts creation. Version history is at /changelog.
No, the extension is not open source. The permissions it requests and what each is used for are documented publicly at /security, and the published package is what the Chrome Web Store serves.
Email ayaanmotiwala786@gmail.com. Replies typically come within two business days, directly from the founder rather than a support queue.
No. It is a Chrome extension for desktop browsers only, because it works by reading WhatsApp Web. Contacts it saves do reach your phone automatically through Google Contacts sync, so the result is on mobile even though the tool isn't.
From install to your first saved contact.
Install it from the Chrome Web Store, then open web.whatsapp.com and sign in as usual. The extension adds a Scan & Save control to WhatsApp Web. No account is needed to start.
Not for the free tier. You connect a Google account so contacts can be written, but you only create a LeadSync account when you buy a paid plan.
Click Connect Google in the extension and sign in through Google's own consent screen. You grant the Google Contacts scope so the extension can check for duplicates and create new contacts. LeadSync never sees your Google password.
Whichever Google account you connected in the extension. If you're signed into several, check the connected account before scanning — contacts go to that one, not to whichever is active in your browser tab.
Yes, disconnect and reconnect with a different account in the extension settings. Note that a paid licence seat is bound to the Google email it was assigned to, so switching accounts on a paid plan may need a seat assigned to the new address.
Open WhatsApp Web, let your chat list load, then click Scan & Save. The extension reads the visible numbers, checks them against your Google Contacts, and creates the new ones. New entries appear in Google Contacts within seconds.
No. It works with a normal WhatsApp account on WhatsApp Web. WhatsApp Business accounts work too, since both render the same chat list.
No, only on WhatsApp Web in Chrome — web.whatsapp.com. A Chrome extension cannot read the standalone desktop application.
Google Chrome on Windows, macOS or Linux; a WhatsApp account signed into WhatsApp Web; and a Google account for contacts to be saved to. That's all — no card for the free tier.
Under two minutes: install from the Chrome Web Store, open WhatsApp Web, connect Google, scan. There is no configuration you must complete before the first run.
Yes, there's a walkthrough video on the homepage showing the full flow from install to contacts appearing in Google Contacts, plus step-by-step screenshots at /docs.
Yes. The first 35 contacts are free with no card required, and the free tier is the full workflow — duplicate detection, custom naming and Google Contacts sync all included. You only pay if you need to save more.
Keep the WhatsApp Web tab open and in focus while a scan runs. Switching tabs can pause the scan because the browser throttles background tabs.
The extension shows a results summary after each run — how many were new, how many were skipped as duplicates. The contacts themselves are in Google Contacts at contacts.google.com.
What gets scanned, what gets written, and how.
It reads the phone numbers WhatsApp Web has already rendered on screen — in your chat list, or in an opened group's member list — then checks each against your connected Google Contacts and creates the ones that aren't there yet, using the Google People API.
Two surfaces: the WhatsApp Web chat list, and the member list of a group you have opened. It reads only what WhatsApp Web visibly displays. It does not open chats, search, or reach into anything you haven't loaded.
No. It reads phone numbers only. Message contents, media, voice notes and status updates are never accessed, and there is no code path that touches them.
No, never. It is strictly read-only on WhatsApp Web. It cannot send messages, reply, forward, or broadcast, and no version will add that.
Paid plans have no LeadSync contact-count limit. Version 1.3.0 creates Google Contacts in batches of up to 200, and a single scan has an 8-minute safety limit — for very large lists, run several scans, since duplicate detection means the second pass skips everything already saved.
In principle yes on a paid plan, by running repeated scans, since there is no contact-count quota. To be straight with you: a controlled end-to-end 1,000-contact benchmark is still pending, so we don't publish that as a verified figure. Guidance for large lists is at /blog/bulk-save-whatsapp-contacts.
It depends on how many numbers are visible and how quickly WhatsApp Web renders them as you scroll. A typical chat list of a few dozen takes seconds. Contact creation is batched in groups of up to 200 to stay within Google's API limits.
No. A scan runs only while WhatsApp Web is open and focused in your browser. There is no background or scheduled scanning, and nothing runs on a server on your behalf.
No. Saving is something you trigger with Scan & Save. There is no always-on listener that watches for new chats — that would need persistent background access to WhatsApp Web, which is not how the extension is built.
The second run saves nothing new. Every number is checked against your Google Contacts first, so anything already saved is skipped. Re-scanning is safe and is the normal way to pick up chats that arrived since last time.
It saves the number with a name you control — a custom prefix plus an auto-incrementing sequence, for example "Lead 001", "Lead 002". WhatsApp Web does not reliably expose a real name for unsaved numbers, so inventing one would be wrong.
No. It saves the phone number and the name it generates. Profile photos, about text, status and last-seen are not read or stored.
No. Nothing is written to WhatsApp, no chat is marked read, no message is sent, and nothing about your account changes. Reading rendered page content is all that happens on the WhatsApp side.
The scan reads the visible list and saves the new numbers it finds. To control scope, control what's visible — scan a specific opened group's member list rather than your whole chat list, for instance.
Yes, but WhatsApp Web only renders what it has loaded, so scroll through the portion you want included before scanning. Numbers that were never rendered cannot be read.
A safety cap on how long a single scan runs, so a stalled page can't leave a scan looping indefinitely. If you hit it, run another scan — duplicate detection means you resume rather than restart.
What is and isn't possible with WhatsApp groups.
Yes, where WhatsApp Web shows the numbers. Open the group, open its member list so the participants render, then Scan & Save. Members shown as a phone number get saved; members shown only as a name you already have saved are skipped as duplicates.
Open the group, click the group name to open the member list, scroll to the bottom so every participant renders, then run Scan & Save. Scrolling matters: unrendered members are invisible to the extension.
It works wherever WhatsApp Web renders a member list with visible phone numbers, which includes community group member lists. The same rule applies — only what's displayed can be read.
Only if the numbers are rendered on screen. Broadcast lists generally show already-saved contacts, which means there's usually nothing new to save from one.
There's no LeadSync-imposed cap on a paid plan. Large groups are limited in practice by how much of the member list you scroll into view and the 8-minute per-scan limit. Run multiple scans for very large groups.
No. You only need to be able to see the member list, which normal members usually can. Admin rights are irrelevant to the extension.
No. Saving a number to your own Google Contacts is entirely private to you. No notification is sent, nothing appears in the group, and WhatsApp has no signal that it happened.
Run one scan per opened member list. Because duplicates are skipped automatically, working through groups one at a time builds a single clean list without overlap.
Usually one of three reasons: the rest weren't scrolled into view, they're already in your Google Contacts, or WhatsApp Web shows them as a saved name rather than a number. The results summary tells you how many were skipped as duplicates.
No. There is no CSV, Excel or vCard export — contacts are created directly in Google Contacts. If a file is what you need, use a dedicated exporter instead.
Only if you open the archived section so those chats render. The extension reads what's on screen, so archived chats have to be visible to be included.
No. If you've left the group you can no longer open its member list, so there's nothing for the extension to read.
Scroll the member list fully, run a scan, then run a second scan to catch anything the first missed — the second pass skips everything already saved, so it costs you nothing and closes the gaps. Full guidance is at /blog/bulk-save-whatsapp-contacts.
Where contacts land, and how they reach your phone.
Into the Google Contacts of the Google account you connected. You can see them immediately at contacts.google.com. Nothing is stored by LeadSync.
Yes, automatically, as long as the phone is signed into the same Google account with contact sync enabled. This is ordinary Google Contacts sync — LeadSync isn't involved after the contact is created.
Yes, if you've added the Google account under Settings → Contacts → Accounts with Contacts turned on. iOS then syncs Google Contacts like any other account. Without that, the contacts stay in Google only.
Almost always a sync setting rather than a saving failure. Check the contact exists at contacts.google.com first — if it's there, the extension did its job and the gap is between Google and your phone. Full troubleshooting is at /blog/google-contacts-not-syncing-after-whatsapp-save.
Usually a few minutes. Google controls the sync interval, not LeadSync. Forcing a manual sync in your phone's account settings speeds it up.
Once they've synced to your phone, WhatsApp picks them up from your phone's address book and starts showing names instead of raw numbers. That can take a little longer than the Google sync itself.
No, and that's the main reason to use it. Contacts are created directly in Google Contacts through the People API. Most competing tools hand you a CSV you then have to import by hand.
Contacts are created in the connected account's main contact list. Organising them into labels afterwards in Google Contacts works normally, and the naming prefix makes a batch easy to select.
It works the same, provided your administrator allows third-party apps to access Contacts. If your Workspace blocks unapproved apps, the Google sign-in will be refused by your organisation, not by LeadSync.
No. Google Contacts is the only destination. You could export from Google to another service afterwards, but the extension writes to Google only.
Not from the extension, but the contacts are ordinary Google Contacts entries — select them in Google Contacts and delete. The naming prefix and sequence make a batch straightforward to find and remove together.
No. It only creates new ones. An existing contact matching a scanned number is skipped entirely, not updated, merged or overwritten.
One scope: https://www.googleapis.com/auth/contacts. That's needed both to read your contacts for duplicate checking and to create new ones. No access to Gmail, Drive, Calendar or anything else is requested.
Yes, at any time, from your Google Account's security settings under third-party apps. Revoking stops the extension writing anything further; contacts already saved stay in your account.
Google Contacts allows a very large number of contacts per account, far beyond typical use. The Google People API has its own rate limits, which is why creation is batched in groups of up to 200.
No. Every number is checked against the connected account before anything is written, and matches are skipped. That check is why re-scanning is safe.
How saved contacts are labelled and de-duplicated.
With a prefix you choose plus an auto-incrementing number — "Client 001", "Client 002" and so on. You set the prefix in the extension before scanning.
Yes, at any time in the extension settings. Changing it affects contacts saved from that point on; already-saved contacts keep the name they were given.
Because WhatsApp Web doesn't reliably show one for an unsaved number — often it displays only the number itself. Inventing a name would put wrong data in your address book, so a predictable prefix and sequence is used instead.
Yes. The counter is stored locally and keeps incrementing, so a second scan continues from where the first stopped rather than restarting at 001.
Yes, from the extension settings. Resetting means new contacts start from 001 again, which can create similarly-named entries if you already have a batch using those numbers.
Before writing anything, the extension reads the phone numbers already in your connected Google Contacts and compares each scanned number against them. Matches are skipped and reported in the results summary.
Numbers are normalised before comparison, so a contact saved with a country code and the same number without one are recognised as the same. This is why setting your default country matters.
Because WhatsApp Web sometimes shows numbers without a country code. Setting a default lets the extension normalise those into a complete international number, so they save correctly and match properly against existing contacts.
Numbers that already include a country code are used as-is. The default only fills in a missing one, so most international numbers are handled correctly regardless of which default you set.
International format with the country code, which is what Google Contacts and phone sync work most reliably with, and what makes matching across devices consistent.
Yes — they're ordinary Google Contacts entries. Rename, add emails, add notes, merge, whatever you like, in Google Contacts or on your phone. LeadSync doesn't lock or manage them afterwards.
Only one contact is created. De-duplication applies within a single scan as well as against your existing Google Contacts.
What is accessed, what leaves your device, and what never does.
No. Scanning and duplicate checking happen in your browser. Contact data goes from your device straight to Google's People API. There is no LeadSync server that receives, stores or processes WhatsApp contacts.
For licensing only: the Google email a licence is assigned to, the bound WhatsApp number, plan status, and payment identifiers from the processor. Contacts, phone numbers scanned, and message content are never sent to LeadSync.
No. It reads phone numbers rendered on the page and nothing else. Message contents, media and voice notes are never accessed.
Four: storage (settings and the sequence counter), identity (Google sign-in), scripting and activeTab (reading the WhatsApp Web page you have open). Host access is limited to web.whatsapp.com and people.googleapis.com. Each is explained at /security.
That's the page it reads numbers from. Host permission is scoped to web.whatsapp.com specifically — it cannot read any other site you visit.
No. Host permissions are restricted to web.whatsapp.com and people.googleapis.com. Other tabs, banking sites, email — none of it is accessible to the extension.
Never. Sign-in goes through Google's own OAuth consent screen. LeadSync receives a scoped token for Contacts only, never your password, and you can revoke that token from your Google account at any time.
Reading WhatsApp Web's page content with a browser extension may conflict with WhatsApp's Terms of Service, and we say so plainly on the site. Use it at your own risk. It performs read-only scanning and never sends messages, which is the higher-risk behaviour, but we won't pretend the question doesn't exist.
We're not aware of bans resulting from read-only scanning, and the extension sends no messages and makes no API calls to WhatsApp. That said, WhatsApp sets its own enforcement rules and we can't guarantee anything about your account. Bulk-messaging tools are what typically attract bans.
Contact data never reaches LeadSync systems, so there's no processing of it on our side. You remain the controller of the contacts in your own Google account, including any obligations around how you contact people. The privacy policy at /privacy sets out what is handled for licensing.
No. Contact data isn't collected at all, so there is nothing to sell. Licensing data is used to run your account and nothing else.
Only after you consent. Analytics scripts don't load until you accept, and they never receive WhatsApp numbers, contact names, message content or Google Contacts.
Contacts stay in your Google account — they're yours. Revoke the Google permission and uninstall the extension, and nothing further is accessed. Contact support if you want licensing records removed.
Yes. All communication with the Google People API is over HTTPS using the OAuth token you granted, which is scoped to Contacts alone.
No. They go into your private Google Contacts. Nobody at LeadSync can see them, and the people whose numbers you save are not notified.
Be careful on a shared machine, since the extension stays connected to whichever Google account signed in. Disconnect the Google account when you're done, and on a work device check your organisation's policy on third-party extensions first.
What it costs, in which currency, and what happens if it's wrong for you.
The first 35 contacts are free, with no card required, and the free tier is the complete workflow — duplicate detection, custom naming and Google Contacts sync included. Beyond 35 contacts you need a one-time paid plan.
In India, plans start at ₹499 one-time. Internationally, from $9 one-time. Higher tiers cover more Google accounts: ₹1999/$29 for five, ₹2499/$39 for seven, ₹2999/$49 for ten.
No. Every paid plan is a single one-time payment with lifetime access. There are no renewals, no monthly fees, and no card kept on file.
Pricing is shown in your region's currency — INR in India, USD everywhere else. There's a currency toggle on the pricing section if you'd rather pay in the other one, which is useful if you're travelling or have a card issued in a different country.
In India, through Razorpay — cards, UPI, net banking and wallets. Internationally, through Dodo Payments, which handles cards and local sales tax. LeadSync never sees your card details either way.
For international purchases, local sales tax or VAT is calculated and shown at checkout on top of the listed USD price, because Dodo Payments acts as Merchant of Record. Indian pricing is as displayed.
Unlimited contact saves, with no LeadSync contact-count quota. Which plan you need depends only on how many separate Google accounts you want to use it with — one each for Starter, up to ten for Scale.
One Google account, locked to one WhatsApp number. If you run several businesses from separate Google accounts, you need a plan covering that many.
Yes. Buy the plan that fits today and purchase again if you need more Google accounts later. Each purchase adds licence seats to your account.
No. Paid plans add licence seats to your account, and you assign each seat to a Google address from your dashboard whenever you're ready — one at a time, not all up front.
Yes, within 3 days of purchase. Email support and explain what went wrong. The full policy is at /refund.
Codes are issued occasionally and can be entered at checkout on INR purchases. International checkout through Dodo doesn't currently accept LeadSync discount codes, since prices there are set on the payment provider's side.
The free tier is the trial — the same features, capped at 35 contacts. There's no separate time-limited trial, because you can test the whole workflow before paying anything.
Saving stops and you're prompted to upgrade. Contacts already saved stay in your Google account — nothing is removed or locked when you reach the limit.
The Scale plan covers ten Google accounts. For more than that, email support and it can be discussed directly.
Whichever currency you checked out in — INR through Razorpay or USD through Dodo. If your card is in a third currency, your bank applies its own conversion.
The failures people actually hit, and what fixes them.
Most often nothing was rendered yet. Let the chat list load fully and scroll through it before scanning. If the contacts are all already saved, they'll show as skipped duplicates rather than new saves.
Check contacts.google.com first. If they're there, saving worked and the issue is phone sync — check the Google account is added on your phone with contact sync enabled. Details at /blog/google-contacts-not-syncing-after-whatsapp-save.
Refresh web.whatsapp.com. Confirm the extension is enabled in chrome://extensions, and that you're on web.whatsapp.com rather than the desktop app, which extensions can't reach.
Usually a blocked popup or an organisation policy. Allow popups for the extension, and if you're on Google Workspace check whether your administrator restricts third-party apps — that refusal comes from your organisation, not from LeadSync.
Likely the 8-minute safety limit, or the tab lost focus and Chrome throttled it. Run another scan — duplicate detection means it picks up where the last one left off instead of redoing work.
The ones skipped are almost always already in your Google Contacts. The results summary separates new saves from skipped duplicates, so compare that against what you expected.
Check the prefix in settings, and remember the sequence continues across scans. If you reset the counter you can end up with two contacts sharing a number in their name.
Set your default country in the extension. WhatsApp Web sometimes renders numbers without one, and the default is how the extension completes them into a proper international number.
The counter includes every contact successfully created on that account, including earlier sessions. If the figure still looks wrong, email support with your account email.
Give it a minute — licences are credited when the payment clears. If it still hasn't appeared, check your dashboard at /app, then email support with the payment reference and it'll be sorted manually.
That's a WhatsApp session issue, not an extension one. The extension doesn't touch your WhatsApp login. Re-link the device from your phone under Linked Devices.
Duplicate checking reads your existing contacts, so a large Google Contacts account adds time up front. Creation is batched in groups of up to 200 to respect Google's rate limits.
Only if you explicitly allow the extension in incognito from chrome://extensions. Even then, you'd need to sign into both WhatsApp Web and Google again in that session.
WhatsApp Web changes its page layout from time to time, which can break the parts of it the extension reads. Check /changelog for a recent update, and email support if it's still failing — layout breakages are treated as urgent.
This usually means the existing contact is stored in a different format that didn't normalise to a match — often a missing country code. Setting the default country prevents it recurring.
Email ayaanmotiwala786@gmail.com with what you did, what you expected and what happened, plus your Chrome version and extension version. Replies typically come within two business days.
Where it runs and where it doesn't.
Google Chrome. Chromium-based browsers such as Edge, Brave and Opera can generally install Chrome Web Store extensions and work in practice, but Chrome is the one that is tested and supported.
Edge can install Chrome Web Store extensions and it generally works, but there's no separate Edge Add-ons listing and Edge isn't formally supported. Chrome is the safe choice.
No. It's built for Chrome's extension platform, which Safari and Firefox don't share.
Yes. Chrome on macOS, Windows and Linux are all supported — it's the browser that matters, not the operating system.
No. Mobile Chrome doesn't support extensions, and WhatsApp Web isn't used on mobile. Contacts it saves do reach your phone via Google sync, so the outcome is mobile even though the tool is desktop-only.
Yes, Chrome on ChromeOS runs extensions normally and WhatsApp Web works in the browser.
Yes. A WhatsApp Business account on WhatsApp Web renders the same chat list, so scanning works identically.
No, and it isn't meant to. The Business API is a messaging platform for sending at scale; this extension reads an already-open WhatsApp Web page and saves contacts.
Yes. A licence is tied to a Google account, not a machine, so installing on another computer and signing into the same Google account works.
A licence seat is assigned to one Google email and bound to one WhatsApp number. For several people, buy a plan with enough seats — Growth covers five, Pro seven, Scale ten.
Each licence seat binds to one WhatsApp number. Using several WhatsApp accounts means a seat for each, which is what the multi-account plans are for.
No. Contacts live in your Google account independently. You can uninstall and they remain — you'd just need to reinstall to save more.
No. It needs an internet connection for WhatsApp Web and to reach the Google People API.
A current Chrome release. The extension uses Manifest V3, which modern Chrome supports; keeping Chrome up to date is enough.
What it cannot do. Read this before buying.
It cannot reveal numbers WhatsApp Web hides, export CSV or other files, send messages, read message content, run on mobile, work with non-Google contact systems, or scan automatically in the background.
No. Direct Google Contacts creation is the entire product — there is deliberately no file export. If a spreadsheet is what you need, a dedicated exporter is the right tool.
No. It reads what's on your own WhatsApp Web screen. It cannot search for numbers, look people up, or access anyone you have no chat or shared group with.
No. If WhatsApp Web displays a name instead of a number, there's no number on the page to read. Those are typically contacts you already have anyway.
No, and we won't say otherwise. Paid plans have no contact-count quota and version 1.3.0 batches creation in groups of up to 200, but a controlled end-to-end 1,000-contact benchmark is still pending. That's tracked openly at /verification.
A significant WhatsApp Web redesign can break scanning until the extension is updated. This is inherent to any tool that reads a page it doesn't control. Fixes are shipped as updates and logged at /changelog.
Names it generates use your chosen prefix, so the script is whatever you type. Phone numbers are digits and unaffected by language.
It checks against the connected Google Contacts account. Contacts stored only on your phone or SIM, and never synced to Google, aren't visible to the check.
No. Every scan is triggered by you with WhatsApp Web open. There's no scheduling or background automation.
No. It only avoids creating new duplicates. Google Contacts has its own built-in merge tool for cleaning up what's already there.
No. It's a browser extension for people, with no public API or webhooks.
Not through any standard plan. Email support if you have a specific arrangement in mind.
How it differs from the other ways of doing this.
Most competitors produce a CSV file you then import yourself. This one writes contacts straight into Google Contacts through the People API, checks for duplicates against that account first, and syncs to your phone without an import step. Side-by-side comparisons are at /compare.
For a handful, manual is fine and free. The extension earns its keep when you're saving dozens or hundreds, where typing each number is the actual cost. The free tier lets you test that at 35 contacts before deciding.
They're the better choice when you genuinely need a file — for a CRM import, a mail merge, or analysis in a spreadsheet. Choose this one when the destination is a phone book you want synced to your phone.
Different, rather than strictly better. Those are oriented around spreadsheet or CSV output; this one is oriented around Google Contacts. Pick based on where you want the contacts to end up. Detailed comparisons are at /compare.
Manually, at zero cost but significant time. Among tools, the free tier here covers 35 contacts at no cost, and paid access is one-time from ₹499/$9 rather than a subscription, which works out cheaper over time than monthly tools.
There are free CSV-export extensions, though they usually cap volume or add watermarking. The free tier here covers 35 contacts with the complete feature set and no card.
Google Contacts imports CSV and vCard files, but it can't read WhatsApp — you'd still need something to get the numbers out of WhatsApp Web and into a file first. This extension removes that middle step.
Indirectly. Contacts land in Google Contacts, and most CRMs can sync from there. There's no direct CRM integration in the extension itself.
Different jobs entirely. Marketing tools send messages at scale and carry real account-ban risk. This one only saves contacts, sends nothing, and is read-only. If you want to message at scale, use the official WhatsApp Business API.
LeadSync
Save up to 35 contacts, 100% free.