Case study 02

Multichannel outbound from one lead table

A real estate photography agency wanted to reach its leads on LinkedIn, email, and SMS. We built a backend and three Make.com scenarios that keep every channel's status on one row of a shared lead table.

Goal

Use every channel the client wanted, so more leads turn into deals.

The tools that send LinkedIn requests, email, and SMS are each good at their own sequence and weak at sharing one status. So the lead table became the record, and every channel writes back to it.

Custom backend + Make.com

One Google Sheets lead table, shared by every part.

Our backend

  1. CSV upload

    Columns mapped, including alternative names

  2. Normalize + dedupe

    Against the table, the file, and the LinkedIn campaign

  3. Route

    A LinkedIn URL goes to HeyReach, the rest to Instantly

batches within API limits

Channels

  1. HeyReach

    LinkedIn sequence

  2. Instantly

    Email sequence

  3. Twilio

    SMS

webhooks

Make.com

→ Slack / Gmail alerts
  1. 1 · LinkedIn activity

    HeyReach events → status → enrol in Instantly

  2. 2 · Replies & link clicks

    Instantly events → status → SMS via Twilio → To Call

  3. 3 · SMS opt-out

    Twilio STOP → find lead by phone → Unsubscribed

status updates

Google Sheets · shared lead table

One row per lead, with every channel's status. Our dashboard reads it for live stats and call priority.

What we built

01 · Backend

Lead import & dedupe

  • CSV columns mapped, including alternative names
  • Emails and LinkedIn URLs normalized
  • Duplicates removed against the table, the file, and the LinkedIn campaign
  • Every upload gets a report
02 · Backend

Channel routing

  • Leads with LinkedIn go to HeyReach, the rest to Instantly
  • Sent in batches within API limits
  • Checks the leads actually landed; resumes a finished campaign
03 · Make · 1

LinkedIn sync

  • HeyReach events: request sent, like, profile view, message, accepted
  • Each one updates the lead's status and time
  • After a request goes out, the lead is also enrolled in email
04 · Make · 2

Email events

  • Interested, not interested, wrong person, and bounce update the lead
  • Reply time is recorded
  • “Wrong person” sends an email alert
05 · Make · 2

Click → SMS → call

  • A link click picks the SMS for that email step
  • Waits a few minutes, then sends it via Twilio once
  • Sets Call Priority to To Call and posts to Slack
06 · Make · 3

SMS opt-out

  • A STOP reply finds the lead by phone
  • Marks it Unsubscribed in the table
  • Posts to Slack

The React dashboard handles CSV upload and shows live stats from the table, call priority, and SMS templates.

Our role

  • Designed and built the whole system: a custom backend and three Make.com scenarios
  • Set up the Instantly and HeyReach campaigns and automations end to end
  • Advised which mailboxes to buy, and how many domains and mailboxes
  • Warmed up the mailboxes
  • Helped write the outreach copy
  • Configured every campaign setting
  • Built the step-by-step LinkedIn sequence in HeyReach
  • Registered the SMS sender (A2P)

Platforms

  • Make.com
  • HeyReach
  • Instantly
  • Twilio
  • Google Sheets
  • Slack
  • Gmail
  • React / TypeScript
  • Netlify Functions