Recruiters

Save Candidate WhatsApp Numbers to Google Contacts

The situation

Candidates reach you on WhatsApp from job posts, referrals and groups. Most are not right for the role they applied to but are right for something later. The chat list becomes an unsearchable archive of CVs you half-remember.

What goes wrong today

• A mandate arrives for a role you interviewed someone perfect for four months ago, and you cannot find them.
• Candidate chats show raw numbers, so you cannot tell who is a Java developer and who is an accountant without opening each one.
• CVs are sitting in chat attachments with no index of who sent what.
• Candidates and clients are in the same undifferentiated chat list.
• Unsaved candidate numbers vanish entirely if a chat is cleared or a phone is replaced.

The workflow

1. 1

   Open WhatsApp Web on a desktop

   Scanning reads the rendered page on your own machine; no candidate data goes to any LeadSync server.

2. 2

   Scroll the chat list to the bottom

   Unscrolled chats are not rendered into the page, so they cannot be read. This determines how much of the backlog a run captures.

3. 3

   Save the backlog with a batch prefix

   Something like `CAND BACKLOG` keeps the first clear-out identifiable and separate from candidates you save deliberately afterwards.

4. 4

   Annotate from the chat, on a keyboard

   Go down the list at contacts.google.com, open each chat alongside it, and record role, primary skill, experience and current location. Use the Company field for the current employer — it is searchable and syncs.

5. 5

   Save and annotate new candidates the same day

   The notes you write while the conversation is fresh are the ones that are still accurate when you search them later.

6. 6

   Re-scan monthly

   Duplicate checking means a monthly pass only adds candidates you missed, so it is safe to make routine.

A naming convention that suits this work

Unknown numbers arrive without names, so they need one. The convention is the cheapest possible CRM, and it works because Google Contacts search matches any part of a name.

What you get

• A new mandate can be matched by searching a skill rather than scrolling months of chats.
• Caller ID identifies a candidate and their role when they ring back.
• Candidates and clients are separable at a glance.
• The list is in your Google account, so it is backed up and moves with you between devices.
• Exportable to an ATS later, because Google Contacts is a standard import source.

Where this stops being enough

Said plainly, because finding out later wastes your time:

• This is not an applicant tracking system. There are no interview stages, no scheduling, no CV parsing and no audit trail.
• It does not work for a team pipeline. A shared address book does not give two recruiters a shared view of progress.
• It stores no CVs. Attachments remain in the chat; the contact is the index to them, not the archive.
• LeadSync cannot message candidates and never will — it is read-only.

Free tools that help here