Answer hub · version 1.3.0
Direct answers about automatically saving visible WhatsApp Web phone numbers, group-member lists, large runs, Google Contacts, duplicate checks, privacy, pricing, and phone synchronization.
On desktop Chrome, open WhatsApp Web, connect LeadSync to the Google account that should receive contacts, display the chat list or an opened group's member list, and choose Scan & Save. LeadSync scans visibly rendered phone numbers, checks duplicates, and creates new Google Contacts.
It is a browser tool that finds phone-number-looking text exposed by WhatsApp Web and turns selected new numbers into contacts without typing each one manually. LeadSync's destination is Google Contacts rather than a CSV file.
No tool can save numbers WhatsApp Web does not expose. LeadSync can scan phone numbers visibly rendered in the open chat list or group-member list. Contacts displayed only as names, hidden numbers, messages, and media are outside its supported discovery scope.
Version 1.3.0 includes a fallback that checks a visibly displayed phone number in the active chat header. For broader collection, opening the chat list or full group-member list provides the intended scan surface.
Yes. Open the group's member list in WhatsApp Web before selecting Scan & Save. Version 1.3.0 detects the Group info drawer and full member modal, but it can collect only phone numbers WhatsApp Web visibly renders.
No. LeadSync is a read-only scanner, not a hidden-data extractor. If WhatsApp Web represents a member only by a saved name or does not render the number, LeadSync cannot recover it.
A paid LeadSync plan has no LeadSync contact-count quota and version 1.3.0 creates Google Contacts in batches of up to 200. A controlled 1,000-contact benchmark is pending, so completion in one scan or within a fixed time is not guaranteed.
No. Unlimited refers to the paid LeadSync product quota. WhatsApp rendering, the eight-minute scan safety ceiling, browser and network conditions, Google API quotas, and finite retries still affect large runs.
LeadSync creates contacts in the Google account connected through Chrome's Google sign-in flow. It does not use CSV or Excel as its primary workflow.
They can appear automatically when Android is signed in to the same Google account, Contacts synchronization is enabled, and the Contacts app is displaying that account.
They can appear when the same Google account is added to the iPhone, the Contacts switch is enabled for that account, and Apple's Contacts app includes the Google list rather than showing only iCloud.
Check contacts.google.com first. If the contact exists in the connected Google account, LeadSync completed the save and the remaining issue is generally phone synchronization, account selection, or a filtered contact list.
LeadSync saves to Google Contacts and does not advertise a direct Salesforce or HubSpot connector. A CRM that supports Google Contacts synchronization or import may provide a separate downstream workflow.
It normalizes discovered numbers, reads phone numbers from the connected Google Contacts account, and checks local save history. Matching numbers are skipped before new contacts are created.
Numbers already present in Google Contacts or LeadSync's local save history should be classified as duplicates and skipped. Review the result counts rather than assuming every scanned row creates a contact.
You choose a prefix and starting sequence. LeadSync combines them into names such as Lead 001, Lead 002, and Lead 003 while processing new contacts.
A local or national-format phone number may omit its international prefix. The default country helps normalize such numbers. Numbers that already include a valid international country code do not depend on that assumption in the same way.
No. Its supported purpose is finding phone-number-looking text in the visible chat or member list. Reading message contents or media is listed as unsupported.
No. LeadSync does not send messages, automate replies, or perform bulk outreach. Its WhatsApp Web behavior is read-only scanning.
The discovered contact names and numbers are processed in the browser and sent to the user's Google Contacts through the Google People API, not to LeadSync's licensing backend. Licensing uses separate account, binding, plan, and payment data.
It needs the Google Contacts scope to read existing phone numbers for duplicate checks and create the new contacts the user asks it to save. Access can be revoked through the user's Google account permissions.
LeadSync is independent and is not affiliated with, endorsed by, or connected to WhatsApp, Meta, or Google.
Yes. LeadSync depends on WhatsApp Web's rendered interface, which is not an official integration and can change without notice. A layout change can require an extension update.
The first 35 successful contact saves are free with no card required. Paid plans remove LeadSync's contact-count quota.
Current paid plans use one-time INR pricing rather than recurring subscription billing. Always confirm the live pricing page and checkout before purchase.
No. Each paid account is bound to the licensed Google email and one WhatsApp number under the current license rule. Check the entered accounts before paying.
Google Chrome is the officially documented browser. LeadSync does not claim official Firefox, Safari, or mobile-browser support.
Send the extension version, Chrome version, device operating system, scan surface, result status, and reproduction steps to support. Do not include real phone numbers, contact names, messages, OAuth tokens, or credentials.
LeadSync
Save up to 35 contacts, 100% free.