← Back to Systems
Aldermere Systems / Build Notes

Speed-to-Lead Automation

# Speed-to-Lead Automation: DIY Installation Manual

Welcome to your **Speed-to-Lead Business-in-a-Box**! This guide contains step-by-step instructions to install, configure, and activate your instant lead notification and auto-response pipeline. 

By following this manual, you will set up the automation in **less than 20 minutes** using free accounts on **Make.com** and **Twilio**.

---

## 📋 What You Need Before Starting
Before setting up the automation, ensure you have:
1. **A website contact form** (WordPress, Elementor, Wix, Squarespace, Webflow, Jotform, or similar).
2. **A free Make.com account** (includes 1,000 free operations per month, enough for ~300 leads).
3. **A free Twilio.com account** (for sending instant SMS alerts to your phone).
4. **A calendar booking link** (Calendly, TidyCal, Google Calendar bookings, etc.).

---

## ⚡ Step 1: Import the Scenario Blueprint into Make.com

We have pre-built the entire automation logic for you in a blueprint file. You only need to import it.

1. Log into your [Make.com](https://www.make.com/) account.
2. From the dashboard, click **Create a new scenario** (top right).
3. Click the **three dots (...)** at the bottom toolbar and select **Import Blueprint**.
4. Choose the **`make_blueprint.json`** file included in this package.
5. Click **Save**. You will now see the pre-wired pipeline layout:
   ```
   [Webhook Trigger] ➡️ [Twilio SMS Alert] ➡️ [Gmail Auto-Responder]
   ```

---

## 🔌 Step 2: Connect Your Website Lead Form (Module 1)

1. Double-click the first module (the purple **Webhooks** circle).
2. Click **Add** to create a new webhook. Name it `My Contact Form` and click **Save**.
3. Make will generate a unique URL (e.g., `https://hook.us1.make.com/...`). Click **Copy Address to Clipboard**.
4. Paste this Webhook URL into your website form integration settings:
   * **Elementor Form:** Actions After Submit ➡️ Add "Webhook" ➡️ Paste the URL.
   * **Wix / Squarespace / Jotform:** Navigate to Integrations ➡️ Webhooks ➡️ Paste the URL.
5. Once pasted, click **Run Once** in Make. Then go to your live website form, fill out a fake submission (Name, Phone, Email, Message), and send it.
6. Make will show a green checkmark indicating it successfully caught the lead structure.

---

## 📱 Step 3: Connect Your Twilio SMS Alerts (Module 2)

This module text-messages you the second a lead comes in, so you can call them back instantly.

1. Go to [Twilio.com](https://www.twilio.com/) and register a free account.
2. In the Twilio Console, click **Get a Trial Number** and copy your **Account SID** and **Auth Token**.
3. Go back to Make.com, double-click the **Twilio** module, and click **Add** to create a connection. Paste your SID and Auth Token.
4. Set up the SMS settings:
   * **Sender Phone Number:** Select your Twilio trial number from the dropdown list.
   * **Receiver Phone Number:** Enter your mobile phone number (with country code, e.g. `+447123456789`).
   * **Message Text:** (Pre-written for you. Verify that variables like name, phone, and service align with your webhook data).

---

## ✉️ Step 4: Connect Your Email Auto-Responder (Module 3)

This email replies to the customer within 3 seconds, offering them your booking link.

1. Double-click the **Gmail/Email** module in Make.
2. Click **Add** to authorize your business email address.
3. Configure your response settings:
   * **To:** Select the lead's email address variable captured from Module 1.
   * **Subject:** Set your subject line (e.g. `Inquiry Received - [Business Name]`).
   * **Email Body:** In the HTML or text input area, paste your booking link to replace the bracketed placeholder: `[Insert Your Calendly Link Here]`.
4. Click **OK** to close the settings card.

---

## 🔬 Step 5: Test and Turn It On!

1. Click **Save** (the disk icon at the bottom of Make).
2. Click **Run Once** to start a test.
3. Submit a new test lead through your website form.
4. **Confirm the following outcomes:**
   * Your phone receives an SMS alert with the lead's details.
   * The lead receives the auto-response email in their inbox.
5. If the test is successful, slide the scheduling switch at the bottom-left from **OFF** to **ON**.

*Your automated Speed-to-Lead system is now live!*

---

## 🔐 Security & Red Team Mitigations (Protecting Your System)

Since this automation runs on cloud platforms and processes customer details, implement these security practices to prevent unauthorized access or system abuse:

### 1. Protect Your Webhook Endpoint (Anti-Spam)
Your Make.com webhook URL is public. If an attacker discovers it, they can send spam payloads, causing you to incur Twilio billing charges and email suspension.
* **Mitigation:**
  * **Obfuscate the URL:** Do not post your Make webhook URL directly in plain-text client-side HTML. Instead, submit your website form to a server-side action handler (like a WordPress PHP script or Webflow server action) that forwards the data to Make from your backend server.
  * **Verification Headers:** Add a custom header (e.g., `X-Auth-Token: [SecretKey]`) in your form submissions. In Make, add a **Filters** block immediately after the Webhook module. Set the filter condition to only allow executions if the header matches your `[SecretKey]`. If a request doesn't contain this key, Make will block it instantly.

### 2. Twilio API Secret Keys Management
* **Mitigation:**
  * Never save your Twilio Account SID or Auth Token in public repositories (like GitHub) or on-page code. 
  * Make and Zapier store these keys in their secure connection vaults, so they are never exposed to users looking at your website. Keep them inside Make's securely encrypted connections.

### 3. Data Privacy Compliance (GDPR / UK-GDPR)
* **Mitigation:**
  * Make.com stores historical logs of lead name, phone, and emails by default. To remain fully GDPR compliant, go to your Make scenario settings, click **Scenario Options**, and set **Data Is Confidential** to **Yes**. This prevents Make from storing the raw contact data in their log history, using it only to route the message in real-time.