Automations → Returning lead → recognised → "second contact", not "new lead"

DUPLICATE CHECK

Returning lead → recognised → "second contact", not "new lead"

Before a lead is logged, the automation checks whether the phone is already in the log. If it is — the alert says "came back", and sales knows this is a second conversation.

MakeGoogle SheetsTelegram4 operations / run✓ Imported successfully into our Make account
Video cover: DUPLICATE CHECK

The problem

The same person fills the form twice and gets two "hi, I saw you left your details" calls from the same salesperson. They conclude there is no system. The consultant's client looks amateur — because of the automation the consultant built.

What happens when it runs

  1. A webhook receives the form
  2. Search the leads log by phone number
  3. Found → new row marked "returning" + alert "second contact from {name}, previous on {date}"
  4. Not found → a normal row + a "new lead" alert

The tools inside

Before you start

Three things to have ready before importing, or Make will ask and you will have to leave halfway:

  • The webhook address
  • The leads spreadsheet id and the phone column
  • Chat ID

Sheet templates

The file maps columns by position. Start from exactly these headers, in this order — a column in the wrong place writes a phone number into the email column.

  • Leads log · timestamp | name | phone | email | source | kind Download ↓

How to import (2 minutes)

  1. In Make: Scenarios → Create a new scenario
  2. At the bottom, the three dots (⋯) → Import Blueprint → choose the file you downloaded
  3. Click every module with an exclamation mark: choose your connection (Google, Telegram) — Make creates one in a click if you have none
  4. Replace every value in double curly braces ({{…}}) with your own from the list above
  5. Run once with a test row in the sheet. Only when it passes — Schedule and ON

The video

What does not work in it

  • Matching is by phone only. "050-1234567" and "0501234567" are two people as far as the sheet is concerned. Normalise the number in the form or in a module before the search.
  • Searching a sheet of thousands of rows is slow and costs operations. Above ~5,000 leads, move to a Make Data Store or a database.

Affiliate link. If you sign up through it we earn a commission from Make; your price is the same, and the link gives you one month of Core free.

More automations

All automations →